Mailman 3 July 2012 - Python-Dev

Re: [Python-Dev] [Python-checkins] peps: Update PEP-0424 with respect to feedback received.
by Andrew Svetlov July 30, 2012

July 30, 2012

On Mon, Jul 30, 2012 at 4:10 AM, alex.gaynor <python-checkins(a)python.org> wrote: > +In addition, a new function ``operator.length`` hint is added ``operator.length`` or ``operator.length_hint``? > + def length_hint(obj, default): Is there default value for `default` parameter? For example: def length_hint(obj, default=0): pass or something like that? -- Thanks, Andrew Svetlov

2 2

Pushing issue #12288
by Andrew Svetlov July 30, 2012

July 30, 2012

Is there ok to push http://bugs.python.org/issue12288 in 3.3? It looks very easy and straightforward. If now is too alte — I'm ok. Georg Brandl, what's your decision? -- Thanks, Andrew Svetlov

2 2

AUTO: Jon K Peck is out of the office
by Jon K Peck July 30, 2012

July 30, 2012

I am out of the office until 08/02/2012. I will be out of the office from July 29 through Aug 2. I expect to have some access to email but will be delayed in responding. Note: This is an automated response to your message "Python-Dev Digest, Vol 108, Issue 46" sent on 07/30/2012 4:00:03. This is the only notification you will receive while this person is away.

1 0

datetime nanosecond support
by Vincenzo Ampolo July 30, 2012

July 30, 2012

Hi all, This is the first time I write to this list so thank you for considering this message (if you will) :) I know that this has been debated many times but until now there was no a real use case. If you look on google about "python datetime nanosecond" you can find more than 141k answer about that. They all say that "you can't due to hardware imprecisions" or "you don't need it" even if there is a good amount of people looking for this feature. But let me explain my use case: most OSes … [View More]

9 17

python-checkins moderation
by Barry Warsaw July 30, 2012

July 30, 2012

I just freed up a bunch, but not all, of the messages to python-checkins being held for moderator approval. We could use some additional moderator volunteers. I'm not sure Fred is still moderating the list, and I suck at it. Please email me directly if you'd like to help out, have experience moderating lists, and at least vaguely <wink> understand what's on and off topic for python-checkins. Cheers, -Barry

2 1

PEP updating
by "Martin v. Löwis" July 29, 2012

July 29, 2012

I added a cron job on www.python.org that checks every 5 minutes for a modified PEP. So automatic updating should work again. Regards, Martin

5 4

feature freeze questions
by Chris Jerdonek July 28, 2012

July 28, 2012

I have a few questions about feature freeze: (1) Is increasing test coverage acceptable during feature freeze, even if it does not involve fixing a bug? (2) When adding new tests (e.g. in the course of fixing a bug or increasing test coverage), are we allowed to refactor other tests so that supporting test code can be shared? Or should the tests be added in a less DRY fashion and refactored only after the branch goes back to pre-alpha? (3) What types of documentation changes are allowed … [View More]

5 7

__sizeof__ tests
by Chris Jerdonek July 28, 2012

July 28, 2012

On Sat Jul 28 10:54:24 CEST 2012, Serhiy Storchaka storchaka at gmail.com wrote: > For not to duplicate the supporting code, I suggest > add (move from test_sys test) three utility functions to test.support > module (issue #15467). Also from the use of the common code will benefit > issues #15402 (for struct) and #15424 (for array). The testing for > cElemetTree also will be easier. > > Martin remarked that this adds new features to test.support and can only > be done … [View More]

2 1

__sizeof__ tests
by Serhiy Storchaka July 28, 2012

July 28, 2012

I have a set of patches about the correct __sizeof__ implementations (one has already been committed (issue #15456), 13 left, 2 of them published (#15469 for deque and #15475 for itertools)). The most tedious is to write tests for them, especially paranoid tests, on which Martin v. Löwis insists. For not to duplicate the supporting code, I suggest add (move from test_sys test) three utility functions to test.support module (issue #15467). Also from the use of the common code will benefit … [View More]

2 1

Issue 15295: New import documentation
by Barry Warsaw July 28, 2012

July 28, 2012

Back when Eric, Jason, and I sprinted on the PEP 420 implementation, I threatened to actually document how the import machinery worked, updating and reorganizing to include the new PEP 420 protocols. Issue 15295 tracks this: http://bugs.python.org/issue15295 I now have a first draft of the new import machinery documentation. This refactors the import statement docs, moving everything concerning the finding and loading of modules into a separate language reference section. The import … [View More]

2 1