The platform module has a way to map system names such as returned by
uname() to marketing names. It maps SunOS to Solaris, for example. But
it doesn't map Darwin to Mac OS X. I think I know how to map Darwin
version numbers to OS X version numbers: from
http://www.opensource.apple.com/darwinsource/ it is clear that OS X
10.a.b corresponds to Darwin (a+4).b, except for OS X versions <=
10.1. I'd be happy to write the code and add it to system_alias() in
platform.py. Is this a good idea?
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
So no brown-paper-bag bugs have been reported that I've seen, so let's
unfreeze the release24-maint branch. Note that there will be at least
a 2.4.3, probably around Feb-March next year (around the time of
2.5a1, as currently vaguely planned). I might also cut a final 2.4.4
after 2.5 final is out.
--
Anthony Baxter <anthony(a)interlink.com.au>
It's never too late to have a happy childhood.
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.2 (final).
Python 2.4.2 is a bug-fix release. See the release notes at the
website (also available as Misc/NEWS in the source distribution) for
details of the more than 60 bugs squished in this release.
For more information on Python 2.4.2, including download links for
various platforms, release notes, and known issues, please see:
http://www.python.org/2.4.2
Highlights of this new release include:
- Bug fixes. According to the release notes, more than 60 have been
fixed, including bugs that prevented Python from working properly
on 64 bit HP/UX and AIX systems.
Highlights of the previous major Python release (2.4) are available
from the Python 2.4 page, at
http://www.python.org/2.4/highlights.html
Enjoy the new release,
Anthony
Anthony Baxter
anthony(a)python.org
Python Release Manager
(on behalf of the entire python-dev team)
The Python 2.4.2 documentation is now online in the main documentation area
(as opposed to just the /dev/ area) for both www.python.org and
docs.python.org. The 2.4 and 2.4.1 documentation areas have been updated to
link to the 2.4.2 documentation as the preferred documentation for all 2.4.x
releases.
-Fred
--
Fred L. Drake, Jr. <fdrake at acm.org>
Sorry for looking in every hole.
Just a suggestion.
A= condition and first or second
problem is in case when first in (None,0,[],"").
May be invent new operator 'take'.
take - returns right operator when left evals to True and stops
computing condidtional expression.
Then we could write:
A = condition take first or second.
A = x==y take w or s
A = z is not None and q!=12 take [] or allowable(z,q) take [(z,q)] or
"Impossible"
Ok, it might looks ugly. But may be not.
-------------------------------------
Excuse my english.
Hello,
I've come to a problem with pty.spawn() as it states on its source code:
# Bugs: No signal handling. Doesn't set slave termios and window size.
As I need this feature working, I want to fix this bug. Does someone
have any idea on how to fix it?
(My problem: I want to launch ncurses software from my python
software, then come back, choose another program and launch it, ...)
--
Gustavo Sverzut Barbieri
---------------------------------------
Computer Engineer 2001 - UNICAMP
GPSL - Grupo Pro Software Livre
Cell..: +55 (19) 9165 8010
Jabber: gsbarbieri(a)jabber.org
ICQ#: 17249123
MSN: barbieri(a)gmail.com
Skype: gsbarbieri
GPG: 0xB640E1A2 @ wwwkeys.pgp.net
So here we go - the release24-maint branch will be frozen from
midnight UTC on Wednesday the 28th (about 36 hours from now). This is
to cut 2.4.2 (final).
If you have any pending patches you want to see landed on the branch,
mail me about them - and do it soon!
There's been a bunch of fixes since 2.4.2c1, but nothing that I judge
making it worthwhile doing a 2.4.2c2. I'm open to other opinions
here, of course.
Anthony
(Adding python-dev back to the CC list)
On 9/20/05, Jason Orendorff <jason.orendorff(a)gmail.com> wrote:
> > If there's one thing I've learned from the PEP 308 vote, it is that
> > votes for language don't work. I prefer some discussion on Python-dev
> > after which I pick one.
>
> +1
>
> Some visual aids:
>
> return (if q: q.popleft() else: None)
> return (if q then q.popleft() else None)
> return q ? q.popleft() : None
>
> Hmmm. Score one for ?:. But:
Why? Just because it's shorter?
> menu.append(
> if gotHerring(): popHerring()
> elif gotAnyFish(): popAnyFish()
> else: Tofurbot())
>
> menu.append(gotHerring() ? popHerring() : gotAnyFish() ?
> popAnyFish() : Tofurbot())
>
> Here, I like the way the verbose syntax politely spreads itself out
> over multiple lines. In C, I never know where to put the line breaks.
Ouch. You're bringing up another valid issue: whether to support
"elif". I think if we go with (if ... then ... else ...) or (if ...:
... else: ...) we'll have to support elif as well:
(if ... then ... elif ... then ... else ...)
or
(if ...: ... elif ...: ... else: ...)
I really don't like the latter.
Here's a suggestion for a way to decide between a "wordy" version or
C-style "?:" -- if we abandon and/or in favor of &&/||, we should also
go with ?:; if we keep and/or, we should use a keyword-based
conditional as well. Since so far the feedback is overwhelmingly in
favor of keeping and/or, I think that settles the case in favor of a
wordy version. My preference then would be
(if ... then ... elif ... then ... else ...)
which gives my a nice nostalgic feeling because (except for the elif
part) Algol-60 had the same thing -- the first programming language I
ever learned. :)
(Oh, and a way to decide between colon or no colon: we're not using
colons in list comps and genexprs either.)
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
Dear all,
We've found a problem using urllib.urljoin when upgrading
from python 2.3 to 2.4. It no longer joins a particular
corner case of URLs correctly (we think!).
The code appears to follow the algorithm (from
http://www.ietf.org/rfc/rfc1808.txt) for resolving urls
almost exacty...
I believe the problem occurs when reaching "step 5" (approx
line 160) which will happen if the embedded url has no
scheme, netloc or path (and is nonempty).
Following the algorithm the resulting url should now be
returned using the base urls scheme,netloc and path but the
embedded urls params / query (if present else set to base
ones) which follows in 2.3:
if not path:
if not params:
params = bparams
if not query:
query = bquery
return urlunparse((scheme, netloc, bpath,
params, query, fragment))
However in 2.4, even if the embedded urls path is empty,
unless the params and query segments are empty too, flow
passes to step 6.
if not (path or params or query):
return urlunparse((scheme, netloc, bpath,
bparams, bquery, fragment))
and thus the last segment of the base path will be removed
in order to append the embedded url's path, but the path is
empty! and so the resulting path is returned incorrectly.
Can you tell me if this was a deliberate decision to move
from following the algorithm? If so then we'll work around it.
--
##############################################################################
Andrew Edmondson
PGP Key: http://search.keyserver.net:11371/pks/lookup?op=get&search=0xCEE814DC
PGP Fingerprint: 7B32 4D1E AC4F 29E2 9EAA 9550 1A3D BBA4 CEE8 14DC