[Python-Dev] fixing broken link in pep 3

2014-12-17 Thread Raymond Sanchez
Hello my name is Raymond and I would like to fix a broken link on pep 3. If you go to https://www.python.org/dev/peps/pep-0003/ and click on link http://www.python.org/dev/workflow/, it returns a 404. What is the correct url? Should we also update the description "It has been replaced by the Issue

Re: [Python-Dev] datetime nanosecond support (ctd?)

2014-12-17 Thread Eric Snow
On Wed, Dec 17, 2014 at 7:52 PM, Matthieu Bec wrote: > > > Attached patch defines a new type struct_timespec for the time module. A new > capsule exports the type along with to/from converters - opening a bridge > for C, and for example the datetime module. I'd recommend opening a new issue in th

Re: [Python-Dev] datetime nanosecond support (ctd?)

2014-12-17 Thread Matthieu Bec
Attached patch defines a new type struct_timespec for the time module. A new capsule exports the type along with to/from converters - opening a bridge for C, and for example the datetime module. Your comments welcomed. If people feel this is worth the effort and going the right direction, I

Re: [Python-Dev] Proposal: Update PEP 1 to allow an explicit "Provisional" status for PEPs

2014-12-17 Thread Nick Coghlan
On 18 December 2014 at 08:10, Barry Warsaw wrote: > On Dec 18, 2014, at 06:57 AM, Nick Coghlan wrote: > >>However, I'd be happier if we could communicate that status more >>explicitly through the PEP process, especially as I think such a >>capability would be useful more generally as we move towar

Re: [Python-Dev] Proposal: Update PEP 1 to allow an explicit "Provisional" status for PEPs

2014-12-17 Thread Barry Warsaw
On Dec 18, 2014, at 06:57 AM, Nick Coghlan wrote: >However, I'd be happier if we could communicate that status more >explicitly through the PEP process, especially as I think such a >capability would be useful more generally as we move towards >implementing metadata 2.0 and potentially other enhan

Re: [Python-Dev] Proposal: Update PEP 1 to allow an explicit "Provisional" status for PEPs

2014-12-17 Thread Ethan Furman
On 12/17/2014 12:57 PM, Nick Coghlan wrote: > > If folks are OK with this idea, I'll go ahead and make the appropriate > changes to PEP 1 and the PEP index generator. I'm also happy to file a > tracker issue, or write a short PEP, if folks feel making such a > change requires a little more formali

[Python-Dev] Proposal: Update PEP 1 to allow an explicit "Provisional" status for PEPs

2014-12-17 Thread Nick Coghlan
Hi folks, The recent release of setuptools 8.0 brought with it the migration to the more explicit version handling semantics defined in PEP 440. Some of the feedback on that release showed us that we could really use the equivalent of PEP 411 for interoperability PEPs as well as for standard libr

Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

2014-12-17 Thread anatoly techtonik
On Wed, Dec 17, 2014 at 12:56 AM, Guido van Rossum wrote: > This thread hasn't been productive for a really long time now. I agree. The constructive way would be to concentrate on looking for causes. I don't know if there is a discipline of "programming language usability" in computer science, bu

[Python-Dev] A metaclass for immutability

2014-12-17 Thread Tschijnmo Tschau
Hi all, Recently when I am writing a computer algebra system for a very special purpose, it is found that being able to have objects of user-defined classes immutable can be very nice. It would greatly enhance the safety of the code. For example in the code that I were writing, objects hold a lot

Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition

2014-12-17 Thread Hrvoje Niksic
On 12/16/2014 08:18 PM, R. David Murray wrote: On Tue, 16 Dec 2014 10:48:07 -0800, Mark Roberts wrote: > Besides, using iteritems() and friends is generally a premature > optimization, unless you know you'll have very large containers. > Creating a list is cheap. [...] No. A premature optimi