[issue7187] importlib/_bootstrap.py write_bytecode raises an IOError if it can't open the .pyc file for writing

Changes by Brett Cannon : -- priority: -> normal stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue7187] importlib/_bootstrap.py write_bytecode raises an IOError if it can't open the .pyc file for writing

Brett Cannon added the comment: Thanks for the report and potential fix, Dave. I'm swamped at the moment but I will get to this. -- ___ Python tracker ___ __

[issue7187] importlib/_bootstrap.py write_bytecode raises an IOError if it can't open the .pyc file for writing

Changes by Benjamin Peterson : -- assignee: -> brett.cannon nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue7006] The replacement suggested for callable(x) in py3k is not equivalent

Benjamin Peterson added the comment: 2009/10/22 Georg Brandl : > > Georg Brandl added the comment: > > 2to3 still uses hasattr(x, 'callable') Do you have strong opinions about this? IMO, hasattr(x, '__call__') is compatible enough. -- ___ Python tr

[issue7182] For non-debug builds, the cygwinccompiler.py should define NDEBUG

Roumen Petrov added the comment: Ok Daniel. In this case for debug build _DEBUG has to be defined too - please check pyconfig.h from MSVC builds. May be you could use CFLAGS environment variable. -- ___ Python tracker

[issue7187] importlib/_bootstrap.py write_bytecode raises an IOError if it can't open the .pyc file for writing

Changes by Dave Malcolm : -- title: importlib/_bootstrap.py write_bytecode fails if it can't open the .pyc file for writing -> importlib/_bootstrap.py write_bytecode raises an IOError if it can't open the .pyc file for writing ___ Python tracker

[issue7187] importlib/_bootstrap.py write_bytecode fails if it can't open the .pyc file for writing

New submission from Dave Malcolm : I'm working on an RPM package of Python 3.1.1 for Fedora [1]. Within my RPMs are precompiled .pyc and .pyo files that are not writable by users, and are hardlinked together if they have equal content. For example: $ ls -al /usr/lib/python3.1/tkinter/__init

[issue6882] uuid creates zombies

Eric Smith added the comment: Back ported the try/finally parts to trunk in r75620. -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue7186] Document specialness of __doc__, and possibly other "special" attributes

New submission from steve steiner : Around the time of the 2.6.4 release, it was suggested that Python 2.6.3 changed the __doc__ attribute to read-only. See: http://bugs.python.org/issue7183 When asked whether this read-only behaviour was intentional, Guido answered, simply "Yes" and also wrote

[issue6952] deprecated conversion from string constant to char *

Barry Alan Scott added the comment: Updated patch with comment explaining cast. -- Added file: http://bugs.python.org/file15184/const_api_r75619.patch ___ Python tracker ___

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

Barry A. Warsaw added the comment: After discussion on python-dev, this will not block 2.6.4 -- priority: release blocker -> high ___ Python tracker ___ _

[issue7185] csv reader utf-8 BOM error

Changes by Skip Montanaro : -- nosy: +skip.montanaro ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5713] smtplib gets out of sync if server returns a 421 status

Mark Sapiro added the comment: I'm not completely sure about this, but here's my thoughts. In the scenarios I've seen, the 421 reply/disconnect only occurs in response to a RCPT which has an invalid address and follows several prior refused RCPTs. In this case, I think the proper action is to cl

[issue1235] CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7185] csv reader utf-8 BOM error

R. David Murray added the comment: In that case we should update the docs. Istvan, can you confirm that this solves your problem? -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl stage: test needed -> needs patch versions: +Python 3.2 __

[issue7006] The replacement suggested for callable(x) in py3k is not equivalent

Georg Brandl added the comment: 2to3 still uses hasattr(x, 'callable'). -- assignee: georg.brandl -> benjamin.peterson ___ Python tracker ___

[issue6670] Printing the 'The Python Tutorial'

Georg Brandl added the comment: OK, fixed in Sphinx, and in the Python stylesheet in r75617. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue6927] Metaclass doc (Ref 3.3.3) errors

Georg Brandl added the comment: Fixed based/passed in r75616, the rest will be done for #1294232. -- resolution: -> fixed status: open -> closed superseder: -> Error in metaclass search order ___ Python tracker _

[issue7067] Suggest better documentation of 2 versus 3 on 3.1.1 site.

Steven R. Loomis added the comment: welcome, looks great! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

R. David Murray added the comment: I'm not sure you do. I have no idea how Boost works, but the fact that removing a Boost 'read-only' declaration circumvents the problem in at least some cases argues that Boost is setting _something_ read-only. --

[issue6977] Getopt documentation ambiguity

Georg Brandl added the comment: Fixed in r75613. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue7156] curses can't find _curses

Georg Brandl added the comment: Added "Platform: Unix" to curses docs in r75612. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue7067] Suggest better documentation of 2 versus 3 on 3.1.1 site.

Georg Brandl added the comment: Thanks, this is now fixed. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

Antoine Pitrou added the comment: I'm not sure I understand, how do you create a "read-only instance dict"? -- nosy: +pitrou ___ Python tracker ___ __

[issue7035] codecs error handlers lack documentation

Georg Brandl added the comment: Thanks, fixed in r75611. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7036] Doc/reference/datamodel: Slots description needs update

Georg Brandl added the comment: As far as I can tell, the text is still correct: >>> class a(object): __slots__ = 'a' >>> class b(a): __slots__ = 'a' works without raising TypeError. I've nevertheless enhanced the docs a bit in r75610. -- resolution: -> fixed status: open -> closed

[issue7062] No docs for module 'IN'

Georg Brandl added the comment: That's the case for all undocumented modules (there are some like IN, that only contain constants; they're also going away in Py3k). However, pydoc can't know which modules are documented, so I'm going to close this as "won't fix". -- resolution: -> won

[issue7067] Suggest better documentation of 2 versus 3 on 3.1.1 site.

Steven R. Loomis added the comment: Thnks for fixing this. there still seems to be something up with http://python.org/download/releases/3.1.1/ - it says 'Inline interpreted text or phrase reference start-string without end-string.' and the changelog link is broken. But I see the new links.

[issue7137] Socket documentation not updated

Georg Brandl added the comment: Thanks, fixed in r75609. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7067] Suggest better documentation of 2 versus 3 on 3.1.1 site.

Georg Brandl added the comment: I added the 3.0 whatsnew and 2to3 links in (pydotorg) r12618. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue7088] New (in 2.6) functions in signal module are not documented as unix-only

Georg Brandl added the comment: Thanks, fixed in r75607. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

Barry A. Warsaw added the comment: Thanks David, that's what I suspect too (that's its a problem with extension types). Unless we get more information, I'm not inclined to hold up the 2.6.4 release for this. -- ___ Python tracker

[issue6324] "in" expression falls back to __iter__ before __getitem__

Georg Brandl added the comment: Thanks, fixed in r75606. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7185] csv reader utf-8 BOM error

Walter Dörwald added the comment: Then the solution should simply be to use "utf-8-sig" as the encoding, instead of "utf-8". -- ___ Python tracker ___ ___

[issue7185] csv reader utf-8 BOM error

R. David Murray added the comment: The restrictions were theoretically removed in 3.1, and the 3.1 documentation has been updated to reflect that. If 3.1 CSV doesn't handle unicode, then that is a bug. -- nosy: +r.david.murray priority: -> normal stage: -> test needed type: compile e

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

R. David Murray added the comment: That should have been 'instance's dict', not the subclass dict. -- ___ Python tracker ___ ___ Pytho

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

R. David Murray added the comment: I added some tests in test_property in my checkout and the __doc__ property is not, as far as I can tell, set read-only by the issue 5890 fix. The error message referenced in the report is: AttributeError: 'Boost.Python.StaticProperty' object attribute '__doc

[issue7183] did 2.6.3 regress for some uses of the __doc__ property?

Barry A. Warsaw added the comment: Robert indicated later that this probably did /not/ affect Bazaar. -- ___ Python tracker ___ ___ Py

[issue7185] csv reader utf-8 BOM error

Walter Dörwald added the comment: http://docs.python.org/library/csv.html#module-csv states: This version of the csv module doesn’t support Unicode input. Also, there are currently some issues regarding ASCII NUL characters. Accordingly, all input should be UTF-8 or printable ASCII to be safe;

[issue7185] csv reader utf-8 BOM error

New submission from Istvan Szirtes : The CSV module try to read a .csv file which is coded in utf-8 with utf- 8 BOM. The first row in the csv file is ["value","vocal","vocal","vocal","vocal"] in hex: "value","vocal","vocal","vocal","vocal" the reader can not read corectly the first row an

[issue3605] Py_FatalError causes infinite loop

Changes by lekma : -- nosy: +lekma ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailma

[issue1235] CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks

Changes by Stac : Removed file: http://bugs.python.org/file15175/MyCGIHTTPServer.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue1235] CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks

Derk Drukker added the comment: The original problem reported concerned spaces in the path of the python executable. So interp needs to be in quotes, as well (as Andy already suggested). I've created a patch against the latest py3k, which I've confirmed works and fixes this issue. I'm not a c

[issue1235] CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks

Stac added the comment: Ok, I corrected the two versions. Now the one for py2.x is closer to the fix for py3k. You'll find below the fixed code for both version. Regards, Stac -- Added file: http://bugs.python.org/file15180/fix.tar ___ Python trac

[issue1235] CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks

Stac added the comment: Oups, I really feel sorry. Well here is a version with the modified cmdline. I will check how the migration was done in py3k. Just a quick question : why the changes done in py3k was not reported to py2.x ? Regards, Stac -- Added file: http://bugs.python.org