[issue15246] Line coverage for collectionts.abc.Set

Changes by Antoine Pitrou : -- nosy: +rhettinger, stutzbach stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10574] email.header.decode_header fails if the string contains multiple directives

Roy Hyunjin Han added the comment: > This is fixed by the fix to issue 1079, but we have decided that fix can't be > backported because it is a behavior change that might break existing working > programs. Thanks for this update. -- ___ Python tra

[issue15249] email.generator.BytesGenerator doesn't mangle "From " lines when non-ASCII bytes are present

New submission from Petri Lehtinen : The _handle_text function of BytesGenerator writes the payload straight through if there surrogateescape sequences are present, and skips the "From " mangling. -- components: email messages: 164641 nosy: barry, petri.lehtinen, r.david.murray priority

[issue15246] Line coverage for collectionts.abc.Set

Mark Dickinson added the comment: Can you attach the failing tests for __and__? -- nosy: +mark.dickinson ___ Python tracker ___ ___ P

[issue15205] distutils dereferences symlinks on Mac OS X but not on Linux

Ollie Walsh added the comment: Hi, > As I said in the other bug, symlinks handling in not fully specified Yes. I've mostly submitted a bug report in case anybody else encounters the problem. > At present I am not sure if having symlinks in a distribution makes sense I agree. In my case syml

[issue15205] distutils dereferences symlinks on Mac OS X but not on Linux

Ollie Walsh added the comment: PS that should be os.readlink() -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue15210] importlib.__init__ checks for the wrong exception when looking for _frozen_importlib

Brett Cannon added the comment: Thanks for the diagnosis, Stefan. Unfortunately that line is the crux of the test. =) I will see if I can steal some time to look at the failure to see if there is anything obvious going on. -- ___ Python tracker

[issue15250] document that filecmp.dircmp comparisons are "shallow"

New submission from Chris Jerdonek : The documentation for the dircmp class doesn't say that the same_files and diff_files attributes are determined using the "shallow=True" rules described in the filecmp.cmp() and filecmp.cmpfiles(). It should say this. For example, the documentation describ

[issue15139] Speed up threading.Condition wakeup

Matt Joiner added the comment: Did this make it into 3.3? -- nosy: +anacrolix ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue12932] filecmp.dircmp does not allow non-shallow comparisons

Chris Jerdonek added the comment: +1 for this. Whether or not this feature is implemented, I think the documentation should state that directory comparisons are done using "shallow=True". I created issue 15250 for this. -- nosy: +cjerdonek ___ Py

[issue15245] ast.literal_eval fails on some literals

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue15210] importlib.__init__ checks for the wrong exception when looking for _frozen_importlib

Chris Jerdonek added the comment: I could be way off (just passing through), but the test flakiness described here seems reminiscent of a discussion we had for issue 7559. There the solution to order-dependent tests with importlib involved calling importlib.invalidate_caches() at the appropr

[issue15139] Speed up threading.Condition wakeup

Gregory P. Smith added the comment: Nope. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue15245] ast.literal_eval fails on some literals

Daniel Urban added the comment: eval(repr(float('nan'))) doesn't work either, so I'm not sure ast.literal_eval should. The same with float('inf'). -- nosy: +daniel.urban ___ Python tracker ___

[issue15251] new.code and new.function crashes Python iterpretter

New submission from Jeffrey Harper : I've attached a script that crashes the Python interpreter. I can get the crash to occur under Windows Vista with this version of Python: C:\tmp\remote>c:\Python27\python.exe Python 2.7.1 Stackless 3.1b3 060516 (release27-maint, Jan 1 2011, 13:04:37) [MS

[issue15251] new.code and new.function crashes Python iterpretter

Jeffrey Harper added the comment: The marshal loads and dumps don't seem to be necessary to reproduce the crash. On both the Windows Vista and Ubuntu Linux systems, the crash still occurred when I replaced: mcopy_code = loads(dumps(code)) with: mcopy_code = code #loads(dumps(code)) --

[issue15251] new.code and new.function crashes Python iterpretter

Martin v. Löwis added the comment: You need to pass co_freevars and co_cellvars as well for your example to work. It shouldn't crash, but I don't consider this particular crash as a bug, as it is a known limitation that new.code doesn't perform all consistency checks that are necessary to gua

[issue15247] io.open() is inconsistent re os.open()

Antoine Pitrou added the comment: Good catch indeed. -- components: +IO nosy: +pitrou stage: -> needs patch versions: +Python 3.2 ___ Python tracker ___ ___

[issue15210] importlib.__init__ checks for the wrong exception when looking for _frozen_importlib

Roundup Robot added the comment: New changeset 906c69928049 by Brett Cannon in branch 'default': Issue #15210: Greatly simplify the test for supporting importlib http://hg.python.org/cpython/rev/906c69928049 -- ___ Python tracker

[issue15210] importlib.__init__ checks for the wrong exception when looking for _frozen_importlib

Brett Cannon added the comment: I realized the problem was that _frozen_importlib was getting set to None, which won't trigger an exception since the code was just directly accessing sys.modules. I switched to an ``import ... as ...`` clause and moved to using test.support.import_fresh_module

[issue15245] ast.literal_eval fails on some literals

João Bernardo added the comment: That's what I said by `nan` and `inf` are not literals, but their representations look like they should be. One solution could be to add another argument to allow some extra names. Maybe a mapping, as `eval`. -- __

[issue15210] importlib.__init__ checks for the wrong exception when looking for _frozen_importlib

Antoine Pitrou added the comment: Thanks Brett! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue3561] Windows installer should add Python and Scripts directories to the PATH environment variable

Jason Spiro added the comment: I'm glad you're willing to consider using a checkbox. It seems to fit better with the wizard paradigm, where there are always [ < Back ], [ Next > ], and [ Cancel ] buttons onscreen. OK, I acknowledge that a lot of third-party software still depends on Python 2.

[issue3561] Windows installer should add Python and Scripts directories to the PATH environment variable

Brian Curtin added the comment: We don't need to stay with some paradigm if it's not the best way. If I can get any of these ways to work, I may post some type of survey on python-dev. Adding to the end wouldn't make this much of a feature. Most users have already put another Python into thei

[issue3561] Windows installer should add Python and Scripts directories to the PATH environment variable

Jason Spiro added the comment: Adding Python to the end of the PATH would very much help Windows non-experts who don't even know what a PATH is. IMO, when Python 3.4 comes out, it'd make sense add Python to the end of the PATH by default. This'd help those non-experts a lot. On 7/4/12, Brian

[issue15251] new.code and new.function crashes Python iterpretter

Jeffrey Harper added the comment: Martin, Thanks for your response. I didn't know it was possible to pass freevars and cellvars to new.code. I think the documentation needs to be updated. The documentation for 2.7.3 located at http://docs.python.org/library/new.html?highlight=new#new.code

[issue15247] io.open() is inconsistent re os.open()

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15247] io.open() is inconsistent re os.open()

Juancarlo Añez added the comment: Note that attempting subsequent operations on the returned object do raise IsADirectoryError. >>> import io >>> import os >>> d = io.open(os.open('.',0)) >>> d.read() Traceback (most recent call last): File "", line 1, in IsADirectoryError: [Errno 21] Is a

[issue15033] Different exit status when using -m

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15020] default value for progname in pythonrun.c should be python3 for Python 3

Arfrever Frehtes Taifersar Arahesis added the comment: Maybe it would be better to use L"python3.2" for Python 3.2 and L"python3.3" for Python 3.3. -- nosy: +Arfrever ___ Python tracker __

[issue15242] PyImport_GetMagicTag() should use the same const char * as sys.implementation.cache_tag

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15245] ast.literal_eval fails on some literals

Benjamin Peterson added the comment: I don't think literal_eval should handle anything which is not syntax. -- ___ Python tracker ___ ___

[issue15033] Different exit status when using -m

Roundup Robot added the comment: New changeset fcbd3bda7c0f by Senthil Kumaran in branch '3.2': Fix issue # 15033 - Return the proper exitcode for failure when modules are invoked using -m switch. Patch contributed by Jeff Knupp http://hg.python.org/cpython/rev/fcbd3bda7c0f New changeset 1186d

[issue15033] Different exit status when using -m

Roundup Robot added the comment: New changeset 55b3de6d701e by Senthil Kumaran in branch '2.7': Fix closes issue # 15033 - Return the proper exitcode for failure when modules are invoked using -m switch. Patch contributed by Jeff Knupp http://hg.python.org/cpython/rev/55b3de6d701e --

[issue15033] Different exit status when using -m

Senthil Kumaran added the comment: Thanks for the patch Jeff and thanks for the guidance, Nick. Committed this in all branches. -- nosy: +orsenthil resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tra

[issue15250] document that filecmp.dircmp comparisons are "shallow"

Changes by Éric Araujo : -- stage: -> needs patch versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list maili

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

Nick Coghlan added the comment: I've thought of a different approach to this which should be less hazardous to doctests: include the truncation warning in the *traceback* section, rather than in the header. doctests already ignore the details of that section because checking it is too fragile

[issue15249] email.generator.BytesGenerator doesn't mangle "From " lines when non-ASCII bytes are present

Petri Lehtinen added the comment: Attached a test case that fails. -- keywords: +patch Added file: http://bugs.python.org/file26258/issue115249_test.patch ___ Python tracker ___

[issue15222] mailbox.mbox writes without empty line after each message

Petri Lehtinen added the comment: Well, by appending newmail to the mailbox, you effectively break the next-to-last message by not inserting a newline after it. This can also be achieved by adding a message that doesn't end in a newline to the mbox (using the mailbox module). The real bug is