Re: [Python-Dev] [RELEASED] Python 3.4.0 - missing information on the web

2014-03-17 Thread Jurko Gospodnetić 

  Hi.

On 17.3.2014. 7:29, Larry Hastings wrote:

On behalf of the Python development team, I'm thrilled to announce
the official release of Python 3.4.
[...lots of great enhancements snipped...]


  Just noted that 'https://www.python.org/download' still lists Python 
3.4.0rc2 as the latest 'testing release' (and does not mention the

final Python 3.4.0 release at all).

  Best regards,
Jurko Gospodnetić


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Nick Coghlan 
On 17 March 2014 16:29, Larry Hastings  wrote:
>
> On behalf of the Python development team, I'm thrilled to announce
> the official release of Python 3.4.

Huzzah! Thanks for all the work on the release wrangling Larry (and
the rest of the release team), as well as to everyone that contributed
to the many fine changes in this release :)

Cheers,
Nick.

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Ben Finney 
Larry Hastings  writes:

> On behalf of the Python development team, I'm thrilled to announce
> the official release of Python 3.4.

Hooray! This is great news, the new release looks like a major step
forward.

Thank you to everyone involved with making the Python 3.4 release
happen.

-- 
 \  “Why should I care about posterity? What's posterity ever done |
  `\for me?” —Groucho Marx |
_o__)  |
Ben Finney

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Victor Stinner 
Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only
accept security fixes, right?

Victor
Le 17 mars 2014 07:48, "Larry Hastings"  a écrit :

>
>
> The "3.4" branch is now checked in.  It contains all the 3.4 releases
> since 3.4.0rc1.  Its current state is effectively 3.4.1.
>
> The "default" branch is now 3.5.
>
> Cry havoc, and let slip the dogs of war,
>
>
> */arry*
>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
>
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0 - missing information on the web

2014-03-17 Thread Ned Deily 
In article ,
 Jurko Gospodnetić  wrote:
>Just noted that 'https://www.python.org/download' still lists Python 
> 3.4.0rc2 as the latest 'testing release' (and does not mention the
> final Python 3.4.0 release at all).

Thanks for the report.  That and other download pages should now be 
up-to-date.

-- 
 Ned Deily,
 [email protected]

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0 - PEP 429 needs updating?

2014-03-17 Thread Jurko Gospodnetić 

  Hi.

On 17.3.2014. 11:35, Ned Deily wrote:

Thanks for the report.  That and other download pages should now be
up-to-date.


  Something similar - does PEP 429 (Python 3.4 Release Schedule) need 
to be updated? It still lists 3.4.0rc3 as a 'future release'.


  Best regards,
Jurko Gospodnetić


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] getattr vs hashattr

2014-03-17 Thread Brett Cannon 
On Fri, Mar 14, 2014 at 3:01 PM, Chris Withers wrote:

> On 03/12/2014 04:49 PM, Chris Angelico wrote:
>>
>>> You can use hasattr() in place of AttributeError
>>>
>>
> Is that true now? It used to be that hasattr swallowed all exceptions
> rather than just AttributeError making is a very dangerous weapon for
> anything (such as an orm or odb) that might do something interesting when
> you try and get an attribute from it.
>

Changed in Python 3.2: http://docs.python.org/3.2/whatsnew/3.2.html


>
> On 12/03/2014 21:37, Tres Seaver wrote:
>
>> I use:
>>
>>   getattr(subject, attrname, default)?
>>
>> *all the time*.
>>
>
> On this one, did anything ever come of making getattr have a default
> default of None?


No. If you want None returned as the default you still need to specify that
to allow for those APIs where the attribute can have a value of None but
you still want it to raise an AttributeError if the attribute isn't there.

-Brett


>
>
> Chris
>
> --
> Simplistix - Content Management, Batch Processing & Python Consulting
> - http://www.simplistix.co.uk
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> brett%40python.org
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Brett Cannon 
On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner wrote:

> Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only
> accept security fixes, right?
>

Typically we do one last release before shutting the last bugfix branch
down, but that's Georg's call since 3.3.5 was released so recently.

-Brett


> Victor
> Le 17 mars 2014 07:48, "Larry Hastings"  a écrit :
>
>>
>>
>> The "3.4" branch is now checked in.  It contains all the 3.4 releases
>> since 3.4.0rc1.  Its current state is effectively 3.4.1.
>>
>> The "default" branch is now 3.5.
>>
>> Cry havoc, and let slip the dogs of war,
>>
>>
>> */arry*
>>
>> ___
>> python-committers mailing list
>> [email protected]
>> https://mail.python.org/mailman/listinfo/python-committers
>>
>>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
>
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Benjamin Peterson 


On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote:
> On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner
> wrote:
> 
> > Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only
> > accept security fixes, right?
> >
> 
> Typically we do one last release before shutting the last bugfix branch
> down, but that's Georg's call since 3.3.5 was released so recently.

Given that, I propose 3.3 goes into security fix mode immediately.
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Tres Seaver 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/17/2014 11:18 AM, Benjamin Peterson wrote:
> 
> 
> On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote:
>> On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner 
>> wrote:
>> 
>>> Until when should we fix bugs in the branch 3.3? Branches 3.1 and
>>> 3.2 only accept security fixes, right?
>>> 
>> 
>> Typically we do one last release before shutting the last bugfix
>> branch down, but that's Georg's call since 3.3.5 was released so
>> recently.
> 
> Given that, I propose 3.3 goes into security fix mode immediately.

Shouldn't we at least do a review of the open issues against 3.3 first,
particularly those with patches?  E.g. "critcal" / "patch review":

http://bugs.python.org/issue?%40search_text=&ignore=file%3Acontent&title=&%40columns=title&id=&%40columns=id&stage=4&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=17&dependencies=&assignee=&keywords=&priority=2&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40action=search

or "high" / "patch review":

http://bugs.python.org/issue?%40search_text=&ignore=file%3Acontent&title=&%40columns=title&id=&%40columns=id&stage=4&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=17&dependencies=&assignee=&keywords=&priority=3&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40action=search

(OT:  man does that cry out for a URL shortener built in).



Tres.
- -- 
===
Tres Seaver  +1 540-429-0999  [email protected]
Palladion Software   "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMnGFYACgkQ+gerLs4ltQ5o5QCg2YUAmIm5POUXv40VB3DEtJPV
cDMAnR9kjBJV0FaGTYrK9beA0YSDKLhQ
=4yP2
-END PGP SIGNATURE-

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Martin v. Löwis 
Am 17.03.14 16:18, schrieb Benjamin Peterson:
> 
> 
> On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote:
>> On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner
>> wrote:
>>
>>> Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only
>>> accept security fixes, right?
>>>
>>
>> Typically we do one last release before shutting the last bugfix branch
>> down, but that's Georg's call since 3.3.5 was released so recently.
> 
> Given that, I propose 3.3 goes into security fix mode immediately.

+1

Martin


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Yury Selivanov 

Congrats Larry and everybody who worked on 3.4!

Yury


On 2014-03-17, 2:29 AM, Larry Hastings wrote:


On behalf of the Python development team, I'm thrilled to announce
the official release of Python 3.4.


Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements and bug fixes.  Major new features and
changes in the 3.4 release series include:

* PEP 428, a "pathlib" module providing object-oriented filesystem paths
* PEP 435, a standardized "enum" module
* PEP 436, a build enhancement that will help generate introspection
   information for builtins
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard 
library

* PEP 445, a new C API for implementing custom memory allocators
* PEP 446, changing file descriptors to not be inherited by default
   in subprocesses
* PEP 450, a new "statistics" module
* PEP 451, standardizing module metadata for Python's module import 
system

* PEP 453, a bundled installer for the *pip* package manager
* PEP 454, a new "tracemalloc" module for tracing Python memory 
allocations

* PEP 456, a new hash algorithm for Python strings and binary data
* PEP 3154, a new and improved protocol for pickled objects
* PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O


To download Python 3.4.0 visit:

http://www.python.org/download/releases/3.4.0/


This is a production release.  Please report any issues you notice to:

 http://bugs.python.org/


Enjoy!


--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/yselivanov.ml%40gmail.com


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Ryan Gonzalez 
YES!!! +1 to the authors of the statistics and pathlib modules.


On Mon, Mar 17, 2014 at 1:29 AM, Larry Hastings  wrote:

>
> On behalf of the Python development team, I'm thrilled to announce
> the official release of Python 3.4.
>
>
> Python 3.4 includes a range of improvements of the 3.x series, including
> hundreds of small improvements and bug fixes.  Major new features and
> changes in the 3.4 release series include:
>
> * PEP 428, a "pathlib" module providing object-oriented filesystem paths
> * PEP 435, a standardized "enum" module
> * PEP 436, a build enhancement that will help generate introspection
>information for builtins
> * PEP 442, improved semantics for object finalization
> * PEP 443, adding single-dispatch generic functions to the standard library
> * PEP 445, a new C API for implementing custom memory allocators
> * PEP 446, changing file descriptors to not be inherited by default
>in subprocesses
> * PEP 450, a new "statistics" module
> * PEP 451, standardizing module metadata for Python's module import system
> * PEP 453, a bundled installer for the *pip* package manager
> * PEP 454, a new "tracemalloc" module for tracing Python memory allocations
> * PEP 456, a new hash algorithm for Python strings and binary data
> * PEP 3154, a new and improved protocol for pickled objects
> * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
>
>
> To download Python 3.4.0 visit:
>
> http://www.python.org/download/releases/3.4.0/
>
>
> This is a production release.  Please report any issues you notice to:
>
>  http://bugs.python.org/
>
>
> Enjoy!
>
>
> --
> Larry Hastings, Release Manager
> larry at hastings.org
> (on behalf of the entire python-dev team and 3.4's contributors)
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> rymg19%40gmail.com
>



-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
"It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated."
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Giampaolo Rodola' 
The what's new looks truly amazing, with pathlib and asyncio being my
favourite additions.
Thanks for all the hard work.


On Mon, Mar 17, 2014 at 5:57 PM, Ryan Gonzalez  wrote:

> YES!!! +1 to the authors of the statistics and pathlib modules.
>
>
> On Mon, Mar 17, 2014 at 1:29 AM, Larry Hastings wrote:
>
>>
>> On behalf of the Python development team, I'm thrilled to announce
>> the official release of Python 3.4.
>>
>>
>> Python 3.4 includes a range of improvements of the 3.x series, including
>> hundreds of small improvements and bug fixes.  Major new features and
>> changes in the 3.4 release series include:
>>
>> * PEP 428, a "pathlib" module providing object-oriented filesystem paths
>> * PEP 435, a standardized "enum" module
>> * PEP 436, a build enhancement that will help generate introspection
>>information for builtins
>> * PEP 442, improved semantics for object finalization
>> * PEP 443, adding single-dispatch generic functions to the standard
>> library
>> * PEP 445, a new C API for implementing custom memory allocators
>> * PEP 446, changing file descriptors to not be inherited by default
>>in subprocesses
>> * PEP 450, a new "statistics" module
>> * PEP 451, standardizing module metadata for Python's module import system
>> * PEP 453, a bundled installer for the *pip* package manager
>> * PEP 454, a new "tracemalloc" module for tracing Python memory
>> allocations
>> * PEP 456, a new hash algorithm for Python strings and binary data
>> * PEP 3154, a new and improved protocol for pickled objects
>> * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
>>
>>
>> To download Python 3.4.0 visit:
>>
>> http://www.python.org/download/releases/3.4.0/
>>
>>
>> This is a production release.  Please report any issues you notice to:
>>
>>  http://bugs.python.org/
>>
>>
>> Enjoy!
>>
>>
>> --
>> Larry Hastings, Release Manager
>> larry at hastings.org
>> (on behalf of the entire python-dev team and 3.4's contributors)
>> ___
>> Python-Dev mailing list
>> [email protected]
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
>> rymg19%40gmail.com
>>
>
>
>
> --
> Ryan
> If anybody ever asks me why I prefer C++ to C, my answer will be simple:
> "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
> nul-terminated."
>
>
> --
> https://mail.python.org/mailman/listinfo/python-list
>
>


-- 
Giampaolo - http://grodola.blogspot.com
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Antoine Pitrou 
On Mon, 17 Mar 2014 11:44:28 -0400
Tres Seaver  wrote:
> 
> Shouldn't we at least do a review of the open issues against 3.3 first,
> particularly those with patches?  E.g. "critcal" / "patch review":
> 
> http://bugs.python.org/issue?%40search_text=&ignore=file%3Acontent&title=&%40columns=title&id=&%40columns=id&stage=4&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=17&dependencies=&assignee=&keywords=&priority=2&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40action=search

Looking at those, they are nice to fix, but not particularly critical
(and indeed they have been open for quite some time).

> or "high" / "patch review":
> 
> http://bugs.python.org/issue?%40search_text=&ignore=file%3Acontent&title=&%40columns=title&id=&%40columns=id&stage=4&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=17&dependencies=&assignee=&keywords=&priority=3&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40action=search

Ditto here.

Regards

Antoine.


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [RELEASED] Python 3.4.0

2014-03-17 Thread Alioune Dia 
yeah , asyncio is a great module, congrat for all jobs you are doing
--Ad | Dakar


2014-03-17 18:11 GMT+01:00 Giampaolo Rodola' :

> The what's new looks truly amazing, with pathlib and asyncio being my
> favourite additions.
> Thanks for all the hard work.
>
>
> On Mon, Mar 17, 2014 at 5:57 PM, Ryan Gonzalez  wrote:
>
>> YES!!! +1 to the authors of the statistics and pathlib modules.
>>
>>
>> On Mon, Mar 17, 2014 at 1:29 AM, Larry Hastings wrote:
>>
>>>
>>> On behalf of the Python development team, I'm thrilled to announce
>>> the official release of Python 3.4.
>>>
>>>
>>> Python 3.4 includes a range of improvements of the 3.x series, including
>>> hundreds of small improvements and bug fixes.  Major new features and
>>> changes in the 3.4 release series include:
>>>
>>> * PEP 428, a "pathlib" module providing object-oriented filesystem paths
>>> * PEP 435, a standardized "enum" module
>>> * PEP 436, a build enhancement that will help generate introspection
>>>information for builtins
>>> * PEP 442, improved semantics for object finalization
>>> * PEP 443, adding single-dispatch generic functions to the standard
>>> library
>>> * PEP 445, a new C API for implementing custom memory allocators
>>> * PEP 446, changing file descriptors to not be inherited by default
>>>in subprocesses
>>> * PEP 450, a new "statistics" module
>>> * PEP 451, standardizing module metadata for Python's module import
>>> system
>>> * PEP 453, a bundled installer for the *pip* package manager
>>> * PEP 454, a new "tracemalloc" module for tracing Python memory
>>> allocations
>>> * PEP 456, a new hash algorithm for Python strings and binary data
>>> * PEP 3154, a new and improved protocol for pickled objects
>>> * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
>>>
>>>
>>> To download Python 3.4.0 visit:
>>>
>>> http://www.python.org/download/releases/3.4.0/
>>>
>>>
>>> This is a production release.  Please report any issues you notice to:
>>>
>>>  http://bugs.python.org/
>>>
>>>
>>> Enjoy!
>>>
>>>
>>> --
>>> Larry Hastings, Release Manager
>>> larry at hastings.org
>>> (on behalf of the entire python-dev team and 3.4's contributors)
>>> ___
>>> Python-Dev mailing list
>>> [email protected]
>>> https://mail.python.org/mailman/listinfo/python-dev
>>> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
>>> rymg19%40gmail.com
>>>
>>
>>
>>
>> --
>> Ryan
>> If anybody ever asks me why I prefer C++ to C, my answer will be simple:
>> "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
>> nul-terminated."
>>
>>
>> --
>> https://mail.python.org/mailman/listinfo/python-list
>>
>>
>
>
> --
> Giampaolo - http://grodola.blogspot.com
>
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/dia.aliounes%40gmail.com
>
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] peps: The final update to PEP 429, the Python 3.4 release schedule. (I think!)

2014-03-17 Thread Antoine Pitrou 
On Mon, 17 Mar 2014 18:30:53 +0100 (CET)
larry.hastings  wrote:
> +(Beta 1 was also "feature freeze"--no new features beyond this point.)

Famous last words :-)

Regards

Antoine.


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] 3.3 branch is now in security fix mode

2014-03-17 Thread Georg Brandl 
Hi all,

since 3.3.5 and 3.4.0 practically coincided, it is a good point to end the
bugfix maintenance of the 3.3 branch.

Please only commit security-related fixes to 3.3 from now -- like for 3.2 --
and as always, please set tracker issues that relate to security fixes to
"release blocker" priority.

Georg

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] hg branching + log question

2014-03-17 Thread Sean Felipe Wolfe 
I'm getting my feet wet with the cpython sources and Mercurial. I'm a
bit confused -- when I checkout a branch, eg. 3.3, and I do an 'hg
log', why do I see log messages for other branches?

I'm expecting different branches to be kept discreetly. If I switch to
3.3, then I expect to see only 3.3 commits and changes.

Also, what does the branch 'default' mean in this context? Since
cpython is concerned with 3 major concurrent release tracks, why would
there even be a default ? Does it just point to 3.4?

Thanks.


-- 
A musician must make music, an artist must paint, a poet must write,
if he is to be ultimately at peace with himself.
- Abraham Maslow
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] hg branching + log question

2014-03-17 Thread Benjamin Peterson 
On Mon, Mar 17, 2014, at 13:02, Sean Felipe Wolfe wrote:
> I'm getting my feet wet with the cpython sources and Mercurial. I'm a
> bit confused -- when I checkout a branch, eg. 3.3, and I do an 'hg
> log', why do I see log messages for other branches?

That's just the way Mercurial works. If you only want to see messages on
the current branch, do "hg log -b .".

> 
> I'm expecting different branches to be kept discreetly. If I switch to
> 3.3, then I expect to see only 3.3 commits and changes.
> 
> Also, what does the branch 'default' mean in this context? Since
> cpython is concerned with 3 major concurrent release tracks, why would
> there even be a default ? Does it just point to 3.4?

It's what will become 3.5 as of today.
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] trouble building 3.3

2014-03-17 Thread Antoine Pitrou 
On Mon, 17 Mar 2014 12:57:48 -0700
Sean Felipe Wolfe  wrote:

> I'm working on some IDLE oriented bugs and I'm having some trouble
> building the 3.3 branch:
> 
> --
> make: *** No rule to make target `Modules/_operator.c', needed by
> `Modules/_operator.o'.  Stop.
> --
> 
> I did a pull/update, then make clean, configure, and make.

Try "make distclean" and then re-run configure.

Regards

Antoine.


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] hg branching + log question

2014-03-17 Thread Antoine Pitrou 
On Mon, 17 Mar 2014 13:02:23 -0700
Sean Felipe Wolfe  wrote:
> I'm getting my feet wet with the cpython sources and Mercurial. I'm a
> bit confused -- when I checkout a branch, eg. 3.3, and I do an 'hg
> log', why do I see log messages for other branches?

This is a classic hg question, you would get the answer by asking
Mercurial for help: hg log --help :)

Basically, to restrict the log to a given branch, just use the -b
option: hg log -b 3.3.

Regards

Antoine.


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] 'Add/Remove Programs' entry missing for 'current user only' 32-bit installations on 64-bit Windows

2014-03-17 Thread Jurko Gospodnetić 

  Hi all.

  This seems like it should be an 'old' issue, but I have not been able 
to find anything related to it on the web.


  When you install 32-bit CPython 'for the current user only' on 64-bit 
Windows, the installation does not show up in the Windows 'Add/Remove 
Programs' dialog (a.k.a. 'Programs and Features' dialog on Windows 7). 
It does not show up there even for the current user.


  As a consequence it is possible for the user to end up in a situation 
where it is impossible to install a 32-bit Python installation without 
manually cleaning up a previous 32-bit Python installation's Windows 
Installer related registry entries (more on this a bit later).


  I tested this CPython installation behaviour with the following 
CPython versions:

  * 2.3.4 - works correctly
  * 2.5.4 - works correctly
  * 2.6.0 - works correctly
  * 2.6.2 - works correctly
  * 2.6.3 - does not work correctly
  * 2.6.4 - does not work correctly
  * 2.6.6 - does not work correctly
  * 2.7.6 - does not work correctly
  * 3.3.3 - does not work correctly
  * 3.3.5 - does not work correctly
  * 3.4.0 - does not work correctly


  Several related observations, indicating that this could be some sort 
of a Windows Installer misconfiguration issue possibly solvable in the 
CPython installer:


  * The same does not occur when you install a 64-bit CPython version - 
their entry is correctly displayed in the 'Add/Remove Programs' dialog.


  * 32-bit CPython installer still correctly detects that a specific 
32-bit version has already been installed, even if that previous 
installation is not listed in the 'Add/Remove Programs' dialog.


  * When you ask Windows using its WMI interface to list all the 
products installed on it (e.g. by running 'wmic product list' on the 
command-line), all the installed CPython versions are correctly 
displayed, even those 32-bit versions not displayed in the 'Add/Remove 
Programs' dialog.



  I started looking into this because I had a 32-bit CPython 3.4.0rc3 
installation on my system that I wanted to remove, and since I did not 
see it registered in the 'Add/Remove Programs' dialog, I directly 
deleted its installation folder. That left my system in a state where a 
replacement 32-bit CPython 3.4.0 installation would always fail because 
it would detect that there was already a valid CPython 3.4 installation 
on the system, and then it would fail attempting to uninstall it. Fixing 
this required manually cleaning up leftover CPython 3.4.0rc3 windows 
installer registry entries. Note that the issue could not be fixed by 
using the CPython 3.4.0rc3 installer as it failed due to the same problem.


  This situation would suggest that something should be done in the 
Windows installer so it does not 'fail miserably' if a previous CPython 
installation can not removed. Possibly allow it to detect that the 
previous CPython installation has already been removed and simply clean 
up its Windows Installer registry entries.



  While working on this, I did discover a 'workaround' for the 
'Add/Remove Programs' dialog issue, but it will take someone more 
knowledgeable about the Windows Installer infrastructure to say if the 
workaround can be applied directly as a clean solution or if it could 
have hidden consequences:


  Each 32-bit installation on 64-bit Windows has its own 'Uninstall' 
registry key under:



HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall


named after its Windows Installer assigned GUID, e.g.:


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{A37F2D73-72D1-364D-BA5D-CEA430BCC040}


  In that key there is a value named 'WindowsInstaller' which for 
CPython installations has the value '1' (of type REG_DWORD).


  If you change that value to '0' (again, of type REG_DWORD), the 
installation's 'Add/Remove Programs' dialog entry will get displayed 
correctly, and user will be able to run the installation 
(reinstall/change/uninstall) from there.



  I compared MSI packaging related CPython source code (Tools/msi 
folder) in 2.6.2 & 2.6.3 releases but I can not see anything suspicious 
there. It could be that the observed beaviour change between those two 
versions is a result of the final release packager changing his used 
Windows Installer version, but I have not rebuilt CPython, and its MSI 
installer to test this theory out.



  Anyone have any more information on this?

  Should I open a 'Add/Remove Programs' dialog related issue in the 
CPython issue tracker? And possibly a separate one for making CPython 
installations not fail without possible recovery if a previous CPython 
installation has already been removed?



  Many thanks.

  Best regards,
Jurko Gospodnetić

P.S.
  All this has been tested using Windows 7 SP1 (x64).

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mai

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Victor Stinner 
Hi,

I modified the Misc/NEWS file:

* I moved 3.3 sections to Misc/HISTORY: items were already present,
but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
* I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be
present in the 3.4 branch (changeset cb161cd94e6e)

Is that correct?

Victor

2014-03-17 7:38 GMT+01:00 Larry Hastings :
>
>
> The "3.4" branch is now checked in.  It contains all the 3.4 releases since
> 3.4.0rc1.  Its current state is effectively 3.4.1.
>
> The "default" branch is now 3.5.
>
> Cry havoc, and let slip the dogs of war,
>
>
> /arry
>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] trouble building 3.3

2014-03-17 Thread Terry Reedy 

On 3/17/2014 3:57 PM, Sean Felipe Wolfe wrote:

I'm working on some IDLE oriented bugs and I'm having some trouble
building the 3.3 branch:


Starting today, Idle for 3.3 is no more patched.
2.7, 3.4, and 3.5 will be patched for now.



--
Terry Jan Reedy

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Nick Coghlan 
On 18 Mar 2014 07:37, "Victor Stinner"  wrote:
>
> Hi,
>
> I modified the Misc/NEWS file:
>
> * I moved 3.3 sections to Misc/HISTORY: items were already present,
> but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
> * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be
> present in the 3.4 branch (changeset cb161cd94e6e)
>
> Is that correct?

Not everything was cherry picked, so we'll need to review that to move the
3.4.1 fixes back to the appropriate section.

Cheers,
Nick.

>
> Victor
>
> 2014-03-17 7:38 GMT+01:00 Larry Hastings :
> >
> >
> > The "3.4" branch is now checked in.  It contains all the 3.4 releases
since
> > 3.4.0rc1.  Its current state is effectively 3.4.1.
> >
> > The "default" branch is now 3.5.
> >
> > Cry havoc, and let slip the dogs of war,
> >
> >
> > /arry
> >
> > ___
> > python-committers mailing list
> > [email protected]
> > https://mail.python.org/mailman/listinfo/python-committers
> >
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [python-committers] default hg.python.org/cpython is now 3.5

2014-03-17 Thread Larry Hastings 

On 03/17/2014 04:23 PM, Nick Coghlan wrote:



On 18 Mar 2014 07:37, "Victor Stinner" > wrote:

>
> Hi,
>
> I modified the Misc/NEWS file:
>
> * I moved 3.3 sections to Misc/HISTORY: items were already present,
> but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
> * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be
> present in the 3.4 branch (changeset cb161cd94e6e)
>
> Is that correct?

Not everything was cherry picked, so we'll need to review that to move 
the 3.4.1 fixes back to the appropriate section.




I merged "default" into "3.4" (3a3a83195159), so every change that was 
in "default" last night will automatically go into 3.4.1.  Stuff that 
got cherry-picked back for 3.4.0 should already be in their correct 
sections.


I worked pretty hard to get that right, so while I'd be interested to 
hear if I got it wrong, my assumption (my hope) for now is that 
Misc/NEWS is basically correct in both "3.4" and "default".



//arry/
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] trouble building 3.3

2014-03-17 Thread Sean Felipe Wolfe 
Ah ok, got it.

Antoine - I'll try your solution out though just out of curiosity, thanks :)

On Mon, Mar 17, 2014 at 2:52 PM, Terry Reedy  wrote:
> On 3/17/2014 3:57 PM, Sean Felipe Wolfe wrote:
>>
>> I'm working on some IDLE oriented bugs and I'm having some trouble
>> building the 3.3 branch:
>
>
> Starting today, Idle for 3.3 is no more patched.
> 2.7, 3.4, and 3.5 will be patched for now.
>
>
>
> --
> Terry Jan Reedy
>
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/ether.joe%40gmail.com



-- 
A musician must make music, an artist must paint, a poet must write,
if he is to be ultimately at peace with himself.
- Abraham Maslow
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] hg branching + log question

2014-03-17 Thread Sean Felipe Wolfe 
Ah well, ok. That seems pretty counterintuitive to me though. I
suppose Hg has its quirks just like ... that other DCVS system ... :P

On Mon, Mar 17, 2014 at 1:07 PM, Antoine Pitrou  wrote:
> On Mon, 17 Mar 2014 13:02:23 -0700
> Sean Felipe Wolfe  wrote:
>> I'm getting my feet wet with the cpython sources and Mercurial. I'm a
>> bit confused -- when I checkout a branch, eg. 3.3, and I do an 'hg
>> log', why do I see log messages for other branches?
>
> This is a classic hg question, you would get the answer by asking
> Mercurial for help: hg log --help :)
>
> Basically, to restrict the log to a given branch, just use the -b
> option: hg log -b 3.3.
>
> Regards
>
> Antoine.
>
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/ether.joe%40gmail.com



-- 
A musician must make music, an artist must paint, a poet must write,
if he is to be ultimately at peace with himself.
- Abraham Maslow
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Python 3.5 now uses surrogateescape for the POSIX locale

2014-03-17 Thread Victor Stinner 
Hi,

I modified Python 3.5 to use the "surrogateescape" error handler (PEP
383) for stdin and stdout when the LC_CTYPE locale is POSIX ("C"
locale):
http://bugs.python.org/issue19977

New behaviour:
---
$ mkdir z
$ touch z/abcé
$ LC_CTYPE=C ./python -c 'import os; print(os.listdir("z")[0])'
abcé
---

Old behaviour, before the change (test with Python 3.3):
---
$ LC_CTYPE=C python3 -c 'import os; print(os.listdir("z")[0])'
Traceback (most recent call last):
  File "", line 1, in 
UnicodeEncodeError: 'ascii' codec can't encode characters in position
3-4: ordinal not in range(128)
---

The POSIX locale is common because it is used by default when no other
locale is set. It's common that programs started by a crontab on UNIX
and daemons are using this locale.

Victor
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] cpython: Add a stub "whatsnew in 3.5" document.

2014-03-17 Thread Georg Brandl 
Am 18.03.2014 01:27, schrieb victor.stinner:
> http://hg.python.org/cpython/rev/daa6bf71170f
> changeset:   89835:daa6bf71170f
> user:Victor Stinner 
> date:Tue Mar 18 00:53:32 2014 +0100
> summary:
>   Add a stub "whatsnew in 3.5" document.
> 
> files:
>   Doc/whatsnew/3.5.rst |  186 +++
>   1 files changed, 186 insertions(+), 0 deletions(-)


Nice, but please also add it to the toctree in Doc/whatsnew/index.rst.

Georg

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com