[Python-Dev] next beta
Barry Warsaw python.org> writes: > > I agree. Our last beta is scheduled for this wednesday Are you sure? According to http://mail.python.org/pipermail/python-3000/2008-July/014269.html, it's scheduled for August 23rd. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] next beta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 11, 2008, at 5:51 AM, Antoine Pitrou wrote: Barry Warsaw python.org> writes: I agree. Our last beta is scheduled for this wednesday Are you sure? According to http://mail.python.org/pipermail/python-3000/2008-July/014269.html , it's scheduled for August 23rd. Ah darn, that's a typo in the PEP. I definitely meant August 13, as the Google calendar shows. Do we think we can be ready for beta3 this Wednesday? If not, I'd rather stick to a weekday release and do it on Wednesday August 20th. Let me know what you think. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSKAwI3EjvBPtnXfVAQLumgQAqq6Vmk9qMQQRQkapppNPkypj8IuJiRAN MSCHi9iEj0RP4XpOuXF6oLAOJPajsabnC13J8Zu/tPqnrKR6gwTm/PG/6CDDi5tv JqNQJwBWyXOT56TtDxXNaIy2HIS2Klu6uqNUXoUrGdLuBskWeNBWlj87GKs0ozhq EfgXVbdl0+Y= =ZZd7 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] next beta
Barry Warsaw python.org> writes: > > Ah darn, that's a typo in the PEP. I definitely meant August 13, as > the Google calendar shows. Ah, am I the only one *not* to use Google calendar? :) > Do we think we can be ready for beta3 this Wednesday? If not, I'd > rather stick to a weekday release and do it on Wednesday August 20th. > Let me know what you think. There are quite a few showstoppers, a number of them non-trivial, in the bug tracker. I'm not very optimistic for a release this Wednesday. By the way, I need your pronouncement on http://bugs.python.org/issue2834 cheers Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] next beta
On Mon, Aug 11, 2008 at 12:50:16PM +, Antoine Pitrou wrote: > Ah, am I the only one *not* to use Google calendar? :) Certainly, no! (-: Oleg. -- Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Resource flag for unicode memory error tests?
Currently running the test suite, even without any resource flags, renders my machine unusable for at least part of the test execution. The main culprit appears to be the checks for expected memory errors in test_unicode. Does anyone have any objections to making the offending test dependent on a resource flag after beta 3 is out the door? Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Base-85
On Aug 2, 2008, at 13:58 PM, Antoine Pitrou wrote: Martin v. Löwis v.loewis.de> writes: P.S. Just in case it isn't clear: I would oppose any specific proposal to add this Ascii85 algorithm to the standard library. It would sound like we don't have any real problems to solve. According to Wikipedia, "its main modern use is in Adobe's PostScript and Portable Document Format file formats". ... git ... mercurial ... bzr It's sort of too bad about the April Fool's RFC, because now people tend to think that an encoding with a non-power-of-2 base is just a joke. I had to overcome that when working with my programming partner, but he eventually decided that base-62 was indeed a useful encoding for our purposes. :-) I've written a few ascii encoders over the years, mostly in Python, plus an optimized C version of base-32 (with a real live Duff's Device): base62.py: http://allmydata.org/source/z-base-62/trunk-hashedformat/z-base-62/ base62/base62.py base36.py: http://allmydata.org/source/z-base-36/trunk-hashedformat/z-base-36/ base36/base36.py base32.py: http://allmydata.org/source/z-base-32/trunk-hashedformat/base32/ base32/base32.py base32.c: http://allmydata.org/source/z-base-32/trunk-hashedformat/base32/base32.c Regards, Zooko ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Base-85
On Mon, Aug 11, 2008 at 8:43 AM, zooko <[EMAIL PROTECTED]> wrote: > On Aug 2, 2008, at 13:58 PM, Antoine Pitrou wrote: > >> Martin v. Löwis v.loewis.de> writes: >>> >>> P.S. Just in case it isn't clear: I would oppose any specific proposal >>> to add this Ascii85 algorithm to the standard library. It would sound >>> like we don't have any real problems to solve. >> >> According to Wikipedia, "its main modern use is in Adobe's PostScript and >> Portable Document Format file formats". > > ... git ... mercurial ... bzr > > It's sort of too bad about the April Fool's RFC, because now people tend to > think that an encoding with a non-power-of-2 base is just a joke. The best April Fool's jokes (imo) are the ones that are obviously silly right off, but that 1) work, 2) no sane person would ever use, and 3) offer up something useful hidden in the joke. The April Fool's RFC fits the bill perfectly, because out of it all comes base85, which is an actual improvement over base64 (25% expansion of data vs. 33%). That some people missed that part of the joke isn't terribly surprising (I have in other situations). - Josiah > I had to overcome that when working with my programming partner, but he > eventually decided that base-62 was indeed a useful encoding for our > purposes. :-) > > I've written a few ascii encoders over the years, mostly in Python, plus an > optimized C version of base-32 (with a real live Duff's Device): > > base62.py: > > http://allmydata.org/source/z-base-62/trunk-hashedformat/z-base-62/base62/base62.py > > base36.py: > > http://allmydata.org/source/z-base-36/trunk-hashedformat/z-base-36/base36/base36.py > > base32.py: > > http://allmydata.org/source/z-base-32/trunk-hashedformat/base32/base32/base32.py > > base32.c: > > http://allmydata.org/source/z-base-32/trunk-hashedformat/base32/base32.c > > Regards, > > Zooko > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/josiah.carlson%40gmail.com > ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] next beta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 11, 2008, at 8:27 AM, Barry Warsaw wrote: Ah darn, that's a typo in the PEP. I definitely meant August 13, as the Google calendar shows. Do we think we can be ready for beta3 this Wednesday? If not, I'd rather stick to a weekday release and do it on Wednesday August 20th. Let me know what you think. It sounds like Wednesday August 13th will not be feasible, so we'll do beta 3 on Wednesday August 20th. I've updated both the PEP and the Google Calendar. Thanks, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSKDE+XEjvBPtnXfVAQIATwQApbwwrof862rrH8YU0QP3gVENMU4TRpZx 9jdnJk+OZJpFo74XitnrWDsprY1r/lJdGaLnebfg9DztbjHVgCWvkRNXI7qIbRpf QfSeMusrhVwDNITBhJ/0j+A1phWUQG6CU0dez+iKvCJUcohgDlFmlIsw8tCkgDYG On7b7ZKlHd8= =kLcU -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
