[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Serhiy Storchaka added the comment: Perhaps it is worth to backport warnings to 2.7 in Py3k mode. This could help to detect some issues earlier. In 3.6 fields could be converted to lists silently, without warnings. --

[issue29519] weakref spewing exceptions during finalization when combined with multiprocessing

Warwick Chapman added the comment: Will this be released in 2.x as suggested by inada.naoki? -- nosy: +Warwick Chapman ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: I like Nick's idea of calling list() to fix the argument. I've created a PR that implements it. I also generate a RuntimeWarning since if we document them as needing to be lists, we should at least warn for invalid types. The

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Change by Neil Schemenauer : -- pull_requests: +4598 stage: resolved -> patch review ___ Python tracker ___

[issue29710] Incorrect representation caveat on bitwise operation docs

Tim Peters added the comment: To answer the old accusation ;-), no, this isn't my wording. I _always_ explain that Python's integer bit operations act as if the integers were stored in 2's-complement representation but with an infinite number of sign bits. That's all.

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Mariatta Wijaya added the comment: I verified that the download links for Python 3.7.0a2 (English) are now working. The French and Japanese docs downloads are still 404. -- nosy: +Mariatta ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Nick Coghlan added the comment: I'd prefer to see this change go in the other direction: instead of enforcing eager type checks, we should be unconditionally wrapping the given values in a "list(arg)" call, such that more typical iterable duck-typing behaviour applies.

[issue29710] Incorrect representation caveat on bitwise operation docs

Nick Coghlan added the comment: I like Mark's phrasing as well. For precision, I'd still like to give an exact algorithmic formulation of what "large enough" means in this context, though. Something like: Each bitwise operation has the same result as though carried

[issue32192] Provide importlib.util.lazy_import helper function

Nick Coghlan added the comment: Maintaining the actual implementation as a third party module seems like a good idea to me, so I'm marking this as a documentation issue instead. The idea would be to add this as an example of a very basic lazy importer under

[issue32176] Zero argument super is broken in 3.6 for methods with a hacked __class__ cell

Change by Nick Coghlan : -- pull_requests: +4597 ___ Python tracker ___ ___

[issue32176] Zero argument super is broken in 3.6 for methods with a hacked __class__ cell

Nick Coghlan added the comment: New changeset 078f1814f1a4413a2a0fdb8cf4490ee0fc98ef34 by Nick Coghlan in branch 'master': bpo-32176: Set CO_NOFREE in the code object constructor (GH-4675) https://github.com/python/cpython/commit/078f1814f1a4413a2a0fdb8cf4490ee0fc98ef34

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Nick Coghlan added the comment: While there are some good comments in line in the PR, I think it would be helpful if these changes were accompanied by some additions to https://devguide.python.org/compiler/ that explain how the various pieces of the solution work together

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Raymond Hettinger added the comment: At this point in the release cycle, it would be nice to get this PR applied soon so that there is more time see if there are any minor follow-on issues. -- ___ Python tracker

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Nick Coghlan added the comment: I like this change, and think we should go ahead with it, but just wanted to note that I suspect it may make the "Badly timed signals may lead to __exit__ being skipped even after __enter__ succeeded" problem slightly easier to hit:

[issue25054] Capturing start of line '^'

Matthew Barnett added the comment: findall() and finditer() consist of multiple uses of search(), basically, as do sub() and split(), so we want the same rule to apply to them all. -- ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: > Thank you, but I don't need a lecture from you. Feel free to propose our > solution in the form of pull request instead of acting like a project manager > and telling people what to do. I'm sorry you are offended. My pull request

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Ned Deily added the comment: OK, thanks. I've pushed PR 3940 to master and backported it to 3.6. I'll keep this open until we've seen the next full doc build complete successfully. -- ___ Python tracker

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

Ned Deily added the comment: New changeset 2ad350a713360e89ae6d264924cd28f519b8b22c by Ned Deily (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31589 : Build PDF using xelatex for better UTF8 support. (GH-3940) (#4683)

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Ned Deily added the comment: New changeset 2ad350a713360e89ae6d264924cd28f519b8b22c by Ned Deily (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31589 : Build PDF using xelatex for better UTF8 support. (GH-3940) (#4683)

[issue29710] Incorrect representation caveat on bitwise operation docs

Martin Panter added the comment: FWIW I find Mark’s suggestion pretty good: “Each bitwise operation has the same result as though carried out in two's complement using a bit-width that's large enough to represent the inputs.” --

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Change by Roundup Robot : -- keywords: +patch pull_requests: +4596 stage: -> patch review ___ Python tracker ___

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

Change by Roundup Robot : -- pull_requests: +4595 ___ Python tracker ___

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

Ned Deily added the comment: New changeset 7324b5ce8e7c031a0a3832a6a8d7c639111ae0ff by Ned Deily (Julien Palard) in branch 'master': bpo-31589 : Build PDF using xelatex for better UTF8 support. (#3940)

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Ned Deily added the comment: New changeset 7324b5ce8e7c031a0a3832a6a8d7c639111ae0ff by Ned Deily (Julien Palard) in branch 'master': bpo-31589 : Build PDF using xelatex for better UTF8 support. (#3940)

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Change by Neil Schemenauer : -- pull_requests: +4594 ___ Python tracker ___ ___

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Berker Peksag added the comment: > Filed a bug https://github.com/simplejson/simplejson/issues/198 for > simplejson. I've opened https://github.com/simplejson/simplejson/pull/197 to make CLASSIFIERS a list. I've also opened https://github.com/ianare/exif-py/pull/80

[issue25054] Capturing start of line '^'

Serhiy Storchaka added the comment: Avoiding ZWM after a NWM in re.sub() is explicitly documented (and the documentation is correct in this case). This follows the behavior in the ancient RE implementation. Once it was broken in sre, but then fixed (see

[issue462270] sub-tle difference between pre and sre

Serhiy Storchaka added the comment: For history, this was fixed by 21009b9c6fc40b25fcb30ee60d6108f235733e40. -- nosy: +serhiy.storchaka ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: > Classifiers were always documented as lists (msg214915) and passing a > non-list type was raised a cryptic exception message as already reported in > my first message That doesn't matter. You can't break a bunch of packages in a

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Serhiy Storchaka added the comment: Filed a bug https://github.com/simplejson/simplejson/issues/198 for simplejson. -- ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Serhiy Storchaka added the comment: In simplejson classifiers is a result of filter(). This is a list in Python 2 and an iterator in Python 3. It can be uploaded using Python 2. -- ___ Python tracker

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Julien Palard added the comment: I recommand PR 3940, as it's simple, and as I'm still unable to fix issue32200 with PR 4069 (I still don't understand how to write those latex macros). I'm open to follow the discussion about PR 4069, if one find a nice documentable

[issue32174] nonASCII punctuation characters can not display in python363.chm.

Change by Ned Deily : -- nosy: +mdk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue25054] Capturing start of line '^'

Matthew Barnett added the comment: The pattern: \b|:+ will match a word boundary (zero-width) before colons, so if there's a word followed by colons, finditer will find the boundary and then the colons. You _can_ get a zero-width match (ZWM) joined to the

[issue32174] nonASCII punctuation characters can not display in python363.chm.

R. David Murray added the comment: The doc source files do not contain smart quotes, and as far as I know, sphinx does produce correct utf-8. Recently there was a bug where incorrect smart quotes were leaking out of the internationalization of the docs, so this might

[issue32172] Add length counter for iterables

R. David Murray added the comment: Guido specifically rejected __len__ for iterators when the iteration protocol was designed. This has become a FREQ in recent times (Frequently Rejected Enhancement Request :) The rationale, as I understand it, is that an iterator

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Change by Ned Deily : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Berker Peksag added the comment: (Sorry, I messed up fields in the issue.) -- nosy: +ned.deily priority: normal -> release blocker ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Berker Peksag added the comment: Classifiers were always documented as lists (msg214915) and passing a non-list type was raised a cryptic exception message as already reported in my first message, https://github.com/pypa/setuptools/issues/1163 and

[issue32168] Mutable instance variables don't get new references with args.

R. David Murray added the comment: For the record: https://docs.python.org/3/faq/programming.html#id13 -- nosy: +r.david.murray ___ Python tracker

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: I tried building the top packages from python3wos.appspot.com. Only simplejson-3.13.2.tar.gz fails to build due to this change. However, given that it is the top downloaded module, I think think making a change to Python that

[issue25054] Capturing start of line '^'

Serhiy Storchaka added the comment: The clause "Empty matches are included in the result unless they touch the beginning of another match" was added in 2f3e5483a3324b44fa5dbbb98859dc0ac42b6070 (issue732120) and I suppose it never was correct. So we can ignore it

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Serhiy Storchaka added the comment: New changeset 13badcbc60cdbfae1dba1683fd2fae9d70717143 by Serhiy Storchaka in branch 'master': bpo-32197: Try to fix a compiler error on OS X introduced in bpo-32030. (#4681)

[issue32030] PEP 432: Rewrite Py_Main()

Serhiy Storchaka added the comment: New changeset 13badcbc60cdbfae1dba1683fd2fae9d70717143 by Serhiy Storchaka in branch 'master': bpo-32197: Try to fix a compiler error on OS X introduced in bpo-32030. (#4681)

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Ned Deily added the comment: Thanks, Julien. To be clear, are you recommending applying just PR 3940 or also the unique part of PR 4069? At this point, I am not concerned about the apparent minor difference in appearance; I would just like the downloadable docs to build

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: I don't see a good reason to add this check. I would guess there could be lots of 3rd party packages that are no uninstallable on Python 3.7. E.g. python3 -m pip install exifread ... TypeError: 'classifiers' should be a 'list',

[issue10544] yield expression inside generator expression does nothing

Change by Serhiy Storchaka : -- status: open -> closed ___ Python tracker ___

[issue10544] yield expression inside generator expression does nothing

Serhiy Storchaka added the comment: New changeset 65d1887170fb278c10a836e9e4319cae4707f524 by Serhiy Storchaka in branch '2.7': [2.7] bpo-10544: Deprecate "yield" in comprehensions and generator expressions in Py3k mode. (GH-4579) (#4676)

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Change by Serhiy Storchaka : -- pull_requests: +4592 ___ Python tracker ___ ___

[issue32030] PEP 432: Rewrite Py_Main()

Change by Serhiy Storchaka : -- pull_requests: +4593 ___ Python tracker ___ ___

[issue32107] Improve MAC address calculation and fix test_uuid.py

Barry A. Warsaw added the comment: > Sorry, but I can't understand how 23df2d1304ece169d7e0dfc843dfb8026b413d9f > could break getnode() on Android and how your changes can fix this. The only > effect of this change is that an error in _random_getnode() no longer > silenced.

[issue32107] Improve MAC address calculation and fix test_uuid.py

Serhiy Storchaka added the comment: Sorry, but I can't understand how 23df2d1304ece169d7e0dfc843dfb8026b413d9f could break getnode() on Android and how your changes can fix this. The only effect of this change is that an error in _random_getnode() no longer

[issue32199] uuid.getnode() should return the MAC address on Android

Change by Serhiy Storchaka : -- keywords: +easy nosy: +serhiy.storchaka ___ Python tracker ___

[issue32198] \b reports false-positives in Indic strings involving combining marks

Serhiy Storchaka added the comment: This is a known issue. See also issue1693050, issue12731, issue25743. I hope it will be solved in 3.7 and maybe the solution will be backported to 2.7 and 3.6 (but not to 3.5, 3.5 takes only security fixes). As a workaround I

[issue32030] PEP 432: Rewrite Py_Main()

Change by Serhiy Storchaka : -- pull_requests: +4591 ___ Python tracker ___ ___

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +4590 stage: -> patch review ___ Python tracker ___

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Julien Palard added the comment: It works with xelatex (https://github.com/python/cpython/pull/3940), here's the difference: https://screenshots.firefox.com/wSn4a8WyFMNzXgKm/null https://screenshots.firefox.com/WmUNljwcO8mImchP/null The "bold" one is the xelatex one.

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Sanyam Khurana added the comment: Even a simple use of ternary operator instead of using if-else inside do-while to handle the macro like: #define SET_DECODE_ERROR(NAME, LEN) \ pymain->err = ((LEN) == (size_t)-2) \ ? _Py_INIT_USER_ERR("cannot decode "

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Sanyam Khurana added the comment: I tried to resolve the issue by trying to figure out the syntax for the SET_DECODE_ERROR macro. I tried to call a function from the macro, and eventually do the checking in that function. Second way I tried was to replace

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Julien Palard added the comment: Yes, it's related to: - https://github.com/python/cpython/pull/3940 - https://github.com/python/cpython/pull/4069 Idea is: Unicode characters are not well supported by pdflatex which what's we're using to build our PDF files. There's

[issue25054] Capturing start of line '^'

Serhiy Storchaka added the comment: Good point. Neither old nor new (which matches regex) behaviors conform the documentation: "Empty matches are included in the result unless they touch the beginning of another match." It is easy to exclude empty matches that

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Change by Julien Palard : -- nosy: +jfbu ___ Python tracker ___ ___

[issue3262] re.split doesn't split with zero-width regex

Change by Serhiy Storchaka : -- pull_requests: +4589 ___ Python tracker ___ ___

[issue852532] ^$ won't split on empty line

Change by Serhiy Storchaka : -- pull_requests: +4588 ___ Python tracker ___

[issue25054] Capturing start of line '^'

Change by Serhiy Storchaka : -- pull_requests: +4586 ___ Python tracker ___ ___

[issue1647489] zero-length match confuses re.finditer()

Change by Serhiy Storchaka : -- pull_requests: +4587 ___ Python tracker ___

[issue32203] [ctypes] test_struct_by_value fails on android-24-arm64

New submission from Xavier de Gaye : test_struct_by_value is ok on Android API 24 on the armv7, x86 and x86_64 architectures. == FAIL: test_struct_by_value (ctypes.test.test_win32.Structures)

[issue32202] [ctypes] all long double tests fail on android-24-x86_64

New submission from Xavier de Gaye : These tests are ok on Android API 24 on the armv7, x86 and arm64 architectures. == FAIL: test_longdouble (ctypes.test.test_callbacks.Callbacks)

[issue32174] nonASCII punctuation characters can not display in python363.chm.

Steve Dower added the comment: I'm not sure there will be any good fix for this. We might be able to coerce proper utf-8 output from Sphinx, and if it also adds the encoding tags required by whatever ancient version of Internet Explorer is used then it should be fine

[issue32201] Python uuids may not be persistent across time

Xavier de Gaye added the comment: Hum, I misunderstood the meaning of persistency in this context. It is the uniqueness that is persistent. Sorry for the noise, closing now. -- resolution: -> not a bug stage: -> resolved status: open -> closed

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

Ned Deily added the comment: It looks like the 3.6 and 3.7 full doc build has been failing since 2017-10-15. Seen in /var/log/docsbuild/python37-en.log: [...] [3] [4] [5] [6] [7] (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-1.def )

[issue32201] Python uuids may not be persistent across time

New submission from Xavier de Gaye : UUIDs are unique and persistent across time and space. UUIDs generated using the getnode() function of the uuid module on a plaform where getnode() cannot use the MAC address are based on a random number created for that purpose and are

[issue32030] PEP 432: Rewrite Py_Main()

Ned Deily added the comment: main.c now has compile errors on macOS: ../../source/Modules/main.c:904:20: error: expected expression return SET_DECODE_ERROR("PYTHONEXECUTABLE environment " ^ ../../source/Modules/main.c:46:5: note: expanded from

[issue32200] Download of 3.7.0a2 docs giving a 404 error

New submission from Carol Willing : Currently, the 3.7.0a2 doc links are giving 404 errors. 3.6 docs are working just fine. https://docs.python.org/3.7/archives/python-3.7.0a2-docs-pdf-letter.tar.bz2 results in a 404. I wasn't sure if I should report here or in python.org

[issue32199] uuid.getnode() should return the MAC address on Android

New submission from Xavier de Gaye : Currently uuid.getnode() returns a random 48-bit number and so the UUIDs are not persistent across time. The reason is that on Android the 'ip link list' command fails. uuid._ip_getnode() should invoke the 'ip link' command instead.

[issue32107] Improve MAC address calculation and fix test_uuid.py

Xavier de Gaye added the comment: > I don't know how the proposed change can help. It helps by fixing the regression introduced by a change made in 23df2d1304ece169d7e0dfc843dfb8026b413d9f in this issue, a change that has been made only in the master branch. Before that

[issue32198] \b reports false-positives in Indic strings involving combining marks

New submission from Shriramana Sharma : Code: import re cons_taml = "[கஙசஞடணதநபமயரலவழளறன]" print(re.findall("\\b" + cons_taml + "ை|ஐ", "ஐவர் பையன் இசை சிவிகை இல்லை இவ்ஐ")) cons_deva = "[कखगघङचछजझञटठडढणतथदधनपफबभमयरलवशषसह]" print(re.findall("\\b" + cons_deva + "ै|ऐ", "ऐषमः

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Sanyam Khurana added the comment: I used git bisect to track down the commit that broke the build. Seems like this is the SHA: ebac19dad6263141d5db0a2c923efe049dba99d2 ebac19dad6263141d5db0a2c923efe049dba99d2 is the first bad commit commit

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Change by Serhiy Storchaka : -- nosy: +vstinner type: crash -> compile error ___ Python tracker ___

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

New submission from Sanyam Khurana : The current master branch at commit af5a895073c24637c094772b27526b94a12ec897 fails while building the interpreter. The following is the traceback while running `make` after `./configure --with-pydebug` gcc -c -Wno-unused-result

[issue32107] Improve MAC address calculation and fix test_uuid.py

Serhiy Storchaka added the comment: I don't know how the proposed change can help. PR 4677 makes the test more lenient. -- stage: patch review -> needs patch ___ Python tracker

[issue32107] Improve MAC address calculation and fix test_uuid.py

Change by Serhiy Storchaka : -- pull_requests: +4585 stage: needs patch -> patch review ___ Python tracker ___

[issue10544] yield expression inside generator expression does nothing

Serhiy Storchaka added the comment: PR 4676 backports warnings to 2.7 in Py3k mode. -- status: closed -> open ___ Python tracker

[issue10544] yield expression inside generator expression does nothing

Change by Serhiy Storchaka : -- pull_requests: +4584 ___ Python tracker ___ ___

[issue32176] Zero argument super is broken in 3.6 for methods with a hacked __class__ cell

Change by Nick Coghlan : -- keywords: +patch pull_requests: +4583 stage: -> patch review ___ Python tracker ___

[issue25910] Fixing links in documentation

Change by Sanyam Khurana : -- pull_requests: +4582 stage: -> patch review ___ Python tracker ___

[issue32107] Improve MAC address calculation and fix test_uuid.py

Xavier de Gaye added the comment: test_uuid fails now on android-24-armv7 on the master branch: == FAIL: test_getnode (test.test_uuid.TestUUIDWithoutExtModule)

[issue25054] Capturing start of line '^'

Martin Panter added the comment: The new “finditer” behaviour seems to contradict the documentation about excluding empty matches if they touch the start of another match. >>> list(re.finditer(r"\b|:+", "a::bc")) [, , , , ] An empty match at (1, 1) is included, despite

[issue29151] test_asyncore.TestAPI_UseIPv4Select / test_asyncore.TestAPI_UseIPv6Select fails test_handle_close_after_conn_broken

patrila added the comment: Adding a 'time.sleep(0.01)' before the 'send()' statement in test.test_asyncore.BaseTestAPI.test_handle_close_after_conn_broken.TestClient.handle_write works around this problem. Unsure if this a fix or just a workaround. Patch attached.

[issue32030] PEP 432: Rewrite Py_Main()

STINNER Victor added the comment: New changeset af5a895073c24637c094772b27526b94a12ec897 by Victor Stinner in branch 'master': bpo-32030: _PyPathConfig_Init() sets home and program_name (#4673)

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

Change by Allen Li : -- nosy: +Allen Li ___ Python tracker ___ ___ Python-bugs-list