Am 19.11.2010 03:23, schrieb Benjamin Peterson:
2010/11/18 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/10 18:32, Martin v. Löwis wrote:
In general, I'm *also* concerned about the lack of volunteers that
are interested in working on the infrastructure. I
Please see this defect:
http://bugs.python.org/issue10430
It would appear that the digest and hexdigest for sha, is wrong on little
endian machines.
There certainly is a discrepancy between little and big endian ones,
irrespective of which one is right
Any thoughts?
K
On Fri, Nov 19, 2010 at 5:43 PM, Georg Brandl g.bra...@gmx.net wrote:
Am 19.11.2010 03:23, schrieb Benjamin Peterson:
2010/11/18 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/10 18:32, Martin v. Löwis wrote:
In general, I'm *also* concerned about the lack of
- date Hg will be available for write access (it should be frozen for
a while, to give the folks doing the conversion a chance to make sure
buildbot is back up and run, commit emails are working properly, etc)
I would target the build slaves to the Mercurial repository already in
the testing
On Sat, Nov 20, 2010 at 12:46 AM, Barry Warsaw ba...@python.org wrote:
On Nov 19, 2010, at 11:50 PM, Nick Coghlan wrote:
- date SVN will go read only
Please note that svn cannot be made completely read-only. We've already
decided that versions already in maintenance or security-only mode
On Fri, Nov 19, 2010 at 15:56, Nick Coghlan ncogh...@gmail.com wrote:
That's enough to make folks like me somewhat nervous as to whether or
not we're actually going to have a usable source control system come
December 12.
Yes, I've been negligent about updating the PEP. I'll try do so next
Am 19.11.2010 08:58, schrieb Martin v. Löwis:
Am 19.11.2010 03:23, schrieb Benjamin Peterson:
2010/11/18 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/10 18:32, Martin v. Löwis wrote:
In general, I'm *also* concerned about the lack of volunteers that
are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/19/2010 7:50 AM, Nick Coghlan wrote:
On Fri, Nov 19, 2010 at 5:43 PM, Georg Brandl g.bra...@gmx.net wrote:
Am 19.11.2010 03:23, schrieb Benjamin Peterson:
2010/11/18 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
Am 19.11.2010 16:00, schrieb Dirkjan Ochtman:
On Fri, Nov 19, 2010 at 15:56, Nick Coghlan ncogh...@gmail.com wrote:
That's enough to make folks like me somewhat nervous as to whether or
not we're actually going to have a usable source control system come
December 12.
Yes, I've been
I was recently surprised to learn that chr(i) can produce a string of
length 2 in python 3.x. I suspect that I am not alone finding this
behavior non-obvious given that a mistake in Python manual stating the
contrary survived several releases. [1] Note that I am not arguing
that the change was
Am 19.11.2010 15:36, schrieb Martin v. Löwis:
- date Hg will be available for write access (it should be frozen for
a while, to give the folks doing the conversion a chance to make sure
buildbot is back up and run, commit emails are working properly, etc)
I would target the build slaves to
ACTIVITY SUMMARY (2010-11-12 - 2010-11-19)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open2549 (+23)
closed 19694 (+43)
total 22243 (+66)
Open issues
Am 19.11.2010 15:46, schrieb Barry Warsaw:
On Nov 19, 2010, at 11:50 PM, Nick Coghlan wrote:
- date SVN will go read only
Please note that svn cannot be made completely read-only. We've already
decided that versions already in maintenance or security-only mode (2.5, 2.6,
2.7, 3.1) will
On Fri, 19 Nov 2010 11:53:58 -0500
Alexander Belopolsky alexander.belopol...@gmail.com wrote:
Since this feature will be first documented in the
Library Reference in 3.2, I wonder if it will be appropriate to
mention it in What's new in 3.2?
No, since it's not new in 3.2. No need to further
On Nov 19, 2010, at 06:12 PM, Georg Brandl wrote:
Am 19.11.2010 15:46, schrieb Barry Warsaw:
On Nov 19, 2010, at 11:50 PM, Nick Coghlan wrote:
- date SVN will go read only
Please note that svn cannot be made completely read-only. We've already
decided that versions already in maintenance
On Fri, 19 Nov 2010 12:41:58 -0500
Barry Warsaw ba...@python.org wrote:
Really? I can understand this for security-only branches (commits there will
be rare, and equivalent commits to the Mercurial branches can be made by
others than the release managers, in order to keep history consistent).
I don't understand all the worry about sys.subversion. It's not like
it's useful to anybody else than us, and I think it should have been
named sys._subversion instead. There's no point in making API-like
promises about which DVCS, bug tracker or documentation toolset we use
for our workflow.
On Fri, Nov 19, 2010 at 05:50, Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Nov 19, 2010 at 5:43 PM, Georg Brandl g.bra...@gmx.net wrote:
Am 19.11.2010 03:23, schrieb Benjamin Peterson:
2010/11/18 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/10 18:32,
Hi,
On Friday 19 November 2010 17:53:58 Alexander Belopolsky wrote:
I was recently surprised to learn that chr(i) can produce a string of
length 2 in python 3.x.
Yes, but only on narrow build. Eg. Debian and Ubuntu compile Python 3.1 in
wide mode (sys.maxunicode == 1114111).
I suspect that
Maybe I misremembered Martin's suggestion, and he was only talking about
security releases.
Technically, I was only talking about 2.5. For each branch, the
respective release manager should make a decision. For 2.5 and 2.6,
it's been decided; Benjamin has not yet announced plans how 2.7 and 3.1
I don't understand all the worry about sys.subversion.
Really? For a security release, there should be *zero* chance that it
breaks existing applications, unless the application relies on the
security bug that has been fixed. By zero chance, I mean absolutely
no chance, never. I'm pretty sure
Am 19.11.2010 22:35, schrieb Martin v. Löwis:
I don't understand all the worry about sys.subversion.
Really? For a security release, there should be *zero* chance that it
breaks existing applications, unless the application relies on the
security bug that has been fixed. By zero chance, I
Le vendredi 19 novembre 2010 à 22:35 +0100, Martin v. Löwis a écrit :
I don't understand all the worry about sys.subversion.
Really? For a security release, there should be *zero* chance that it
breaks existing applications,
It should have been clear that my message explicitly excluded
In my opinion, the question is more what was it not fixed in Python2. I
suppose
that the answer is something ugly like backward compatibility or
historical
reasons :-)
No, there was a deliberate decision to not support that, see
http://www.python.org/dev/peps/pep-0261/
There had been a
Hi,
On 19/11/2010 18.10, alexander.belopolsky wrote:
Author: alexander.belopolsky
Date: Fri Nov 19 17:09:58 2010
New Revision: 86530
Log:
Issue #4153: Updated Unicode HOWTO.
Modified:
python/branches/py3k/Doc/howto/unicode.rst
Modified: python/branches/py3k/Doc/howto/unicode.rst
2010/11/19 Martin v. Löwis mar...@v.loewis.de:
Maybe I misremembered Martin's suggestion, and he was only talking about
security releases.
Technically, I was only talking about 2.5. For each branch, the
respective release manager should make a decision. For 2.5 and 2.6,
it's been decided;
Victor Stinner wrote:
Hi,
On Friday 19 November 2010 17:53:58 Alexander Belopolsky wrote:
I was recently surprised to learn that chr(i) can produce a string of
length 2 in python 3.x.
Yes, but only on narrow build. Eg. Debian and Ubuntu compile Python 3.1 in
wide mode (sys.maxunicode ==
It'S rather common to confuse a transfer encoding with a storage format.
UCS2 and UCS4 refer to code units (the storage format).
Actually, they don't. Instead, they refer to coded character sets,
in W3C terminology: mapping of characters to natural numbers. See
So maybe this is the wrong forum, if so please tell me what the right
forum is for each of the various pieces. I'm assuming that I should
file some bugs in the tracker, but I'm not exactly sure whether to file
them on cgitb, http.server, or subprocess, or all of the above. Pretty
sure there
Martin v. Löwis writes:
The term UCS-2 is a character set that can encode only encode 65536
characters; it thus refers to Unicode 1.1. According to the Unicode
Consortium's FAQ, the term UCS-2 should be avoided these days.
So what do you propose we call the Python implementation? You can
On Fri, Nov 19, 2010 at 20:01, benjamin.peterson python-check...@python.org
wrote:
Author: benjamin.peterson
Date: Sat Nov 20 03:01:45 2010
New Revision: 86540
Log:
c89 declarations
Modified:
python/branches/py3k/Parser/asdl_c.py
python/branches/py3k/Python/Python-ast.c
Modified:
On 11/19/2010 7:48 PM, Glenn Linderman wrote:
One of the cgitb outputs from my attempt to serve the binary file
claims that my CGI script's output file (which comes from a subprocess
PIPE) is a TextIOWrapper with encoding cp1252. Maybe that is the
default that comes when a new Python is
32 matches
Mail list logo
