[issue3214] Suggest change to glossary explanation: "Duck Typing"

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: While we are at it, should we keep this one as is? « Python3000 A mythical python release, not required to be backward compatible, with telepathic interface. » Not so mythical after all... missing the telepathic interface though. --

[issue3214] Suggest change to glossary explanation: "Duck Typing"

Paddy McCarthy <[EMAIL PROTECTED]> added the comment: Hi Georg, A bit of relevant background about me: I've been interested in Duck Typing _specifically_ for a couple of years when I started watching edits to it on Wikipedia. I researched the history of the use of the term and changed the attr

[issue2275] urllib2 header capitalization

Senthil <[EMAIL PROTECTED]> added the comment: Issue applicable to Py2.6 and Py3K. Previous patch attached was wrong. Removed it. -- versions: +Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> __

[issue2275] urllib2 header capitalization

Changes by Senthil <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9907/issue2275.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3254] Suggestion: change default behavior of __ne__

Changes by cvp <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10793/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python

[issue3254] Suggestion: change default behavior of __ne__

Changes by cvp <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10792/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python

[issue3254] Suggestion: change default behavior of __ne__

cvp <[EMAIL PROTECTED]> added the comment: 1) I didn't say that the option to edit __ne__ should be removed, only that it'd be both more consistent and convenient to change the meaning to something relative by default. 2) So long as the old code defines __ne__, which I'm guessing is the code tha

[issue3254] Suggestion: change default behavior of __ne__

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: 1) It's much more flexible. 2) It would break compatibility. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3254] Suggestion: change default behavior of __ne__

cvp <[EMAIL PROTECTED]> added the comment: But why not? Laziness or something? Or "just cuz?" -Constantine On Tue, Jul 1, 2008 at 4:11 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > > Benjamin Peterson <[EMAIL PROTECTED]> added the comment: > > Sorry, this is documented [1], and it unlikel

[issue3254] Suggestion: change default behavior of __ne__

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Sorry, this is documented [1], and it unlikely to ever be changed. [1] http://docs.python.org/ref/customization.html -- nosy: +benjamin.peterson resolution: -> rejected status: open -> closed ___

[issue2885] Create the urllib package

Brett Cannon <[EMAIL PROTECTED]> added the comment: And it looks like the 2.6 docs need to be updated as well. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3254] Suggestion: change default behavior of __ne__

New submission from cvp <[EMAIL PROTECTED]>: After defining my own __eq__ method for a class that judged equality based on a 'name' variable, imagine my surprise to see this: In [20]: my_graph.edges[-1].end == my_graph.vertices[-1] Out [20]: True In [21]: my_graph.edges[-1].end != my_graph.vert

[issue2351] Using __(get|set|del)slice__ needs a Py3K warning

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-li

[issue3251] references are case insensitive

Georg Brandl <[EMAIL PROTECTED]> added the comment: Thanks, fixed in r64642. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Corrected as r64633 (trunk) and r64639 (release25-maint). version 3.0 is not affected, and there won't be any more 2.4 release. Thanks for the report! -- resolution: -> fixed status: open -> closed ___

[issue1410739] Add notes to the manual about `is` and methods

Georg Brandl <[EMAIL PROTECTED]> added the comment: Reworded a bit and applied as r64638. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue1523853] 2.4.2 file.read caches EOF state

Georg Brandl <[EMAIL PROTECTED]> added the comment: Added note in r64635. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3191] round docstring is inaccurate

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed in r64634. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3112] implement PEP 3134 exception reporting

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Potential reviewers, let's make life easier for you: http://codereview.appspot.com/2448 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3240] IDLE environment corrupts string.letters

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: As Georg says: you shouldn't be mixing Unicode objects and string objects. It's perfectly valid for string.letters to contain non-ASCII bytes, and it's no surprise that this fails for you. string.letters indeed *does* contain only letters. I

[issue3214] Suggest change to glossary explanation: "Duck Typing"

Georg Brandl <[EMAIL PROTECTED]> added the comment: Paddy: IMO hasattr() is the "if it quacks like a duck" part of duck-typing. It e.g. allows testing "hasattr(x, 'write')" to see if it's a writable file-like object, and doing something else otherwise. Benjamin: ABCs are not duck-typing since th

[issue1682] Move Demo/classes/Rat.py to Lib/fractions.py and fix it up.

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Well, I can't find anything more to fuss about here. :-) Reclosing. -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3203] sphinx - table of contents doesn't render correctly (html)

Georg Brandl <[EMAIL PROTECTED]> added the comment: This is already on my to-do list. Thanks for raising it as an issue though, I won't forget it so easily this way :) ___ Python tracker <[EMAIL PROTECTED]> __

[issue3216] Scarce msilib documentation

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed the Execute parameter in r64630. add_data was already fixed. Assigning to Martin; if someone is to write usage info, it's got to be him. -- assignee: georg.brandl -> loewis nosy: +loewis resolution: -> fixed title: errors in msi

[issue3240] IDLE environment corrupts string.letters

Georg Brandl <[EMAIL PROTECTED]> added the comment: Well, that wouldn't be different if you had set the locale in your prompt. In short, ``u'a' in string.letters`` can never work with any string.letters except the default, English-only one, and therefore is wrong. ___

[issue3217] make text is broken

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed with r64629. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3220] Improve Bytes and Byte Array Methods doc

Georg Brandl <[EMAIL PROTECTED]> added the comment: > Lib Ref/Built-in Types/Sequence Types/Bytes and Byte Array Methods > > The following set/frozenset and dict sections repeat (and for dicts, > expands upon) the constructor interface from the Built-in Functions > section. The sequence type s

[issue3240] IDLE environment corrupts string.letters

Roger Upole <[EMAIL PROTECTED]> added the comment: It introduces high characters that cause comparisons to fail under IDLE that succeed from the normal python prompt: Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "l

[issue3235] Improve subprocess module usage

Georg Brandl <[EMAIL PROTECTED]> added the comment: Added a link to PEP 324 in r64625. The other issues were explained by Martin; it will be easier to read the subprocess docs in 2.6 where they're all on one page. -- resolution: -> fixed status: open -> closed _

[issue2775] Implement PEP 3108

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed in r64624. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list

[issue2683] subprocess.Popen.communicate takes bytes, not str

Georg Brandl <[EMAIL PROTECTED]> added the comment: You're right, I fixed that too in r64621. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyth

[issue3174] 3.0b1 doesn't seem to install on macs

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3219] repeated keyword arguments

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Done for 2.6 in r64622. (Georg reviewed.) -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> __

[issue2683] subprocess.Popen.communicate takes bytes, not str

Rafael Zanella <[EMAIL PROTECTED]> added the comment: _communicate still encodes the string under the hood ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2683] subprocess.Popen.communicate takes bytes, not str

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed docs in r64619. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3174] 3.0b1 doesn't seem to install on macs

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Ok. I tried to get it working in r64618. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3218] 2to3 Fix_imports optimization

Nick Edds <[EMAIL PROTECTED]> added the comment: Here is a diff for the both the fix_imports changes which I corrected, and the pytree changes. The pytree changes were a lot more significant before the fix_imports change, but I think they are still a decent improvement. I think I have now restore

[issue3239] curses/textpad.py incorrectly and redundantly imports ascii

Georgij Kondratjev <[EMAIL PROTECTED]> added the comment: >>> import curses.ascii as curses_ascii If you like curses_ascii you would probably like curses.ascii :) so here is the patch. I tested it with module built-in testing facility (if __name__ == '__main__') but didn't run other tests. Patc

[issue3253] shutil.move bahave unexpected in fat32

New submission from grissiom <[EMAIL PROTECTED]>: Build the environment in a fat32 file system: $echo test > test_move $mkdir testmove If I shutil.move('test_move', 'testmove'), it will raise: Traceback (most recent call last): File "testmove.py", line 5, in shutil.move('test_move', 'tes

[issue3252] str.tobytes() and bytes/bytearray.tostr()

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: There's nothing new to .encode() and .decode(). They have existed since Python 1.6. -- nosy: +lemburg resolution: -> wont fix status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3218] 2to3 Fix_imports optimization

Collin Winter <[EMAIL PROTECTED]> added the comment: The change to pytree.py doesn't add much speed benefit over the fix_imports.py change, and causes a test to fail. The fix_imports.py change, on the other hand, takes the test suite run time from 8m31s down to 1m45s -- this needs to go in! Tha

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

Brodie Rao <[EMAIL PROTECTED]> added the comment: Thanks. The patch fixes the crash for me on Python 2.5.2 and 2.6b1 on OS X and Python 2.4.5 on Debian and Ubuntu. ___ Python tracker <[EMAIL PROTECTED]> _

[issue3252] str.tobytes() and bytes/bytearray.tostr()

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > encoding and decoding is generally accepted terminology Yes, but I personally always pause a couple of seconds each time I have to write "encode" or "decode". Following Mark's idea, I think I will mentally use "en-bytes" and "de-bytes

[issue3252] str.tobytes() and bytes/bytearray.tostr()

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: -1 encoding and decoding is generally accepted terminology. Besides then we would be binding ourselves to returning bytes or a str; that's not necessarily guaranteed. Anyway, I think this hardly has a chance in the place we are (between be

[issue3000] 2to3 doesn't handle print(whatever); print nor string.* functions

Changes by Mark Summerfield <[EMAIL PROTECTED]>: -- type: -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list m

[issue3252] str.tobytes() and bytes/bytearray.tostr()

New submission from Mark Summerfield <[EMAIL PROTECTED]>: I know it is almost certainly too late, but I think a lot of people will be confused by str.decode() and bytes.encode() (or was that the other way around)? Calling the methods str.tobytes() and bytes.tostr() (or nicer, str.to_bytes() and

[issue3249] bug adding datetime.timedelta to datetime.date

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3249] bug adding datetime.timedelta to datetime.date

Tim Peters <[EMAIL PROTECTED]> added the comment: This isn't "a bug", since it's functioning as documented and designed. Read note 1 in the "date Objects" section of the reference manual, explaining the meaning of "date2 = date1 + timedelta": """ date2 is moved forward in time if timedelta.days

[issue3251] references are case insensitive

New submission from Wolfgang Langner <[EMAIL PROTECTED]>: References can be added case sensitive as .. _myRef: but only used case insensitive with :ref:`myref` usage of :ref:`myRef` doesn't generate a working reference. Make this behavior consistent please, always case insensitive or always case

[issue648658] xmlrpc can't do proxied HTTP

anatoly techtonik <[EMAIL PROTECTED]> added the comment: I will be second to emphasize the importance of using XML-RPC through a proxy. bzr behind a proxy can't be used with launchpad because of this bug. -- nosy: +techtonik ___ Python tracker <[EMAIL

[issue1613573] xmlrpclib ServerProxy uses old httplib interface

anatoly techtonik <[EMAIL PROTECTED]> added the comment: * use newer 2.0 public interface of httplib for connection handling Attached patch is for trunk/ Tested for Python 2.5 issue1767370 is a separate issue that can be fixed later -- keywords: +patch nosy: +techtonik versions: +Python

[issue3250] datetime.time does not support arithmetic

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- type: -> feature request versions: +Python 2.7 -Python 2.4, Python 2.5 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3250] datetime.time does not support arithmetic

New submission from Chris Withers <[EMAIL PROTECTED]>: >>> from datetime import time >>> time(9,0)-time(8,0) Traceback (most recent call last): File "", line 1, in TypeError: unsupported operand type(s) for -: 'datetime.time' and 'datetime.time' I'd expect a datetime.timedelta(0,3600) --

[issue3249] bug adding datetime.timedelta to datetime.date

New submission from Chris Withers <[EMAIL PROTECTED]>: The following demonstrates the problem: >>> from datetime import datetime,timedelta >>> datetime.now().date()+timedelta(hours=1) datetime.date(2008, 7, 1) I'd expect the above to either result in a TypeError or (preferably) datetime.datetim

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I reproduced the problem on windows, and it is indeed a problem with the "print" statement, when the write() method reassigns sys.stdout: the code calls PyFile_WriteString(), then PyFile_SoftSpace on the same object, which has been freed

[issue3099] On windows, "import nul" always succeed

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: GetFileAttributes() succeeds for "nul", but GetFileAttributesEx() fails. Maybe is it good idea to use GetFileAttributesEx()? # test code import ctypes import ctypes.wintypes as type dll = ctypes.windll.kernel32 print dll.GetFileAttribut