[issue29767] build python failed on test_socket due to unused_port is actually used.

Xiang Zhang added the comment: Could you show the failure message here? And you could make your patch a PR on GitHub. -- nosy: +xiang.zhang ___ Python tracker

[issue29764] PyUnicode_Decode with encoding utf8 crashes

Xiang Zhang added the comment: You need to first call `Py_Initialize()` to initialize the Python interpreter. It is required. -- nosy: +xiang.zhang resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue20087] Mismatch between glibc and X11 locale.alias

Benjamin Peterson added the comment: "eo_XX" is just something that appears in the X11 locale.alias file. My change doesn't add that; it was already there. (for Esperanto, which I suppose explains the "XX") Most of the changes you identify the glibc aliases taking precedence over the X11

[issue29759] Deadlock in multiprocessing.pool.Pool on terminate

Changes by Xiang Zhang : -- nosy: +davin versions: -Python 3.3, Python 3.4 ___ Python tracker ___

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Changes by Nick Coghlan : -- versions: +Python 3.7 ___ Python tracker ___ ___

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Nick Coghlan added the comment: OK, https://github.com/python/cpython/pull/575 is the new PR that covers everything needed to fix the root cause of the problem (which was the entirely unnecessary add-and-overwrite dance that zipfile and directory executation was doing for sys.path[0])

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Changes by Nick Coghlan : -- pull_requests: +471 ___ Python tracker ___ ___

[issue29319] Embedded 3.6.0 distribution cannot run pyz files

Changes by Nick Coghlan : -- pull_requests: +472 ___ Python tracker ___ ___

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Nick Coghlan added the comment: Slightly correction, as I didn't have the isolated mode equivalents quite correct: python3 -s script_dir/__main__.py python3 -s script_dir python3 -I script_dir Isolated mode still runs the system site.py, which turns out to be signficant in a

[issue29760] tarfile chokes on reading .tar file with no entries (but does fine if the same file is bzip2'ed)

Changes by Serhiy Storchaka : -- nosy: +lars.gustaebel type: crash -> behavior versions: -Python 3.3, Python 3.4 ___ Python tracker

[issue29762] Use "raise from None"

Serhiy Storchaka added the comment: I don't think this is needed. The traceback points to the actual line -- the line with the "raise" statement. -- ___ Python tracker

[issue29768] Fix expact version check

Changes by Serhiy Storchaka : -- pull_requests: +470 ___ Python tracker ___ ___

[issue29768] Fix expact version check

New submission from Serhiy Storchaka: The compile-time check for expat version added in issue14234 doesn't work with expat 3.0.0. Following PR fixes this. -- components: Extension Modules, XML messages: 289273 nosy: gregory.p.smith, serhiy.storchaka priority: normal severity: normal

[issue29682] Possible missing NULL check in pyexpat

Serhiy Storchaka added the comment: Thank you Alex and svelankar for your report and fix. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue29682] Possible missing NULL check in pyexpat

Changes by svelankar : -- pull_requests: +469 ___ Python tracker ___ ___

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Nick Coghlan added the comment: Work in progress PR at https://github.com/python/cpython/pull/571 I also came up with a reasonably straightforward way of defining the desired "sys.path" initialisation behaviour, which is that the following should all get the *same* sys.path entries:

[issue29756] Improve documentation for list methods that compare items by equality

Changes by Xiang Zhang : -- pull_requests: +468 ___ Python tracker ___ ___ Python-bugs-list

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Changes by Nick Coghlan : -- pull_requests: +467 ___ Python tracker ___ ___

[issue29756] Improve documentation for list methods that compare items by equality

Xiang Zhang added the comment: +1 for jsoh. Actually the behaviour is documented in https://docs.python.org/3/reference/expressions.html#value-comparisons. So a single 'a is b' or 'a == b' is not complete. I would like to use 'equal to' which implies 'a is b or a == b'. -- nosy:

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Nick Coghlan added the comment: As Eryk notes, this has revealed a separate bug in that we don't make the path absolute when adding to sys.path. However, that's *not* directly related to the regression, so I'm resisting the temptation to change it here. Instead, the new test case I'm adding

[issue29767] build python failed on test_socket due to unused_port is actually used.

New submission from Shuo Li: I am running a debian system. And trying to build cpython3.6 from source. When I run make altinstall, it failed on test_socket. Reporting cli attribute is missing. After some trouble shooting, it seems the support.get_unused_port() is not reliable. Then I

[issue29762] Use "raise from None"

Josh Rosenberg added the comment: Particularly when the type of the exception isn't being changed, it's only altering the message to provide more information? -- ___ Python tracker

[issue29762] Use "raise from None"

Josh Rosenberg added the comment: To tie the exceptions to the actual line, would it perhaps make sense to copy over the traceback of the original exception using .with_traceback? -- nosy: +josh.r ___ Python tracker

[issue29758] Previously-working SWIG code fails in Python 3.6

Changes by Xiang Zhang : -- nosy: +haypo, serhiy.storchaka ___ Python tracker ___ ___

[issue29760] tarfile chokes on reading .tar file with no entries (but does fine if the same file is bzip2'ed)

Matt Bogosian added the comment: FWIW, the (offending) fix for #24259 was introduced (e.g., in 2.7) via 2.7.10. I've verified that 2.7.9 works as expected: ``` $ python -V Python 2.7.9 $ python tarfail.py opening /…/tarfail/test.tar.bz2 opening /…/tarfail/test.tar .

[issue10408] Denser dicts and linear probing

Raymond Hettinger added the comment: Agreed. This doesn't make sense for the compact dict implementation. -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker

[issue29766] --with-lto still implied by --enable-optimizations in Python 2.7

New submission from Hanno Schlichting: I think the fix for issue28032 wasn't applied correctly to the 2.7 branch. Compare the change in Python 2.7: https://github.com/python/cpython/commit/9cbfa79111e7152231556a21af90a220b72ed086#diff-e2d5a00791bce9a01f99bc6fd613a39dL6425 vs. for example

[issue29765] 2.7.12 compile error from ssl related

New submission from ada: Download the python version 2.7.12 source code from official web site. Compile the python code by the following steps: sudo ./configure sudo make sudo make install but from make, I get the following errors: /Modules/_ssl.c: In function ‘_create_tuple_for_X509_NAME’:

[issue29764] PyUnicode_Decode with encoding utf8 crashes

New submission from Alexey Trenikhin: #include int main(){ PyUnicode_Decode("abcdef", 4, "utf_8", "ignore"); return 0; } crashes on linux and Windows (but works fine with encoding "utf-8" ) -- components: Unicode files: test.c messages: 289261 nosy: Alexey Trenikhin,

[issue29749] Outdated int() docstring

Changes by Brett Cannon : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29759] Deadlock in multiprocessing.pool.Pool on terminate

Changes by Michael : -- type: -> behavior versions: +Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

Changes by Oren Milman : -- pull_requests: +466 ___ Python tracker ___ ___ Python-bugs-list

[issue29763] test_site failing on AppVeyor

New submission from Brett Cannon: E.g. https://ci.appveyor.com/project/python/cpython/build/3.7.0a0.142. This looks to be the last consistent failure on AppVeyor. -- components: Windows messages: 289260 nosy: brett.cannon, paul.moore, steve.dower, tim.golden, zach.ware priority: normal

[issue29761] Wrong size of c_ulong in linux, windows version is fine

Eryk Sun added the comment: ctypes is correct. 64-bit Linux uses an LP64 data model, and 64-bit Windows uses LLP64. https://en.wikipedia.org/wiki/64-bit_computing#64-bit_data_models -- nosy: +eryksun resolution: -> not a bug stage: -> resolved status: open -> closed

[issue29762] Use "raise from None"

Changes by Serhiy Storchaka : -- pull_requests: +465 ___ Python tracker ___ ___

[issue29762] Use "raise from None"

New submission from Serhiy Storchaka: Sometimes after catching some exception the new exception of more appropriate type and with more appropriate message is raised. The initial exception often is not relevant to the final exception, it is raised only due to using EAFP rather than LBYL. It

[issue29761] Wrong size of c_ulong in linux, windows version is fine

New submission from Jorge Cisneros: In the linux version 2.7.12 the size of c_ulong and c_ulonglong is the same, that is not correct Python 2.7.12 (default, Mar 6 2017, 18:06:04) [GCC 4.9.4] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from ctypes

[issue28810] Document bytecode changes in 3.6

Ivan Levkivskyi added the comment: It looks like there are still few things that are not covered in two open PRs. I will add these in an additional PR in the next few days. -- ___ Python tracker

[issue29749] Outdated int() docstring

Serhiy Storchaka added the comment: After converting int.__new__() to Argument Clinic this issue will become outdated. -- ___ Python tracker ___

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Eryk Sun added the comment: main361 can be run as a package from the current directory via -m because an empty string is in sys.path, i.e. the current directory. It imports the package, executing __init__.py and then __main__.py. In this case, the main361 directory/zip import source is not

[issue29760] tarfile chokes on reading .tar file with no entries (but does fine if the same file is bzip2'ed)

New submission from Matt Bogosian: It looks like there's a problem examining ``.tar`` files with no entries: ``` $ # == $ # Extract test cases (attached to this bug report) $ tar xpvf tarfail.tar.bz2 x tarfail/ x tarfail/tarfail.py

[issue29749] Outdated int() docstring

Changes by Serhiy Storchaka : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue29749] Outdated int() docstring

svelankar added the comment: True, but the docstring says "return 0 if no arguments are given". So please let me know, if you want me to still change it i.e. add int() or keep it as it is. Thanks. -- ___ Python tracker

[issue29749] Outdated int() docstring

Serhiy Storchaka added the comment: int() can be called without argument. -- ___ Python tracker ___ ___

[issue28810] Document bytecode changes in 3.6

Brett Cannon added the comment: If the "ping" is for me, I spent my open source day last week reviewing the dependency for this issue (and other stuff) so I plan to get to this PR this Friday. -- ___ Python tracker

[issue29759] Deadlock in multiprocessing.pool.Pool on terminate

Michael added the comment: This patch kind of solves the issue. Not a nice one, but perhaps the safest one. https://github.com/michael-a-cliqz/cpython/commit/1536c8c8cfc5a87ad4ab84d1248cb50fefe166ae -- ___ Python tracker

[issue29749] Outdated int() docstring

Changes by Roundup Robot : -- pull_requests: +464 ___ Python tracker ___

[issue29759] Deadlock in multiprocessing.pool.Pool on terminate

New submission from Michael: Following code snippet causes a deadlock on Linux: """ import multiprocessing.pool import signal def signal_handler(signum, frame): pass if __name__ == '__main__': signal.signal(signal.SIGTERM, signal_handler) pool =

[issue28810] Document bytecode changes in 3.6

Serhiy Storchaka added the comment: Ping. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue29749] Outdated int() docstring

svelankar added the comment: int docstring is the only one that needs to be changed. docstrings for float,tuple and list look fine to me. -- nosy: +svelankar ___ Python tracker

[issue26259] Memleak when repeated calls to asyncio.queue.Queue.get is performed, without push to queue.

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue29758] Previously-working SWIG code fails in Python 3.6

New submission from Tristan Croll: Possibly related to http://bugs.python.org/issue29327 - yields the same error message: Objects/tupleobject.c:81: bad argument to internal function I have a large SWIG project which was previously working well in Python 3.5. After migrating to Python 3.6.0,

[issue26259] Memleak when repeated calls to asyncio.queue.Queue.get is performed, without push to queue.

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___

[issue26259] Memleak when repeated calls to asyncio.queue.Queue.get is performed, without push to queue.

Bartek Biernacki added the comment: I ran into similar problem with many getters timing out and staying in memory until some put is called. I think this may be solved by using a callback on Future which would clean it if it was cancelled. I am presenting the idea on attached poc. If you

[issue28682] Bytes support in os.fwalk()

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29756] Improve documentation for list methods that compare items by equality

Josh Rosenberg added the comment: Steven: Technically, in CPython, they use both identity and equality testing, as a function of using RichCompareBool (which tests identity first, then equality), rather than RichCompare (which only tests equality). It makes a difference for stuff like NaN

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: Why was the PR merged while we were still discussing it ? -- ___ Python tracker ___

[issue29752] Enum._missing_ not called for __getattr__ failures

Josh Rosenberg added the comment: Could that perhaps be intentional? Attribute access seems like something where the developer would be explicitly naming a single, hard coded, canonical name for the type, while string construction seems like something where you're getting a string from

[issue29645] webbrowser module import has heavy side effects

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29756] Improve documentation for list methods that compare items by equality

Steven D'Aprano added the comment: To be clear, I'm referring to the docs in the tutorial: https://docs.python.org/3.7/tutorial/datastructures.html and the docstrings as well as the library reference: https://docs.python.org/3.7/library/stdtypes.html#sequence-types-list-tuple-range The

[issue29756] Improve documentation for list methods that compare items by equality

Steven D'Aprano added the comment: Further to Barry's explanation, you see the same result with any values which compare equal: py> from decimal import Decimal as D py> [1, 1.0, D(1), True, 1+0j].count(D(1)) 5 This is standard behaviour for methods `count`, `remove`, and `index`, but it

[issue29757] The loop in utility `socket.create_connection()` swallows previous errors

New submission from Kostis Anagnostopoulos: ## Context The utility method `socket.create_connection()` currently works like that: 1. resolve the destination-address into one or more IP(v4 & v6) addresses; 2. loop on each IP address and stop to the 1st one to work; 3. if none works, re-raise the

[issue29723] 3.6.1rc1 adds the current directory to sys.path when running a subdirectory's __main__.py; previous versions did not

Steve Dower added the comment: > C:\Temp doesn't belong in sys.path in this case Hang on, why not? If I were running a module.py then it would be, so why is a package\__main__.py different (and not able to import itself or its siblings)? The package is the "script" being run here, yes? Or is

[issue29756] List count() counts True as 1

Barry A. Warsaw added the comment: bools are subclasses of int and False and True have integer equivalents: https://docs.python.org/3/library/stdtypes.html#bltin-boolean-values -- nosy: +barry resolution: -> not a bug stage: -> resolved status: open -> closed

[issue28231] zipfile does not support pathlib

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29756] List count() counts True as 1

New submission from Alexander Todorov: When using list.count() I get the following results >>> [1, 2, 3].count(1) 1 >>> [1, 2, 3, True].count(2) 1 >>> [1, 2, 3, True].count(True) 2 >>> [1, 2, 3, True].count(1) 2 as you can see True is considered the same as 1.

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

Oren Milman added the comment: yes and yes. I would start with a PR for 3.7. and thanks for the review :) -- ___ Python tracker ___

[issue28231] zipfile does not support pathlib

Changes by Serhiy Storchaka : -- pull_requests: +462 ___ Python tracker ___ ___

[issue29747] unittest - assertDoesNotRaise

Vinícius Dantas added the comment: As a last argument: It is a matter of coherence/consistency with unittest's API, given that this module does differentiates errors from failures -- ___ Python tracker

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Changes by Oren Milman : -- pull_requests: +461 ___ Python tracker ___ ___ Python-bugs-list

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: On 08.03.2017 10:37, Serhiy Storchaka wrote: > > The problem is that that table can get incorrect result for non-Linux > platforms (or for Linux with old glibc). Sure, it's a best effort approach. Also note that on today's systems you often don't have

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: On 08.03.2017 07:27, Benjamin Peterson wrote: > > Why is the X11 locale alias map used at all? It seems like it can only create > confusion with libc. Because it was the only such maintained mapping available at the time. It's also used for the X.org

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Serhiy Storchaka added the comment: This for your preference. -- ___ Python tracker ___ ___ Python-bugs-list

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Oren Milman added the comment: sure. In general, should drafts (like this one) be uploaded here? or is it always better to open a PR? -- ___ Python tracker

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Serhiy Storchaka added the comment: Open a PR. It will be not hard to make small changes after opening it. -- ___ Python tracker ___

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Oren Milman added the comment: should I open a PR (even though we didn't give Florent enough time to respond)? -- ___ Python tracker ___

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Serhiy Storchaka added the comment: LGTM. -- nosy: +stutzbach ___ Python tracker ___ ___ Python-bugs-list

[issue29741] BytesIO methods don't accept integer types, while StringIO counterparts do

Oren Milman added the comment: I wrote a patch, but I attach it here and not in a PR, as you haven't approved adding tests. (I would be happy to open a PR with or without the tests.) I ran the test module (on my Windows 10), and seems like the patch doesn't break anything. also, while running

[issue10408] Denser dicts and linear probing

Serhiy Storchaka added the comment: I think this issue is outdated. Liner probing doesn't make much sense for current dict implementation. -- status: open -> pending ___ Python tracker

[issue20087] Mismatch between glibc and X11 locale.alias

Serhiy Storchaka added the comment: The problem is that that table can get incorrect result for non-Linux platforms (or for Linux with old glibc). -- ___ Python tracker

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: On 08.03.2017 08:20, Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > > Not all platforms use glibc 2.24 as libc. True. Many don't even use glibc. > Ideally most of entries should even not exist. We should ask libc for the > default

[issue29619] st_ino (unsigned long long) is casted to long long in posixmodule.c:_pystat_fromstructstat

Serhiy Storchaka added the comment: I think it is worth to backport this at least to 3.6. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue29755] python3 gettext.lgettext sometimes returns bytes, not string

Changes by Serhiy Storchaka : -- components: +Library (Lib) nosy: +loewis, serhiy.storchaka versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.4 ___ Python tracker

[issue29755] python3 gettext.lgettext sometimes returns bytes, not string

New submission from Petri Savolainen: On Debian stable (Python 3.4), with the LANGUAGE environment variable set to "C" or "en_US.UTF-8", the following produces a string: d = gettext.textdomain('apt-listchanges') print(gettext.lgettext("Informational notes")) However, setting the language, for

[issue28230] tarfile does not support pathlib

Changes by Serhiy Storchaka : -- pull_requests: +460 ___ Python tracker ___ ___

[issue29537] Alternative fix for BUILD_MAP_UNPACK_WITH_CALL opcode in 3.5

Changes by Nick Coghlan : -- pull_requests: +459 ___ Python tracker ___ ___

[issue29751] PyLong_FromString fails on decimals with leading zero and base=0

Mark Dickinson added the comment: Yes, PyLong_FromString is directly used by the implementation of int, and is also used in parsing of numeric integer literals in source: https://github.com/python/cpython/blob/cb41b2766de646435743b6af7dd152751b54e73f/Python/ast.c#L4084 So I agree that this is

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

Serhiy Storchaka added the comment: LGTM. But maybe combine PyFloat_Check+_PyLong_FromNbInt in one helper function? Could you please create a PR Oren? -- stage: patch review -> commit review versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue29754] sorted ignores reverse=True when sorting produces same list

Tomas Dabašinskas added the comment: Thanks for taking time to review and respond Tim! (; -- ___ Python tracker ___

[issue29619] st_ino (unsigned long long) is casted to long long in posixmodule.c:_pystat_fromstructstat

STINNER Victor added the comment: On Windows, _Py_attribute_data_to_stat() converts BY_HANDLE_FILE_INFORMATION to _Py_stat_struct, and then _pystat_fromstructstat() creates Python objects. The file index in BY_HANDLE_FILE_INFORMATION is made of two DWORD, so yes, it's unsigned. On Linux,

[issue29619] st_ino (unsigned long long) is casted to long long in posixmodule.c:_pystat_fromstructstat

Changes by STINNER Victor : -- pull_requests: +458 ___ Python tracker ___ ___