New submission from David Wolever:
The PyInstanceMethod_Type, unlike all other method types, isn't hashable.
It seems like the code exists, it's just been commented out:
https://github.com/python/cpython/blame/c30098c8c6014f3340a369a31df9c74bdbacc269/Objects/classobject.c#L569
Th
David Wolever added the comment:
It may also be worth noting that the strftime formatters table now includes
examples from different locales:
https://docs.python.org/2/library/datetime.html#strftime-strptime-behavior
This change was introduced about a year ago
David Wolever added the comment:
D'oh, yes, it can (and I've closed it now).
--
status: pending -> closed
___
Python tracker
<http://bugs.pytho
Changes by David Wolever :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue18680>
___
___
Python-bugs-list
David Wolever added the comment:
Done, pushed to 2.7, 3.3, default.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
David Wolever added the comment:
Here's the relevant diff. Will commit on a +1.
diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
--- a/Doc/library/datetime.rst
+++ b/Doc/library/datetime.rst
@@ -1664,7 +1664,7 @@
| ``%M``| Minute as a zero-padded| 00, 01, ..
New submission from David Wolever:
The documentation for the `%S` formatter suggests that it supports leap
seconds, but the footnote contradicts that:
> The range really is 0 to 61; according to the Posix standard this
> accounts for leap seconds and the (very rare) double leap seconds.
Changes by David Wolever :
Added file: http://bugs.python.org/file30354/0f4d971b0cee.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list m
Changes by David Wolever :
Removed file: http://bugs.python.org/file30353/102b3e257dca.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bug
Changes by David Wolever :
Added file: http://bugs.python.org/file30353/102b3e257dca.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list m
David Wolever added the comment:
Fixed a misleading note about Unicode in localized formatters in file29841.
--
___
Python tracker
<http://bugs.python.org/issue17
Changes by David Wolever :
Added file: http://bugs.python.org/file29841/53a0e908f787.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list m
David Wolever added the comment:
Ok, I've added some locale examples and fixed up the note numbering. See diff
in file29839, and there is a live version to preview here:
http://hul.wolever.net/python-doc/library/datetime.html#strftime-and-strptime-behavior
If I can get a +1 on this, I&#x
Changes by David Wolever :
Added file: http://bugs.python.org/file29839/ae18c5ae2c4d.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list m
Changes by David Wolever :
Removed file: http://bugs.python.org/file29836/b3b1dcdc8cee.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bug
Changes by David Wolever :
Added file: http://bugs.python.org/file29836/b3b1dcdc8cee.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list m
Changes by David Wolever :
--
hgrepos: +182
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Wolever added the comment:
Ah, yes — thanks Éric. I've fiddled with the wording on the %f note a bit so it
makes more sense along with the versionadded, and removed the versionadded
text, which is basically identical to the note and descri
Changes by David Wolever :
Added file: http://bugs.python.org/file29785/strftime-docs.diff
___
Python tracker
<http://bugs.python.org/issue17701>
___
___
Python-bug
New submission from David Wolever:
The current strftime documentation isn't very helpful. It doesn't have
examples, and the ordering is unhelpful.
I've also moved some format-specific notes into the notes below the
format-string-table, because the format string table is what
David Wolever <[EMAIL PROTECTED]> added the comment:
Here is a patch that will detect a `from __future__ import print_function`
and adjust the grammar appropriately.
Any objections?
--
keywords: +patch
Added file: http://bugs.python.org/file10081/print_function_detectio
David Wolever <[EMAIL PROTECTED]> added the comment:
I've cleaned up and applied the patch in r62470.
As Collin suggested, I'm leaving the ticket open to use in the future.
__
Tracker <[EMAIL PROTECTED]>
<http://
David Wolever <[EMAIL PROTECTED]> added the comment:
Ah, yes -- that may be the fault of the confusingly named
'check_both'. The "both" means "both when the module in question
exists and when it does not". If you've got a better name, please
David Wolever <[EMAIL PROTECTED]> added the comment:
Can you write a test case proving this?
At the moment, the second thing that the transform function in
fix_import.py does is return if the import doesn't look like a local
import (see probably_a_local_import in fix_import).
At
David Wolever <[EMAIL PROTECTED]> added the comment:
Ah, yea -- in my rush to catch my train I must have neglected to look at
the _results_ of running test.py... I have updated the patch so the fixers
will work.
Added file: http://bugs.python.org/file9853/fixer_head_node_lookup_
Changes by David Wolever <[EMAIL PROTECTED]>:
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2468>
__
___
David Wolever <[EMAIL PROTECTED]> added the comment:
Ah, nuts -- I had a test case for this, but it was testing with 'from
itertools import izip, imap'... But not the single node >_<
It has been fixed, and appropriate test has been added, in r61824.
On 23-Mar-08, at 4:
David Wolever <[EMAIL PROTECTED]> added the comment:
Ok, I've fixed this in r61755.
I _think_ it does the right thing, but it might be good if someone else
checks out the test cases to make sure.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
David Wolever <[EMAIL PROTECTED]> added the comment:
A patch so that, on each node, only fixers who's head node could match
this node are executed. It's still hacky and ugly, but a decent POC.
--
keywords: +patch
Added file: http://bugs.python.org/file9791/fixer_head_
David Wolever <[EMAIL PROTECTED]> added the comment:
Martin and I talked about this, and I'm going to try loading the first
node of each tree generated by the PATTERNs into a dictionary, then when
the tree is walked, only fixers which could potentially match the current
node a
New submission from David Wolever <[EMAIL PROTECTED]>:
It takes me 10 seconds to run 2to3 on the example file.
--
assignee: collinwinter
components: 2to3 (2.x to 3.0 conversion tool)
messages: 64152
nosy: David Wolever, collinwinter
severity: normal
status: open
title: 2to3 is
David Wolever <[EMAIL PROTECTED]> added the comment:
Ok, fixed in r61664.
--
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
David Wolever <[EMAIL PROTECTED]> added the comment:
Ok, I've added explicit ordering to fixers in r61654, fixing this issue.
--
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bu
Changes by David Wolever <[EMAIL PROTECTED]>:
--
assignee: collinwinter -> David Wolever
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
David Wolever <[EMAIL PROTECTED]> added the comment:
itertools.imap is being translated directly to map... But I bet this is
another one of those ordering problems -- itertools.imap is converted to
the map, then the map is converted to list(map(...)) because fix_map
doesn't know t
David Wolever <[EMAIL PROTECTED]> added the comment:
As of r61635, the fix_print fixer has been fixed and tests have been added
(which will ``assert False`` when 2to3 is fixed so it can handle
``print(**kwargs)``).
--
assignee: David Wolever -> col
David Wolever <[EMAIL PROTECTED]> added the comment:
I've updated the fixer (checkin to come shortly), but 2to3 gets upset when
you it comes across print statements with kwargs (eg: print("spam", end="
")), so the tests will be co
Changes by David Wolever <[EMAIL PROTECTED]>:
--
assignee: collinwinter -> David Wolever
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
David Wolever <[EMAIL PROTECTED]> added the comment:
Added in r61626.
--
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2414>
__
_
David Wolever <[EMAIL PROTECTED]> added the comment:
Ok, checked in the last piece -- fixer for filter -- in r61598.
--
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
David Wolever <[EMAIL PROTECTED]> added the comment:
Added to future_builtins in r61587.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2171>
__
___
Python
David Wolever <[EMAIL PROTECTED]> added the comment:
Filter has been fixed in r61546.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2171>
__
___
Python
Changes by David Wolever <[EMAIL PROTECTED]>:
--
nosy: -brett.cannon, collinwinter
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by David Wolever <[EMAIL PROTECTED]>:
--
nosy: -brett.cannon, collinwinter
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by David Wolever <[EMAIL PROTECTED]>:
--
nosy: -brett.cannon, collinwinter
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by David Wolever <[EMAIL PROTECTED]>:
--
nosy: -brett.cannon, collinwinter, georg.brandl
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
David Wolever <[EMAIL PROTECTED]> added the comment:
Fixed in r61466.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2360>
__
___
Python-bugs-list mailing
David Wolever <[EMAIL PROTECTED]> added the comment:
Fixed in r61466.
--
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2361>
__
_
David Wolever <[EMAIL PROTECTED]> added the comment:
Fixed in r61466.
--
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2362>
__
_
David Wolever <[EMAIL PROTECTED]> added the comment:
Fixed in r61466.
--
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2363>
__
_
David Wolever <[EMAIL PROTECTED]> added the comment:
The 2to3 stuff relating to map is added in r61479.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2171>
__
David Wolever <[EMAIL PROTECTED]> added the comment:
To clarify, 2to3 shouldn't wrap map, filter, zip in list() if they are
imported from future_builtins.
------
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
New submission from David Wolever <[EMAIL PROTECTED]>:
ssh-rsa
B3NzaC1yc2EBIwAAAIEAvyZUU3zNsAoETLN8kDgTmm6qPeWMqUno3KkxcayPSVzT
U2pBLlMet/LVtLpHwqARTo4d5/g9vmjwPluQO7LgyIsH88GlJYRgPwV08rpzBTDR+/
0ZQWt82J7loB1z6mhxMS+YS0Oe2UOEXxYTCKfwwyTXDKVRk8wjlneyI9JZfB8=
[EMAIL PRO
David Wolever <[EMAIL PROTECTED]> added the comment:
I'll take this one (and the next few dealing with itertools)
------
nosy: +David Wolever
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
New submission from David Wolever <[EMAIL PROTECTED]>:
This patch makes it easier to run tests in the 2to3 suite.
--
assignee: collinwinter
components: 2to3 (2.x to 3.0 conversion tool)
files: 2to3tester.patch
keywords: patch
messages: 63740
nosy: David Wolever, collinwinter
se
55 matches
Mail list logo
