[Python-Dev] status of OS/2 ports of Python

[Guido van Rossum]

> > Andy, would it help if you had SourceForge commit privileges?  You'd
> > be obliged to only check in code that doesn't break the build on other
> > platforms, so you would be required to test anything you want to check
> > in on another platform (Linux or Windows) before you commit to save
> > you the embarrassment of breaking the build, but if (as I expect) you
> > would mostly be adding stuff inside "#ifdef OS2", that shouldn't be a
> > big burden.  It would save you the trouble of uploading patches to
> > SourceForge and it would save *us* the trouble of reviewing your
> > patches and checking them in.
> 
> I've never used CVS, but am prepared to rectify that.

Be prepared for some long evenings of fun with CVS!  Lots of folks
here on python-dev have developed a deep understanding of CVS theory
and tricks though, so you're in a good place to learn.

> I am also prepared
> to work within the commit rules you specify.

I didn't doubt this for a second.

> I can work with the requirement for testing on another platform if FreeBSD
> is an acceptable test platform.

Sure is -- in fact, we could use more FreeBSD testing. :-)

> I would also propose to look after patches to the VAC++ build (such as
> Michael Muller's), on the basis that although I can't test the patches
> directly, I can test that they don't affect the rest of the system, and I
> can work with the submitter to resolve issues that affect OS/2 specific
> functionality.

That sounds like a very good idea.  Right now I don't really know what
to do with the two sets of OS/2 patches...  Since Michael is cc'ed
here, Michael, what do you think of this?

> As to whether having commit privs would help - on the time availability
> front, no; otherwise more likely than not.

OK.  As soon as you think you're ready to commit anything (try
something small first :-), post a message here and one of the admins
will add you.  (You need to have a SF login first.)  Not me, I'm about
to go underground for a while to take care of my wife and son (to be
born by Friday).

> > All your code would be owned by the PSF, but that's what you want
> > anyway, right?
> 
> Yes.

Good!  The PSF legal team will eventually come up with paperwork to
make this official; in the mean time, this archived email message is
good enough for me.

--Guido van Rossum (home page: http://www.python.org/~guido/)