Mailman 3 June 2008 - Python-Dev

Python FAQ: Why doesn't Python have a "with" statement?
by Michael Foord June 19, 2008

June 19, 2008

The Python FAQ has the following entry: 4.26 Why doesn't Python have a "with" statement like some other languages? From: http://www.python.org/doc/faq/general/ Even if the content is still relevant (I know nothing of the use of 'with' outside Python), the entry probably needs at least clarifying now that Python does have a 'with' statement. Michael Foord -- http://www.ironpythoninaction.com/ http://www.theotherdelia.co.uk/ http://www.voidspace.org.uk/ http://www.ironpython.info/ http://www.resolverhacks.net/

15 30

Another run at beta one
by Barry Warsaw June 19, 2008

June 19, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I'm going to try again tonight to release beta one for Python 2.6 and 3.0. I'm planning on starting the release at 6pm US/Eastern or 2200 UTC. Right now the Python 2.6 buildbots look pretty good. We have /one/ green buildbot for Python 3.0. That's better than last week at least, but it would be great to get a few more. I know folks have been working hard at this, and I really appreciate it. I think we're looking fairly good on … [View More]

2 3

releasing betas tonight
by Barry Warsaw June 18, 2008

June 18, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There are enough green buildbots and I think all the showstoppers are resolvable, so I'm going ahead and releasing beta 1 tonight. Please refrain from any commits unless I ask you to check something in. We've got a major thunderstorm blowing through right now, but when it clears I'll be on irc.freenode.net #python-dev. I'll start making the release as soon as I get on, and feel free to ask any questions. - -B -----BEGIN PGP SIGNATURE---… [View More]

1 0

Epoch and Platform
by Curt Hagenlocher June 18, 2008

June 18, 2008

The documentation for the time module says that "the epoch is the point where the time starts. On January 1st of that year, at 0 hours, the ``time since the epoch'' is zero. For Unix, the epoch is 1970. To find out what the epoch is, look at gmtime(0)." This confirms that the epoch is platform-specific. As such, the only legal uses of the timestamp should be 1) comparing with another timestamp to determine elapsed time in seconds 2) passing to another standard Python library function which … [View More]

4 12

Re: [Python-Dev] [Python-checkins] r64360 - python/trunk/Lib/lib2to3/refactor.py
by "Martin v. Löwis" June 18, 2008

June 18, 2008

>> Please never commit to python/trunk/Lib/lib2to3. >> Instead, commit to sandbox/trunk/2to3, and merge >> that using svnmerge. > > Could you explain that policy? Why isn't 2to3 maintained in the > trunk but in the sandbox? Or maybe more general: Where can I find > more information on the svn directory layout? It started off as a sandbox project, also with the intent of releasing it separately. At PyCon 2008, I restructured it introducing lib2to3, which I then … [View More]

1 0

Merging changes before beta
by Amaury Forgeot d'Arc June 17, 2008

June 17, 2008

Hello, I am in the process of merging changes from trunk to the py3k branch. (If somebody else is already doing it, please tell me quickly!) IMO it would be better to have the beta versions in sync; the 2.6->3.0 migration should not be a regression! I will integrate the changes that are either simple, or that I can understand, or have unit tests. The changes I will skip are (for the moment): - r64114 (gregory.p.smith): a bunch of checks for integer overflows, contributed by Google. This … [View More]

2 1

Error building python3.0 under OS X
by Brad Miller June 17, 2008

June 17, 2008

I have been updating the 3.0 source using bzr and after my latest bzr pull I get an error on make install. I'm running 10.5.3. ./configure --enable-framework make make install ... running install_egg_info Writing /Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/lib-dynload/Python-3.0a5_-py3.0.egg-info ln -fs "../../../Python" "/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/config/libpython3.0.a" cd Mac && make installmacsubtree DESTDIR="" … [View More]

1 0

Re: [Python-Dev] Epoch and Platform
by Forest June 17, 2008

June 17, 2008

ISTR using a Microsoft C compiler in the early/mid 1990s whose runtime library used an unusual epoch. I don't recall any others straying from the Unix way, but then again, I haven't been looking for such quirks. Guido wrote: > > ISTR that we force the epoch to be 1970 on all major platforms -- or > perhaps it happens to be 1970 even on Windows when using MS's C > runtime. > > On Mon, Jun 16, 2008 at 4:08 PM, Curt Hagenlocher <curt(a)hagenlocher.org> > wrote: >… [View More]> The documentation for the time module says that "the epoch is the point >> where the time starts. On January 1st of that year, at 0 hours, the >> ``time >> since the epoch'' is zero. For Unix, the epoch is 1970. To find out what >> the >> epoch is, look at gmtime(0)." This confirms that the epoch is >> platform-specific. As such, the only legal uses of the timestamp should >> be >> >> 1) comparing with another timestamp to determine elapsed time in seconds >> 2) passing to another standard Python library function which expects a >> timestamp >> 3) as a source of randomness. >> >> However, the following files in the standard library have hardcoded the >> assumption that the Python epoch will always be the same as the Unix >> epoch: >> In gzip.py, method GzipFile._write_gzip_header >> In tarfile.py, method _Stream._init_write_gz >> In uuid.py, function uuid1 >> >> Additionally, the following files in the standard library have hardcoded >> the >> assumption that the Python epoch will cause timestamps to fall within >> the >> range of a 32-bit unsigned integer value: >> In imputil.py, function _compile >> In py_compile.py, function compile >> >> So there's some kind of a potential discrepancy here, albeit a minor >> one. >> This discrepancy can be resolved in one of at least three ways: >> >> 1) The documentation for the time module is wrong, and the epoch for >> Python >> (at least versions 2.x) should be the Unix epoch. >> 2) These library functions are slightly wrong and should be modified by >> subtracing an "epoch offset" before doing other calculations. This >> offset >> can be calculated as "time.mktime((1970, 1, 1, 0, 0, 0, 3, 1, 0)) - >> time.timezone". >> 3) These library files should be considered part of the >> platform-specific >> implementation, and an alternate platform should provide its own version >> of >> these files if necessary. >> >> Any thoughts on this? >> >> From the perspective of implementing IronPython, I'd prefer that the >> answer >> is 1 or 2 -- but mainly I just want to be as compatible with "the spec" >> as >> possible, while respecting CLR-specific norms for functionality which is >> left up to individual implementations. >> >> -- >> Curt Hagenlocher >> curt(a)hagenlocher.org [View Less]

1 0

Blow your mind
by Barry Warsaw June 17, 2008

June 17, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A colleague just forward this to me and it blew my fscking mind to smithereens. It also brings back a lot of memories. Enjoy! - -Barry http://www.vimeo.com/1093745 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSFbK8XEjvBPtnXfVAQLPhwP/XQitqKSHHHUsYyrqN77G2FfIK0adyGNI /NUY0DGJQUKrL0Wy+LQQzXUqY0B9a2uk6hxyyA7qWYzd57/l7JCGCgWdEJPhOyxb Y8LW1N9z2SqdngaZHrQz1j5rRj5x2BFZpwt9/c/fqhbBhXIUrLnX/CZ342jQzneL WrKzvqemGlY= =JSCL -----END PGP SIGNATURE-----

5 4

Error building 3.0 on OS-X
by Brad Miller June 17, 2008

June 17, 2008

I have been updating the 3.0 source using bzr and after my latest bzr pull I get an error on make install. I'm running 10.5.3. ./configure --enable-framework make make install ... running install_egg_info Writing /Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/lib-dynload/Python-3.0a5_-py3.0.egg-info ln -fs "../../../Python" "/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/config/libpython3.0.a" cd Mac && make installmacsubtree DESTDIR="" … [View More]

1 0