[issue19543] Add -3 warnings for codec convenience method changes

Nick Coghlan added the comment: I think so - if anyone spots another place a Py3k warning could be usefully emitted, it can be handled as a new issue. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue26344] `sys.meta_path` Skipped for Packages with Non-Standard Suffixed `__init__` Files

Brett Cannon added the comment: I found the problem: you have a bug in your code at line 45 (the first line of WolfPathFinder.find_spec()). When you try and import a top-level package the path will always be None since __path__ doesn't exist for a top-level package. You only end up with a `pat

[issue26347] BoundArguments.apply_defaults doesn't handle empty arguments

New submission from Frederick Wagner: [First-time contributor, feedback appreciated.] Found and fixed some unexpected behavior in inspect.BoundArguments.apply_defaults. Simplest explanation is the following test that I added: # Make sure a no-args binding still acquires proper default

[issue26339] Python rk0.3b1 KeyError: 'config_argparse_rel_path'

Berker Peksag added the comment: Thanks for the report, but both rk and configobj are not part of the Python standard library. Please use their issue tracker to report your problem. -- nosy: +berker.peksag resolution: -> not a bug stage: -> resolved status: open -> closed ___

[issue26180] multiprocessing.util._afterfork_registry leak in threaded environment

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue26347] BoundArguments.apply_defaults doesn't handle empty arguments

Martin Panter added the comment: Patch looks good to me -- nosy: +martin.panter stage: -> patch review ___ Python tracker ___ ___ Pyt

[issue26346] PySequenceMethods documentation missing sq_slice and sq_ass_slice

Martin Panter added the comment: Maybe they are missing because they don’t exist in Python 3 :) Perhaps what is needed instead is a list of the actual fields in order, since I assume Python supports compilers that can’t use the

[issue26346] PySequenceMethods documentation missing sq_slice and sq_ass_slice

Anthony Tuininga added the comment: Ah yes. The fields are still there, though, just marked as not used. Interestingly enough they aren't documented in the Python 2 documentation eitherand they are in the Python 2.7 headers I have (not marked as unused either). Your suggestion makes sense

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Robert P Fischer added the comment: > The makefiles use CC throughout and don't look at and OBJC variable. Is > that variable a standard way to specify an ObjC compiler in makefiles? I believe that OBJC and OBJCFLAGS are standard for Autoconf/Automake: https://www.gnu.org/software/automake/manu

[issue26343] os.O_CLOEXEC not available on OS X

Gustavo Goretkin added the comment: Can the documentation be updated accordingly? Currently the documentation (roughly) says that this is available. If not separately noted, all functions that claim “Availability: Unix” are supported on Mac OS X, which builds on a Unix core. os.O_EXLOCK

[issue26253] tarfile in stream mode always set zlib compression level to 9

Changes by Ned Deily : -- nosy: +lars.gustaebel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue26343] os.O_CLOEXEC not available on OS X

Ned Deily added the comment: This is only one example of many cases of calls and options that are exposed by the os module but are not available on specific platforms or platform releases. It would be a huge documentation effort to try to identify and keep them all up-to-date. The fourth bul

[issue26279] time.strptime does not properly convert out-of-bounds values

Ned Deily added the comment: Thanks for the report. Closing this issue as a duplicate of Issue23719. -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> PEP 475: port test_eintr to Windows ___ Pyth

[issue26279] time.strptime does not properly convert out-of-bounds values

Ned Deily added the comment: Make that Issue23718 -- superseder: PEP 475: port test_eintr to Windows -> strptime() can produce invalid date with negative year day ___ Python tracker ___

[issue23718] strptime() can produce invalid date with negative year day

Changes by Ned Deily : -- nosy: +iaslan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

<    1   2