Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-24 Thread Neal Norwitz
[bcc python-dev to move to python-3000] On 3/22/06, Michael Hudson <[EMAIL PROTECTED]> wrote: > "Fredrik Lundh" <[EMAIL PROTECTED]> writes: > > > neal.norwitz wrote: > > > >> +Outstanding Issues > >> +== > >> + > >> +* Require C99, so we can use // comments, named initializers, dec

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-23 Thread Martin v. Löwis
M.-A. Lemburg wrote: > That would be Donn Cave: > > http://bebits.com/app/4232 > > He's also the one who wrote the Bethon wrapper for the BeOS C++ API. > > BTW, the fact that you don't see new checkins doesn't necessarily > mean that a port is no longer used. It may just be that the existi

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-23 Thread Neal Norwitz
On 3/23/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > Martin v. Löwis wrote: > > M.-A. Lemburg wrote: > >>> And we still have someone actively interested in maintaining the OS2 > >>> port, it seems. > >> > >> Dito for BeOS, now under the name Zeta OS. > > > > Who is the one interested in maintaini

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-23 Thread M.-A. Lemburg
Martin v. Löwis wrote: > M.-A. Lemburg wrote: >>> And we still have someone actively interested in maintaining the OS2 >>> port, it seems. >> >> Dito for BeOS, now under the name Zeta OS. > > Who is the one interested in maintaining the BeOS port? the last > checkins related to BeOS seem to origin

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-22 Thread Martin v. Löwis
M.-A. Lemburg wrote: >> And we still have someone actively interested in maintaining the OS2 >> port, it seems. > > Dito for BeOS, now under the name Zeta OS. Who is the one interested in maintaining the BeOS port? the last checkins related to BeOS seem to originate from the 2001/2002 period. Re

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-22 Thread M.-A. Lemburg
Michael Hudson wrote: > "Fredrik Lundh" <[EMAIL PROTECTED]> writes: > >> neal.norwitz wrote: >> >>> +Outstanding Issues >>> +== >>> + >>> +* Require C99, so we can use // comments, named initializers, declare >>> variables >>> + without introducing a new scope, among other benefi

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-22 Thread Fredrik Lundh
Michael Hudson wrote: > >> +* Remove support for old systems, including: OS2, BeOS, RISCOS, (SGI) > >> Irix, Tru64 > > > > what's old with tru64 ? it's not that uncommon in places where Python > > has a strong presence, you can still buy AXP hardware throughout 2006, > > and HP says they'll keep

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-22 Thread Michael Hudson
"Fredrik Lundh" <[EMAIL PROTECTED]> writes: > neal.norwitz wrote: > >> +Outstanding Issues >> +== >> + >> +* Require C99, so we can use // comments, named initializers, declare >> variables >> + without introducing a new scope, among other benefits. > > gcc only, in other words ?

Re: [Python-Dev] r43214 - peps/trunk/pep-3000.txt

2006-03-22 Thread Fredrik Lundh
neal.norwitz wrote: > +Outstanding Issues > +== > + > +* Require C99, so we can use // comments, named initializers, declare > variables > + without introducing a new scope, among other benefits. gcc only, in other words ? > +* Remove support for old systems, including: OS2, Be