[issue29515] socket module missing IPPROTO_IPV6, IPPROTO_IPV4 on Windows
Change by Jan Gosmann <jan+pythontrac...@hyper-world.de>: -- nosy: +jgosmann ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue29515> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29949] sizeof set after set_merge() is doubled from 3.5
Changes by Jan Gosmann <jan+pythontrac...@hyper-world.de>: -- nosy: +jgosmann ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29949> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24875] pyvenv doesn´t install PIP inside a new venv with --system-site-package
Changes by Jan Gosmann <jan+pythontrac...@hyper-world.de>: -- nosy: +jgosmann ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24875> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21318] sdist fails with symbolic links do non-existing files
New submission from Jan Gosmann: If there is a symbolic link to a non-existing file anywhere in the source tree python setup.py sdist fails with an output like the following: running sdist running check warning: check: missing required meta-data: url error: abc: No such file or directory Pruning the problematic path with a MANIFEST.in file does not help. I could locate the culprit in filelist.py http://hg.python.org/cpython/file/c82dcad83438/Lib/distutils/filelist.py in line 267: stat = os.stat(fullname) fails for symlinks to non-existing files. Maybe os.lstat should be used? Or it should be checked before os.stat if it is a symlink to a nonexisting file? In case you wonder why I have links to non-existing files in my source tree: Those can be left behind by automated tests I'm using and are not supposed to be part of the source (or any other) distribution. But as I said, the error is not prevented by excluding them with a MANIFEST.in file. My current workaround is to delete all the leftovers from the test as first thing in setup.py. -- components: Distutils messages: 216930 nosy: dstufft, eric.araujo, jgosmann priority: normal severity: normal status: open title: sdist fails with symbolic links do non-existing files type: behavior versions: Python 2.7, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21318 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17396] modulefinder fails if module contains syntax error
Jan Gosmann added the comment: Here is an updated patch, also containing a test. -- Added file: http://bugs.python.org/file30237/fix-handling-of-syntax-errors.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17396] modulefinder fails if module contains syntax error
Jan Gosmann added the comment: It's based on the default branch becoming 3.4. -- versions: +Python 3.4 -Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17396] modulefinder fails if module contains syntax error
Jan Gosmann added the comment: Could you point me to some documentation on how to add a test? I have not been involved in Python development so far. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17396] modulefinder fails if module contains syntax error
New submission from Jan Gosmann: Running modulefinder.ModuleFinder.run_script on a script which has an import statement with a module containing a syntax error will raise a SyntaxError exception. I think, modulefinder should instead continue its analysis and add the module to badmodules. Especially, as there are valid reasons for importing modules with syntax errors like in the following code snippet if not python3: from .exec_py2 import exec_ else: from .exec_py3 import exec_ I attached a patch which changes the code to catch potential SyntaxError exceptions and change them to an ImportError. -- components: Library (Lib) files: fix-handling-of-syntax-errors.diff keywords: patch messages: 183953 nosy: jgosmann priority: normal severity: normal status: open title: modulefinder fails if module contains syntax error versions: Python 2.7 Added file: http://bugs.python.org/file29376/fix-handling-of-syntax-errors.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com