[issue9169] Deprecate use of more than 3 positional arguments in timedelta constructor

Changes by Alexander Belopolsky : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue7584] datetime.rfcformat() for Date and Time on the Internet

Alexander Belopolsky added the comment: Adding issue 7989 as a dependency because having pure python implementation in the CPython tree will make it much easier to experiment with new datetime features. I am still -1 on adding specialized formatting methods to the datetime class. I think th

[issue9254] __import__ docstring should recommend importlib.import_module()

Éric Araujo added the comment: More rationale for not using a dummy fromlist, from Brett Cannon: “Pulling from sys.modules is the correct way to do this. There are subtle issues when using a bunk fromlist argument (empty modules, double initialization, etc.). If one does not use importlib.impor

[issue9255] document that the 'test' package is for core developers only

R. David Murray added the comment: Alexander: issue8273 addresses this, but I don't think Brett's doc change should be held up pending the resolution of that issue. Also, the entire set of test.support documentation should move to a set of 'developer' docs (which I think Brett plans to write

[issue9243] sndhdr erroneously detects files as vox

STINNER Victor added the comment: > Oh, and the reason it got changed to startswith is probably > a micro-optimization: startswith is more efficient than doing > a slice-and-compare. Not really. I changed it because it's more readable (it's easier to understand that the code). -- James: I c

[issue9253] argparse: optional subparsers

R. David Murray added the comment: I've added Steven as nosy so he knows this was reposted here. I've also set the priority to low. Personally I'm at least -0 on this, since if I use a command that has subcommands I expect to get an error if I supply an invalid subcommand. As you say, howe

[issue9253] argparse: optional subparsers

Changes by R. David Murray : -- priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue9253] argparse: optional subparsers

Changes by R. David Murray : -- stage: -> unit test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue9255] document that the 'test' package is for core developers only

Alexander Belopolsky added the comment: Issue 8273 is in some sense the opposite of this - it calls for blessing of everything in in test.support while this issue calls for wholesale "unblessing". I don't think either approach is right. While users should definitely never import test_* modu

[issue9255] document that the 'test' package is for core developers only

R. David Murray added the comment: "Use it at your own risk" is always an option. Brett is saying that test.support docs need to make it clear that anyone using it is doing so at their own risk: it is for core development only and so we might change anything at any time without considering b

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: Aren't there two ValueErrors in the file? One is a platform and (in the now-fixed version) the other would indicate a problem with I/O or vcvars execution (like permissions). -- ___ Python tracker

[issue7989] Add pure Python implementation of datetime module to CPython

Alexander Belopolsky added the comment: In issue7989c.diff, I reverted to lazy import of _strptime, added cleanup of _xyz helper functions, and made test_datetime more robust by restoring sys.modules more thoroughly. Unfortunately I've encountered an issue with Rietveld that prevents me from

[issue9256] plistlib should create non-naïve datetime objects

New submission from Wim : The plistlib module parses elements in the plist into datetime objects. (This is good.) However, it produces naïve datetimes, even though the elements include an explicit timezone specification ('Z' for UTC, since they're in ISO 8601 format). Now that issue 5094 ha

[issue9256] plistlib should create non-naïve datetime objects

Alexander Belopolsky added the comment: Yes, parsing elements ending with 'Z' into aware datetime objects makes perfect sense, but this should be done carefully because doing so will break any code that mixes the result with naive datetimes. There is a lengthy RFC 3339 discussion in issue 75

[issue2986] difflib.SequenceMatcher not matching long sequences

Terry J. Reedy added the comment: [copied from pydev post] Summary: adding an autojunk heuristic to difflib without also adding a way to turn it off was a bug because it disabled running code. 2.6 and 3.1 each have, most likely, one final version each. Don't fix for these but add something t

[issue9249] struct.pack and Long Integer datatype should be 4, but is 8 bytes

Changes by Mark Dickinson : -- components: +Extension Modules -ctypes resolution: -> invalid status: open -> pending ___ Python tracker ___ __

[issue9257] cElementTree iterparse requires events as bytes; ElementTree uses strings

New submission from Eric Talevich : In xml.etree, ElementTree and cElementTree implement different interfaces for the iterparse function/class. In ElementTree, the argument "events" must be a tuple of strings: from xml.etree import ElementTree as ET for result in ET.iterparse('example.xml', ev

[issue6033] LOOKUP_METHOD and CALL_METHOD optimization

Reid Kleckner added the comment: I have an patch for unladen-swallow out for review here: http://codereview.appspot.com/160063/show It resolves the correctness issues I mentioned previously by emitting guards if necessary. If the type is predictable and uses slots, then we don't need to chec

[issue5673] Add timeout option to subprocess.Popen

Reid Kleckner added the comment: I went through the trouble of building and testing Python on Windows Vista, and with some small modifications I got the tests I added to pass. Here's an updated patch. I'm still not really sure how those threads work on Windows, so I'd rather leave that TODO

<    1   2