Hi all,
I've updated PEP-0397 to try and address some of the comments from
the last draft. I've checked the new version into hg, so you can find a
full diff there, but the key items I've changed are:
* Spelled out the "version qualifier" rules for the shebang lines.
* Spelled out some custo
Hi,
I broke recently all tests of CJK encodings (#12057) in Python 2.7 (sorry, it
is now fixed). But the "x86 XP-4 2.7" buildbot is green, I don't understand
how (the bug was not fixed in the build 894):
http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%202.7/builds/894
This build doe
Hello
I am about to merge packaging in the stdlib, and we will continue our
work there :)
The impact is:
- addition of Lib/packaging
- addition of test/test_packaging.py
- changes in Lib/sysconfig.py
- addition of Lib/sysconfig.cfg
For the last one, I would like to make sure again that everyone
Am 17.05.2011 17:36, schrieb Tarek Ziadé:
> The next change I have planned is to allow several levels of
> configuration, like distutils.cfg does. sysconfig.py will look for a
> sysconfig.cfg file in these places:
>
> 1. the current working directory -- so can be potentially included in
> a projec
On Tue, May 17, 2011 at 19:40, Jeremy Dunck wrote:
> So, to start with, is there a maintainer for the json module, or how
> should I go about discussing implementing this solution?
Your subject states that there is an actual bug in the json module,
but your message fails to mention any actual bug
On 17 May, 2011, at 17:36, Tarek Ziadé wrote:
> Hello
>
> I am about to merge packaging in the stdlib, and we will continue our
> work there :)
>
> The impact is:
>
> - addition of Lib/packaging
> - addition of test/test_packaging.py
> - changes in Lib/sysconfig.py
> - addition of Lib/sysconfi
On Tue, May 17, 2011 at 1:21 PM, Dirkjan Ochtman wrote:
> On Tue, May 17, 2011 at 19:40, Jeremy Dunck wrote:
>> So, to start with, is there a maintainer for the json module, or how
>> should I go about discussing implementing this solution?
>
> Your subject states that there is an actual bug in t
On behalf of the Python development team, I am pleased to announce the
first release candidate of Python 3.2.1.
Python 3.2.1 will the first bugfix release for Python 3.2, fixing over 120
bugs and regressions in Python 3.2.
For an extensive list of changes and features in the 3.2 line, see
ht
Le mardi 17 mai 2011 à 17:36 +0200, Tarek Ziadé a écrit :
> - addition of Lib/packaging
> - addition of test/test_packaging.py
> - changes in Lib/sysconfig.py
> - addition of Lib/sysconfig.cfg
Does setup.py continue to use the "old" distutils module?
I fixed recently some bugs in distutils. Shoul
On Tue, May 17, 2011 at 7:21 PM, Ronald Oussoren wrote:
...
>> 1. the current working directory -- so can be potentially included in
>> a project source release
>
> Does this mean that python behaves differently when there happens to be a
> sysconfig.cfg file in the current working directory? Tha
On Tue, May 17, 2011 at 10:40 PM, Victor Stinner
wrote:
> Le mardi 17 mai 2011 à 17:36 +0200, Tarek Ziadé a écrit :
>> - addition of Lib/packaging
>> - addition of test/test_packaging.py
>> - changes in Lib/sysconfig.py
>> - addition of Lib/sysconfig.cfg
>
> Does setup.py continue to use the "old"
On Tue, May 17, 2011 at 6:42 PM, Christian Heimes wrote:
> Am 17.05.2011 17:36, schrieb Tarek Ziadé:
>> The next change I have planned is to allow several levels of
>> configuration, like distutils.cfg does. sysconfig.py will look for a
>> sysconfig.cfg file in these places:
>>
>> 1. the current w
The bytes type in Python 3 does not feel very consistent.
For example:
--> some_var = 'abcdef'
--> some_var
'abcdef'
--> some_var[3]
'd'
--> some_other_var = b'abcdef'
--> some_other_var
b'abcdef'
--> some_other_var[3]
100
On the one hand we have the 'bytes are ascii data' type interface, and
2011/5/17 Ethan Furman :
> Considering that ord() still works fine, I'm not sure why it was done this
> way.
I agree that this change was unfortunate and not too useful in practice.
>
> Is there code out there that is using this "list of int's" interface, or is
> there time to make changes to byt
On May 17, 2011, at 5:27 PM, Ethan Furman wrote:
> The bytes type in Python 3 does not feel very consistent.
>
> For example:
>
> --> some_var = 'abcdef'
> --> some_var
> 'abcdef'
> --> some_var[3]
> 'd'
> --> some_other_var = b'abcdef'
> --> some_other_var
> b'abcdef'
> --> some_other_var[3]
>
In article ,
Tarek Ziadé wrote:
> On Tue, May 17, 2011 at 10:40 PM, Victor Stinner
> wrote:
> > Le mardi 17 mai 2011 à 17:36 +0200, Tarek Ziadé a écrit :
> >> - addition of Lib/packaging
> >> - addition of test/test_packaging.py
> >> - changes in Lib/sysconfig.py
> >> - addition of Lib/sysconfig
On Wed, May 18, 2011 at 1:25 AM, Ned Deily wrote:
...
> Just to be clear: what about for the build of the interpreter itself,
> i.e. its setup.py for the standard library extension modules? Will the
> existing distutils code continue to be used for that? Or is it being
> replaced by code in pack
In article ,
Tarek Ziadé wrote:
> On Wed, May 18, 2011 at 1:25 AM, Ned Deily wrote:
> > Just to be clear: what about for the build of the interpreter itself,
> > i.e. its setup.py for the standard library extension modules? Will the
> > existing distutils code continue to be used for that? [...
On Wed, May 18, 2011 at 8:27 AM, Ethan Furman wrote:
> On the one hand we have the 'bytes are ascii data' type interface, and on
> the other we have the 'bytes are a list of integers between 0 - 256'
> interface.
No. Bytes are a list of integers between 0-256. End of story. Using
them to represen
On Wed, May 18, 2011 at 3:13 PM, Nick Coghlan wrote:
> On Wed, May 18, 2011 at 8:27 AM, Ethan Furman wrote:
>> On the one hand we have the 'bytes are ascii data' type interface, and on
>> the other we have the 'bytes are a list of integers between 0 - 256'
>> interface.
>
> No. Bytes are a list o
On Wed, May 18, 2011 at 1:23 PM, Robert Collins
wrote:
> The Python 2 confusion was deplorable, but it doesn't make the Python
> 3 situation better: its different, but still very awkward for people
> to write code that is correct and fast in.
When Python 3 goes wrong, it raises exceptions or exec
Ethan Furman wrote:
On the one hand we have the 'bytes are ascii data' type interface, and
on the other we have the 'bytes are a list of integers between 0 - 256'
interface.
I think the weird part is that there exists a literal for
writing a byte array as an ascii string, and furthermore
that
Robert Collins wrote:
urlparse converting bytes to 'str' to operate on them is
at best a kludge - you're forcing 5 times the storage (the original
bytes + 4 bytes-per-byte when its decoded into unicode)
That is itself an implementation detail of current Python,
though, due to it only having one
On 5/17/2011 10:39 PM, Greg Ewing wrote:
Personally I think that the default literal syntax for
bytes, and also the form produced by repr(), should have
been something more neutral, such as hex, with the ascii
form available for use when it makes sense.
Much nicer would be
some_var = x'dea
Hi All,
A friend of mine is coming over to Python and asked a question I thought
would have a better answer than it appears to:
How do I know which version of Python a PEP lands in?
I was expecting there to be a note at the bottom of the PEP, 342 in this
case, but that doesn't appear to be t
Hi,
2011/5/18 Chris Withers :
> A friend of mine is coming over to Python and asked a question I thought
> would have a better answer than it appears to:
>
> How do I know which version of Python a PEP lands in?
>
> I was expecting there to be a note at the bottom of the PEP, 342 in this
> case, b
That's great, but where is the list if changes?
--
anatoly t.
On Tue, May 17, 2011 at 9:50 PM, Georg Brandl wrote:
> On behalf of the Python development team, I am pleased to announce the
> first release candidate of Python 3.2.1.
>
> Python 3.2.1 will the first bugfix release for Python 3.2, f
Hi,
2011/5/18 anatoly techtonik :
> That's great, but where is the list if changes?
All changes are always listed in the Misc/NEWS file.
A "Change log" link on every download page displays this file.
--
Amaury Forgeot d'Arc
___
Python-Dev mailing list
> How do I know which version of Python a PEP lands in?
You should look at the Python-Version header of the PEP.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://ma
On 18.05.2011 07:39, Greg Ewing wrote:
> Ethan Furman wrote:
>
>> On the one hand we have the 'bytes are ascii data' type interface, and
>> on the other we have the 'bytes are a list of integers between 0 - 256'
>> interface.
>
> I think the weird part is that there exists a literal for
> writi
> Is there code out there that is using this "list of int's" interface
Just in case this isn't clear yet: yes, certainly. Any non-trivial piece
of Python 3 code that has been written already (and there is some) will
have run into that issue.
Regards,
Martin
___
>> That's great, but where is the list if changes?
>
> All changes are always listed in the Misc/NEWS file.
> A "Change log" link on every download page displays this file.
I think it would be good if the release announcement made some
summary statement, though, like "NNN bugs have been fixed, in
2011/5/18 "Martin v. Löwis" :
>> How do I know which version of Python a PEP lands in?
>
> You should look at the Python-Version header of the PEP.
But some PEPs don't have it: 341, 342, 343, 353...
--
Amaury Forgeot d'Arc
___
Python-Dev mailing list
P
On Wed, May 18, 2011 at 4:24 PM, "Martin v. Löwis" wrote:
>> How do I know which version of Python a PEP lands in?
>
> You should look at the Python-Version header of the PEP.
Which is unfortunately missing from some PEPs (including PEP 342). PEP
344 shows where this information *should* be, thou
34 matches
Mail list logo
