[issue4928] tempfile.NamedTemporaryFile: automatic cleanup by OS
Hugo added the comment: It would seem that the main issue here lies in the documentation not being obvious enough for some of us. If you're familiar with lower level OS APIs, it might be clear, but as an app developer, some things slip by. The key difference is that TemporaryFile will be erased properly (at least on Linux) even if the process gets a SIGKILL, while NamedTemporaryFile will linger (which fills up my disk every few weeks/months). As an application developer, this difference is super important to me (I hope I'm not the only one). Would a PR that mentions this explicitly in the docs be an acceptable solution here? -- nosy: +WhyNotHugo ___ Python tracker <https://bugs.python.org/issue4928> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46285] http/server.py wont respect its protocol_version
New submission from Hugo Almeida : Hi, Sorry for my poor English, this is not a spam issue. How to reproduce File about `http/server.py`, line 1235 at main branch. 1st, change `protocol_version`, e.g. from "HTTP/1.0" to "HTTP/1.1": --- protocol="HTTP/1.0", port=8000, ... +++ protocol="HTTP/1.1", port=8000, ... 2ed, run with `python -m http.server` and test by: `curl http://127.0.0.1:8000 2>/dev/null| head -n 1` Result == The response head line will always been a fixed HTTP Version refer to `BaseHTTPRequestHandler.protocol_version` defined, thus "HTTP/1.0 200 OK" currently. Expected It should equal to `http.server.test(protocol="...")` which specified like above, for this issue, it is expected to be "HTTP/1.1 200 OK". P.S. I know it is just locate in a test code area (http.servers::test), but what I submit here is about a Python Variable Scope issue maybe. -- components: Library (Lib) messages: 409894 nosy: openalmeida priority: normal severity: normal status: open title: http/server.py wont respect its protocol_version type: enhancement versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46285] http/server.py wont respect its protocol_version
Hugo Almeida added the comment: update == It seems I've found the problem, http/server.py#L1277-L1288: ``` handler_class = partial(SimpleHTTPRequestHandler, directory=args.directory) ``` Because of `partial` (provide by the functools module), there comes a closure like stuff ? -- resolution: -> remind ___ Python tracker <https://bugs.python.org/issue46285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46285] http/server.py wont respect its protocol_version
Hugo Almeida added the comment: The short story is, everything is okay, its my bad to taken the test function out of context, sorry about that of issue report. # just for details review (related file attached): # # check line 1277 to line 1278 (main branch of Python currently): # https://github.com/python/cpython/blob/17b16e1/Lib/http/server.py#L1277-L1278 # # thus, `functools.partial` (closure/wrapper) will # make the parameter `protocol` of the function `test` useless. # So, specify a handler class directly. -- resolution: remind -> not a bug stage: -> resolved status: open -> closed Added file: https://bugs.python.org/file50551/my_http.py ___ Python tracker <https://bugs.python.org/issue46285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46285] http/server.py wont respect its protocol_version
Hugo Almeida added the comment: Hi, buddy, there is no problem if invoke the http.server.test function as its designed, I mean the function iteself is okay, thus http/server.py invoked it via the functools.partial wrapper (handler_class) only will case this issue, which technically ignored its protocol parameter's specify. User of http/server.py::test should specify a handler class directly. If this is a bug, maybe it is about the usage/desire of `functools.partial` ... I am not sure, closure model programming (the lambda etc.) is not eary for me and I closed this issue by courtesy yesterday, if reopen this issue will help/valueable a bit, please tell me. Improve my English seems too nessary, thank you so much for your warm hearted. -- ___ Python tracker <https://bugs.python.org/issue46285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46285] protocol_version in http.server.test can be ignored
Hugo Almeida added the comment: Hi Éric, thank you so much. I know only a little usage of closure and functools.partial but not the historical/relative knowledge of their design/feature, I mean this issue have 2 visual, the partical object not working as it expected or we are not calling the partical as it expected: 1) partial is not working as its feature or design said, assume I guessed right, thus partial object behaviors should be totally equal to its wrapper/inside class called with properties applied in a standalone/outside way which we usually used, the use of partical at http.server.test should be okey. """ import functools class Obj: pass obj = Obj(); obj.foo = bar # usually used jbo = functools.partial(Obj, foo=bar) # if jbo totally equal to obj in anywhere # (the so called Duck Type or # maybe the LSP rule, Liskov # Substitution Principle) # the use of partical in http.server # should also be ok # # I used the partical times the same # as http.server's author did # and I told myself I know its usage # but now I do not think so """ 2) solve this issue itself, to pass handler class directly to ignore partial object caused problem, this is a coding logic shelter/fixing because the way we used functools.partical is not as it expected. This is what cpython@github PR30701 already done. (so the use of partical in http.server is not ok, not welcome at least, so based what I said above, the feature/design of partical now confused me, unless its a bug of partical itself which I am not sure.) -- ___ Python tracker <https://bugs.python.org/issue46285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13395] Python ISO-8859-1 encoding problem
New submission from Hugo Silva :
Hi all,
I'm facing a huge encoding problem in Python when dealing with ISO-8859-1 /
Latin-1 character set.
When using os.listdir to get the contents of a folder I'm getting the strings
encoded in ISO-8859-1 (ex: ''Ol\xe1 Mundo''), however in the Python interpreter
the same string is encoded to a different charset:
In : 'Olá Mundo'.decode('latin-1')
Out: u'Ol\xa0 Mundo'
How can I force Python to decode the string to the same format. I've seen that
os.listdir is returning the strings correctly encoded but the interpreter is
not ('á' character corresponds to '\xe1' in ISO-8859-1, not to '\xa0'):
http://en.wikipedia.org/wiki/ISO/IEC_8859-1
This is happening
Any thoughts on how to overcome ?
Regards,
--
components: Unicode
messages: 147552
nosy: Hugo.Silva, ezio.melotti
priority: normal
severity: normal
status: open
title: Python ISO-8859-1 encoding problem
versions: Python 2.7
___
Python tracker
<http://bugs.python.org/issue13395>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7506] multiprocessing.managers.BaseManager.__reduce__ references BaseManager.from_address
Hugo Shi added the comment: Does BaseManager need to be pickleable? It looks like it contains an AuthenticationKey which should NOT be pickled for security reasons. All the unit tests pass if we remove the __reduce__ method. Is that the fix? -- nosy: +Hugo.Shi ___ Python tracker <http://bugs.python.org/issue7506> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7506] multiprocessing.managers.BaseManager.__reduce__ references BaseManager.from_address
Hugo Shi added the comment: I didn't run the unittests in windows, But I don't have the capability to do so at the moment. I maybe able to do this on monday I don't know why AuthenticationKey has security issues with being pickled, however in process.py # # We subclass bytes to avoid accidental transmission of auth keys over network # class AuthenticationString(bytes): def __reduce__(self): from .forking import Popen if not Popen.thread_is_spawning(): raise TypeError( 'Pickling an AuthenticationString object is ' 'disallowed for security reasons' ) return AuthenticationString, (bytes(self),) -- ___ Python tracker <http://bugs.python.org/issue7506> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38640] while False: break => SyntaxError: 'break' outside loop
New submission from Hugo Dupras : In python 3.8 the following code raises an exception, which was not the case with previous python. ``` while False: ... break ``` It raises the following exception: SyntaxError: 'break' outside loop. This `while False` loop was used to temporary disable a while loop in our code base. Workaround to fix this: ``` enable=False while enable: ... break ``` (or use the walrus operator) -- components: Interpreter Core messages: 355700 nosy: jabesq priority: normal severity: normal status: open title: while False: break => SyntaxError: 'break' outside loop type: behavior versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue38640> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24955] webbrowser broken on Mac OS X when using the BROWSER variable
Change by Hugo Delgado : -- pull_requests: +26228 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/27751 ___ Python tracker <https://bugs.python.org/issue24955> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24955] webbrowser broken on Mac OS X when using the BROWSER variable
Hugo Delgado added the comment: Yes, I've created a PR for it. https://github.com/python/cpython/pull/27751 Happy to adapt it as needed. Thanks -- ___ Python tracker <https://bugs.python.org/issue24955> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39443] Inhomogeneous behaviour for descriptors in between the class-instance and metaclass-class pairs
New submission from Hugo Ricateau :
Assume one has defined the following descriptor:
```
class Descriptor:
def __set__(self, instance, value):
print('SET')
```
On the one hand, for the class-instance pair, the behaviour is as follows:
```
class FirstClass:
descriptor = Descriptor()
def __init__(self):
self.descriptor = None
FirstClass().descriptor = None
```
results in "SET" being displayed twice; i.e. both assignations triggered the
__set__ method of the descriptor.
On the other hand, for the metaclass-class pair, the behaviour is the following:
```
class SecondClassMeta(type):
descriptor = Descriptor()
class SecondClass(metaclass=SecondClassMeta):
descriptor = None
SecondClass.descriptor = None
```
results in "SET" being displayed only once: the first assignation (the one in
the class definition) did not triggered __set__.
It looks to me like an undesirable asymmetry between the descriptors behaviour
when in classes vs when in metaclasses. Is that intended? If it is, I think it
should be highlighted in the descriptors documentation.
Best
--
components: Interpreter Core
messages: 360623
nosy: Hugo Ricateau
priority: normal
severity: normal
status: open
title: Inhomogeneous behaviour for descriptors in between the class-instance
and metaclass-class pairs
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue39443>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39443] Inhomogeneous behaviour for descriptors in between the class-instance and metaclass-class pairs
Hugo Ricateau added the comment: Thanks for this detailed answer; very instructive :) > the descriptor protocol is only triggered by "dotted access" Indeed; this is what I was missing... despite it is indirectly mentioned in the documentation. Nonetheless, it could be worth the overload to explicitly add in the language reference that 'the descriptor protocol is only triggered by "dotted access"' (looks like it is not the case for now). >+ a list enumerating places where descriptors are *not* invoked > [...] > Which of those do you think would have helped you the most? Could be really helpful as well, by clearly exhibiting the limitations of the descriptors; I think the best location for this could be the 'descriptors howto' page despite the other option is perfectly suitable as well. Best, Hugo -- ___ Python tracker <https://bugs.python.org/issue39443> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40461] execution of file with pictures doesn't work in command --onefile in pyinstaller
New submission from Hugo Benavides : hi, I have a problem to crete an executable using the command pyinstaller at the time of use the helper --onefile I've created an executable using the next instruction: pyinstaller --windowed --add-data "Rute PC to my Folder\Imagen";"Imagen" Aplicacion_Calculadora.py The folder Imagen has an imagen that is called into the code and at this time everything work fine, the executable starts and works very fine. I have used the calculator and operations are correct and the imagen is upload in the interface, but I deleted everything and started again. I would like to add everything in one File using the command: pyinstaller --onefile --add-data "Rute PC to mi Folder\Imagen";"Imagen" Aplicacion_Calculadora.py At this point, the executable never starts. If I saw the message in console when the .exe is running and it shows me the next error: File "tkinter\__init__.py", line 4061, in __init__ File "tkinter\__init__.py", line 4006, in __init__ _tkinter.TclError: couldn't open "./Imagen/Retroceder.png": no such file or directory [11320] Failed to execute script Aplicacion_Calculadora The executable never can find the folder and the imagen, it happenning just when I use the command --onefile I've been looking in every documentation and instructions but I've not found anything about that error just using the command --onefile May you help me with that error or what instruction I should add, please? Attach code and folder with the imagen Thanks -- components: Library (Lib) files: Aplicacion_Calculadora.zip messages: 367811 nosy: Hugo Benavides priority: normal severity: normal status: open title: execution of file with pictures doesn't work in command --onefile in pyinstaller versions: Python 3.8 Added file: https://bugs.python.org/file49103/Aplicacion_Calculadora.zip ___ Python tracker <https://bugs.python.org/issue40461> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43402] IDLE shell adds newline after print even when `end=''` is specificied
New submission from Hugo Nobrega :
When evaluting a call to the `print` function with argument `end=''` in the
IDLE shell, a newline is unexpectedly added at the end, before the next shell
prompt.
The expected behavior is to have the shell prompt next to the last printed
line. The expected behavior is seen when evaluting the same expression in an
interactive python shell from a terminal (`python -i`)
Example:
IDLE shell (not expected):
>>> print('a',end='')
a
>>>
Interactive python shell (expected):
>>> print('a',end='')
a>>>
I could not find any settings in IDLE that might be governing this behavior,
not any other issues mentioning this same thing.
Tested on Python 3.9.1 on Manjaro Linux.
--
assignee: terry.reedy
components: IDLE
messages: 388115
nosy: hugonobrega, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE shell adds newline after print even when `end=''` is specificied
type: behavior
versions: Python 3.9
___
Python tracker
<https://bugs.python.org/issue43402>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43402] IDLE shell adds newline after print even when `end=''` is specificied
Hugo Nobrega added the comment: I see, thank you. But, in that case, shouldn't the interactive `python -i` shell have the same (now seen as desired) behavior as the IDLE shell? -- ___ Python tracker <https://bugs.python.org/issue43402> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43418] FTPLib module crashes when server returns byte message instead of string
New submission from Hugo Chia : https://github.com/cowrie/cowrie/issues/1394 https://github.com/cowrie/cowrie/pull/1396 Above are some of the links mentioning the issue with the FTPLib module. It happens when the FTP server returns a byte message instead of a string. Ftplib expects a string and does not account for receiving a byte message -- components: Library (Lib) messages: 388198 nosy: hugochiaxyz8 priority: normal severity: normal status: open title: FTPLib module crashes when server returns byte message instead of string type: crash versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue43418> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24955] webbrowser broken on Mac OS X when using the BROWSER variable
Hugo Delgado added the comment: I've bumped into this and won't mind working on it, is it ok for me to try to finish it? -- nosy: +Hugo Delgado ___ Python tracker <https://bugs.python.org/issue24955> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11549] Build-out an AST optimizer, moving some functionality out of the peephole optimizer
Hugo Geoffroy added the comment: I would like to point out that the changes in `ast.literal_eval` may have some security risk for code that do not expect this function to return an object with user-controlled length (for example, with `2**32*'X'`). AFAIK, this is not possible with the current version of `literal_eval`. At least [this library](https://pypi.python.org/pypi/serpent) would have a serious risk of remote DoS : > Because it only serializes literals and recreates the objects using > ast.literal_eval(), the serialized data is safe to transport to other > machines (over the network for instance) and de-serialize it there. Sorry for the noise if this is a useless/incorrect consideration. -- nosy: +pstch ___ Python tracker <http://bugs.python.org/issue11549> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29526] Documenting format() function
New submission from Hugo Prod'homme: Hello python contributors, this is my first time on python.org and I am coming with a suggestion. The idea is to help people that have to format strings containing numbers of various kinds, I am from the scientific domain but this should help everybody anyway. In the past the strftime was the best way to format numbers in strings (truncating to some digits after point, setting to exponent notation, etc...). To remind the "strf language" one had to use the internet or a document such as this page : http://strftime.org/";>http://strftime.org/ Some idea was provided to add this indications in the python docs. http://bugs.python.org/issue9650";>http://bugs.python.org/issue9650 Now the format() function has appeared in the python __builtins__ and this is even more adequate to add help about the string formatting, because we can write the "Format Specification Mini-Language" directly inside the docstring of the format.__doc__ . See the paragraph named "7.1.3.1. Format Specification Mini-Language" in the following page : https://docs.python.org/2/library/string.html";>https://docs.python.org/2/library/string.html I emphasize, the interest of this is to allow the user to be reminded of the formatting options without opening another document than his(her) script, to avoid breaking the workflow. I am providing what I think is the minimal material that the docstring should contains within the attached file. I am not really familiar with docstring formatting according to PEP (436?) and someone should help getting this in the right way of writing. Furthermore, a specific syntax is needed within the string in addition to the format() arguments, this should be described. And the reminder about the mini-language should appear clearly as a reminder. These are two supplemental difficulties in comparison with an usual docstring. To anyone thinking something else should be added to the docstring; please add or say it. PS: I think I can start from the matplotlib.pyplot.plot.__doc__ as a template to complete the format.__doc__ but I have some work aside for now. -- files: format_docstring_v0.1.txt messages: 287539 nosy: hugo.prodho...@gmx.fr priority: normal severity: normal status: open title: Documenting format() function type: enhancement versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file46625/format_docstring_v0.1.txt ___ Python tracker <http://bugs.python.org/issue29526> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29526] Documenting format() function
Hugo Prod'homme added the comment:
+1 :
Adding the reference to help('FORMATTING') will indeed solve all the problems I
was thinking about at first.
--
I realized I was thinking only about a small part of the problem thanks to your
answers. I wasn't even thinking about the dates and other types... So I agree
applying my first idea will be a big mess.
(... and yes I was referring to printf formatting)
--
___
Python tracker
<http://bugs.python.org/issue29526>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call
Hugo Geoffroy added the comment: This patch blacklists `__wrapped__` (using the same form as the first comment, with a more explicit exception message) in `unittest.mock._Call.__getattr__`. I also documented the change and added a tests that checks `assertFalse(hasattr(call, '__wrapped__'))`. I did not make the same change in the `Mock` class, as its instances are not usually set at module level (which is what triggers this bug in doctests, as they run `inspect.unwrap` on module attributes). I'd like to note that this regression can be nasty for some CI systems : it makes the Python interpreter infinitely allocate memory (as it's not a recursion error) and crashes any host that doesn't limit virtual memory allocation. -- keywords: +patch nosy: +pstch Added file: http://bugs.python.org/file44178/blacklist-wrapped-in-mock-call.patch ___ Python tracker <http://bugs.python.org/issue25532> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call
Hugo Geoffroy added the comment: You are right, the fix would be better suited in `unwrap`. But, still, shouldn't any `__getattr__` implementation take care of not returning, for the `__wrapped__` attribute, a dynamic wrapper that provides the same attribute ? `__wrapped__` is commonly resolved to the innermost value without `__wrapped__`, which in this case never happens. This would also avoid problems with introspection tools that resolve `__wrapped__` without the help of `unwrap` (before Python 3.4 IIRC). -- ___ Python tracker <http://bugs.python.org/issue25532> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call
Hugo Geoffroy added the comment: Another argument for having the fix in `unwrap` rather than `signature` is that this bug does not actually seem to be called by `signature`, as the doctest module calls `unwrap` for "inspect.isroutine(inspect.unwrap(val))". Also, this call does not even check for `ValueError`, which, if I'm not wrong, is something that should be corrected. Maybe `unwrap` could be made recursive to make it respect recursion limits directly ? Otherwise, limiting the loop seems like a good idea. (Temporarily, `from mock import call; call.__wrapped__ = None` seems to be a good workaround to prevent infinite memory allocation). -- ___ Python tracker <http://bugs.python.org/issue25532> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8489] Support UTF8SMTP as part of RFC 5336 in smptlib
Hugo Hallman added the comment: Can not reproduce the problem in 2.7 Attaching a patch with test cases proving that the problem is solved. Patch based on current tip 2.7. -- keywords: +patch nosy: +hhallman Added file: http://bugs.python.org/file29181/issue8489.patch ___ Python tracker <http://bugs.python.org/issue8489> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
New submission from Hugo van Kemenade :
The behaviour of os.path.normpath appears to have changed between Python
3.10/Python 3.11.0a2 and 3.11.0a3+.
I don't see anything mentioned in
https://docs.python.org/3.11/whatsnew/3.11.html
Is this intentional?
Old behaviour:
Python 3.10.1 (v3.10.1:2cd268a3a9, Dec 6 2021, 14:28:59) [Clang 13.0.0
(clang-1300.0.29.3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from os.path import normpath
>>> normpath('handbook/../../Tests/image.png')
'../Tests/image.png'
>>>
Python 3.11.0a2 (main, Dec 30 2021, 21:22:15) [Clang 13.0.0
(clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from os.path import normpath
>>> normpath('handbook/../../Tests/image.png')
'../Tests/image.png'
>>>
New behaviour:
Python 3.11.0a3+ (heads/main:af6b406, Dec 9 2021, 15:34:48) [Clang 13.0.0
(clang-1300.0.29.3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from os.path import normpath
>>> normpath('handbook/../../Tests/image.png')
'Tests/image.png'
>>>
Python 3.11.0a3+ (heads/main:8d7644f, Dec 30 2021, 21:32:51) [Clang 13.0.0
(clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from os.path import normpath
>>> normpath('handbook/../../Tests/image.png')
'Tests/image.png'
>>>
(Found in https://github.com/sphinx-doc/sphinx/issues/10030.)
--
components: Library (Lib)
messages: 409384
nosy: hugovk
priority: normal
severity: normal
status: open
title: os.path.normpath change between 3.11.0a2 and 3.11.0a3+
versions: Python 3.11
___
Python tracker
<https://bugs.python.org/issue46208>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Hugo van Kemenade added the comment: git bisect between v3.11.0a2 and v3.11.0a3 points to the same commit, 99fcf1505218464c489d419d4500f126b6d6dc28. -- ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46178] Remove `.travis.yml`?
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 2.0 -> 3.0 pull_requests: +28522 pull_request: https://github.com/python/cpython/pull/30309 ___ Python tracker <https://bugs.python.org/issue46178> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33937] test_socket: SendmsgSCTPStreamTest.testSendmsgTimeout() failed on Travis CI with: [Errno 12] Cannot allocate memory
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 2.0 -> 3.0 pull_requests: +28523 pull_request: https://github.com/python/cpython/pull/30309 ___ Python tracker <https://bugs.python.org/issue33937> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Hugo van Kemenade added the comment: Here's a branch with a passing ntpath.normpath test and a failing posixpath.normpath test: https://github.com/hugovk/cpython/tree/issue-46208-tests https://github.com/hugovk/cpython/commit/d7e8da179adce51a8f63d2dbd062a272dda826bc -- ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23952] cgi: Document the 'maxlen' member of the cgi module
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +28550 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30338 ___ Python tracker <https://bugs.python.org/issue23952> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4849] instantiating and populating xml.dom.minidom.Element is cumbersome
Hugo van Kemenade added the comment: Hi Mike, "patch review" means: "A patch or pull request exists, but it needs review. Any triager or core developer may do the review." https://devguide.python.org/triaging/#stage So we were waiting for someone to review patches listed above under the "Files" section (eg. issue4849_2.patch). But seeing as they're from 2012/2014, and development has now moved to GitHub, a pull request needs to be opened on GitHub instead. So I reckon you're good to go ahead and create a PR. -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue4849> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20281] [doc] time.strftime %z format specifier is the same as %Z
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 6.0 -> 7.0 pull_requests: +28567 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30354 ___ Python tracker <https://bugs.python.org/issue20281> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29964] [doc] %z directive has no effect on the output of time.strptime
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 6.0 -> 7.0 pull_requests: +28568 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/30354 ___ Python tracker <https://bugs.python.org/issue29964> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33252] [doc] Clarify ResourceWarning documentation
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +28572 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30358 ___ Python tracker <https://bugs.python.org/issue33252> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23183] timeit CLI best of 3: undocumented output format
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 5.0 -> 6.0 pull_requests: +28573 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30359 ___ Python tracker <https://bugs.python.org/issue23183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28546] [doc] Clarify setting pdb breakpoints
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +28574 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30360 ___ Python tracker <https://bugs.python.org/issue28546> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34538] Remove encouragement to author a base class for all Exception subclasses in a module
Change by Hugo van Kemenade : -- keywords: +patch nosy: +hugovk nosy_count: 9.0 -> 10.0 pull_requests: +28575 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30361 ___ Python tracker <https://bugs.python.org/issue34538> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Hugo van Kemenade added the comment: Searching 4,764 sdists from the top 5,000 PyPI packages, these 13 contain "LegacyInterpolation": configparser-5.1.0.tar.gz configparser2-4.0.0.tar.gz eth_abi-2.1.1.tar.gz eth-account-0.5.6.tar.gz eth-hash-0.3.2.tar.gz eth-utils-1.10.0.tar.gz hexbytes-0.2.2.tar.gz jedi-0.18.1.tar.gz magicinvoke-2.4.5.tar.gz mypy-0.910.tar.gz pytype-2021.11.12.tar.gz web.py-0.62.tar.gz webcolors-1.11.1.tar.gz The first two are stdlib backports: configparser is active and configparser2 was last updated in 2015: configparser-5.1.0/src/backports/configparser/__init__.py: "LegacyInterpolation", configparser-5.1.0/src/backports/configparser/__init__.py:class LegacyInterpolation(Interpolation): configparser-5.1.0/src/configparser.py:"LegacyInterpolation", configparser-5.1.0/src/configparser.py:LegacyInterpolation, configparser-5.1.0/src/test_configparser.py:elif isinstance(self.interpolation, configparser.LegacyInterpolation): configparser-5.1.0/src/test_configparser.py:elif isinstance(self.interpolation, configparser.LegacyInterpolation): configparser-5.1.0/src/test_configparser.py:elif isinstance(self.interpolation, configparser.LegacyInterpolation): configparser-5.1.0/src/test_configparser.py:interpolation = configparser.LegacyInterpolation() configparser-5.1.0/src/test_configparser.py:class ConfigParserTestCaseLegacyInterpolation(ConfigParserTestCase, unittest.TestCase): configparser2-4.0.0/src/backports/configparser2/__init__.py:class LegacyInterpolation(Interpolation): configparser2-4.0.0/src/configparser2.py:LegacyInterpolation, The others are all configparser.pyi typeshed stub files: eth_abi-2.1.1/venv/lib/python3.6/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth_abi-2.1.1/venv/lib64/python3.6/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv-py3.8/lib/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv-py3.8/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv-py3.8/lib64/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv-py3.8/lib64/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv/lib/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv/lib64/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-account-0.5.6/venv/lib64/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv-py3.8/lib/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv-py3.8/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv-py3.8/lib64/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv-py3.8/lib64/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv/lib/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv/lib64/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-hash-0.3.2/venv/lib64/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-utils-1.10.0/venv-py3.8/lib/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-utils-1.10.0/venv-py3.8/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-utils-1.10.0/venv-py3.8/lib64/python3.8/site-packages/jedi/third_party/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-utils-1.10.0/venv-py3.8/lib64/python3.8/site-packages/mypy/typeshed/stdlib/3/configparser.pyi:class LegacyInterpolation(Interpolation): ... eth-utils-1.10.0/venv/lib/python3.8/site-packages/jedi
[issue45173] Remove configparser deprecations
Change by Hugo van Kemenade : -- pull_requests: +29106 pull_request: https://github.com/python/cpython/pull/30927 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Change by Hugo van Kemenade : -- pull_requests: +29131 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30952 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46607] Add DeprecationWarning to configparser's LegacyInterpolation
New submission from Hugo van Kemenade : The LegacyInterpolation class of configparser has been deprecated in docs since 3.2, but without raising a DeprecationWarning. The 3.2 HISTORY file says: > - configparser: the SafeConfigParser class has been renamed to ConfigParser. > The legacy ConfigParser class has been removed but its interpolation > mechanism is still available as LegacyInterpolation. Searching the top 5,000 PyPI sdists, there's very little (if any "real") use of LegacyInterpolation. Details: https://bugs.python.org/issue45173#msg409685 Other configparser deprecations were added in 3.2, but with DeprecationWarnings. Let's add a DeprecationWarning for a couple of releases before removal. -- components: Library (Lib) messages: 412339 nosy: hugovk priority: normal severity: normal status: open title: Add DeprecationWarning to configparser's LegacyInterpolation versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46607> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46607] Add DeprecationWarning to configparser's LegacyInterpolation
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +29258 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30927 ___ Python tracker <https://bugs.python.org/issue46607> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Change by Hugo van Kemenade : -- pull_requests: -29106 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Hugo van Kemenade added the comment: Sure, please see https://bugs.python.org/issue46607. I've rebased GH-30927 to use the new issue number. -- ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Change by Hugo van Kemenade : -- pull_requests: +29268 pull_request: https://github.com/python/cpython/pull/31084 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46607] Add DeprecationWarning to configparser's LegacyInterpolation
Hugo van Kemenade added the comment: > > Other configparser deprecations were added in 3.2, but with > > DeprecationWarnings. > Its deprecation was never documented anywhere in Doc/. Correct, only in the docstring: ``` class LegacyInterpolation(Interpolation): """Deprecated interpolation used in old versions of ConfigParser. Use BasicInterpolation or ExtendedInterpolation instead.""" ``` I've updated GH-30927 to say "deprecated in the docstring" instead of "deprecated in docs". -- ___ Python tracker <https://bugs.python.org/issue46607> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47022] PEP 594: Document removal of asynchat, asyncore and smtpd
New submission from Hugo van Kemenade : PEP 594 – Removing dead batteries from the standard library As mentioned in the SC acceptance: > One thing we’d like to see happen while implementing it: Document the status > of the modules being deprecated and removed and backport those deprecation > updates to older CPython branch documentation (at least back to 3.9). That > gets the notices in front of more people who may use the docs for their > specific Python version. So let's update documentation and deprecation warnings to make clear in which release they're to be removed. This first one is just for the three modules (asynchat, asyncore and smtpd) slated for removal soonest, in 3.12: https://peps.python.org/pep-0594/#deprecated-modules -- components: Library (Lib) messages: 415222 nosy: hugovk priority: normal severity: normal status: open title: PEP 594: Document removal of asynchat, asyncore and smtpd versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue47022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47022] PEP 594: Document removal of asynchat, asyncore and smtpd
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +29989 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31891 ___ Python tracker <https://bugs.python.org/issue47022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43721] Documentation of property.{getter, setter, deleter} fails to mention that a *new* property is returned
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +29991 pull_request: https://github.com/python/cpython/pull/31893 ___ Python tracker <https://bugs.python.org/issue43721> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40465] Deprecate the optional *random* argument to random.shuffle()
Hugo van Kemenade added the comment: GH-31818 adds an entry to What's New in 3.11. -- message_count: 5.0 -> 6.0 nosy: +hugovk nosy_count: 3.0 -> 4.0 pull_requests: +30050 pull_request: https://github.com/python/cpython/pull/31818 ___ Python tracker <https://bugs.python.org/issue40465> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47022] PEP 594: Document removal of asynchat, asyncore and smtpd
Change by Hugo van Kemenade : -- pull_requests: +30086 stage: backport needed -> patch review pull_request: https://github.com/python/cpython/pull/31997 ___ Python tracker <https://bugs.python.org/issue47022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47022] PEP 594: Document removal of asynchat, asyncore and smtpd
Change by Hugo van Kemenade : -- pull_requests: +30087 pull_request: https://github.com/python/cpython/pull/31998 ___ Python tracker <https://bugs.python.org/issue47022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47061] Deprecate modules listed in PEP 594
Change by Hugo van Kemenade : -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue47061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47061] Deprecate modules listed in PEP 594
Change by Hugo van Kemenade : -- pull_requests: +30169 pull_request: https://github.com/python/cpython/pull/32082 ___ Python tracker <https://bugs.python.org/issue47061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47126] Update to canonical PEP URLs
New submission from Hugo van Kemenade : With the recent implementation https://peps.python.org/pep-0676/ the canonical URL for PEPs has changed from, for example: https://www.python.org/dev/peps/pep-0008/ to: https://peps.python.org/pep-0008/ Redirects are in place so the old links still work, but let's update the docs and docstrings to use the new canonical form. There's also a couple of places in code, so a BPO number is needed. -- assignee: hugovk components: Documentation, Library (Lib), Parser messages: 416051 nosy: hugovk, lys.nikolaou, pablogsal priority: normal severity: normal status: open title: Update to canonical PEP URLs versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue47126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47126] Update to canonical PEP URLs
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +30203 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32124 ___ Python tracker <https://bugs.python.org/issue47126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47126] Update to canonical PEP URLs
Change by Hugo van Kemenade : -- assignee: hugovk -> ___ Python tracker <https://bugs.python.org/issue47126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47126] Update to canonical PEP URLs
Hugo van Kemenade added the comment: Here's a devguide PR: https://github.com/python/devguide/pull/822 -- ___ Python tracker <https://bugs.python.org/issue47126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47138] Bump Sphinx to fix docs build
New submission from Hugo van Kemenade : The docs build on GitHub Actions is passing on `main` but has started failing for the `3.7` - `3.10` branches: ``` Missing the required blurb or sphinx-build tools. Please run 'make venv' to install local copies. make[1]: *** [Makefile:50: build] Error 1 ``` https://github.com/python/cpython/actions/workflows/doc.yml https://github.com/python/cpython/runs/5714593700?check_suite_focus=true This is because the `PATH=./venv/bin:$PATH sphinx-build --version` check is failing: ``` /home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/util/docutils.py:45: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. __version_info__ = tuple(LooseVersion(docutils.__version__).version) Traceback (most recent call last): File "/home/runner/work/cpython/cpython/Doc/./venv/bin/sphinx-build", line 5, in from sphinx.cmd.build import main File "/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/cmd/build.py", line 25, in from sphinx.application import Sphinx File "/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/application.py", line 42, in from sphinx.registry import SphinxComponentRegistry File "/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/registry.py", line 24, in from sphinx.builders import Builder File "/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/builders/__init__.py", line 26, in from sphinx.util import import_object, logging, rst, progress_message, status_iterator File "/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/sphinx/util/rst.py", line 22, in from jinja2 import environmentfilter ImportError: cannot import name 'environmentfilter' from 'jinja2' (/home/runner/work/cpython/cpython/Doc/venv/lib/python3.10/site-packages/jinja2/__init__.py) ``` This is because `3.10` and `3.9` are still using old versions of Sphinx (3.2.1 and 2.4.4 respectively) which is incompatible with the newest Jinja2: https://github.com/pallets/jinja/issues/1630 `main` is using a newer Sphinx (4.2.0), so it passes. Bumping to Sphinx 4.5.0 will fix both `3.9` and `3.10`. `3.7` and `3.8` are affected too. We can bump `main` to use `4.5.0` as well. -- assignee: docs@python components: Documentation messages: 416149 nosy: docs@python, hugovk priority: normal severity: normal status: open title: Bump Sphinx to fix docs build versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue47138> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45618] Documentation builds fail with Sphinx 3.2.1
Hugo van Kemenade added the comment: > > This really should be handled in a new issue since the original fixes for > > all affected releases are already in the field. > Sorry, I got suggested too much with expected fix which is common for both of > those issues. Shall I create a new issue? I created https://bugs.python.org/issue47138, let's continue there. -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue45618> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47138] Bump Sphinx or pin Jinja2 to fix docs build
Hugo van Kemenade added the comment: re: https://bugs.python.org/issue45618#msg416017 Maciej Olko, please could you update these PRs to keep the Sphinx version the same and only pin Jinja2 to match? 3.7: https://github.com/python/cpython/pull/32109 3.8: https://github.com/python/cpython/pull/32111 I guess update them to use this bpo too. Thanks! -- title: Bump Sphinx to fix docs build -> Bump Sphinx or pin Jinja2 to fix docs build ___ Python tracker <https://bugs.python.org/issue47138> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47138] Bump Sphinx or pin Jinja2 to fix docs build
Change by Hugo van Kemenade : -- pull_requests: +30235 pull_request: https://github.com/python/cpython/pull/32154 ___ Python tracker <https://bugs.python.org/issue47138> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47138] Bump Sphinx or pin Jinja2 to fix docs build
Change by Hugo van Kemenade : -- pull_requests: +30234 pull_request: https://github.com/python/cpython/pull/32153 ___ Python tracker <https://bugs.python.org/issue47138> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47138] Pin Jinja2 to fix docs build
Hugo van Kemenade added the comment: I cherry picked Maciej's 3.8 commit into 3.9 and 3.10 PRs: 3.9: https://github.com/python/cpython/pull/32153 3.10: https://github.com/python/cpython/pull/32154 And marking this issue as not relevant to 3.11; instead I bumped the Sphinx version in bpo-47126 / gh-32124 as it's directly relevant there. Thanks! -- title: Bump Sphinx or pin Jinja2 to fix docs build -> Pin Jinja2 to fix docs build versions: -Python 3.11 ___ Python tracker <https://bugs.python.org/issue47138> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36795] "make venv" failed in Docs
Hugo van Kemenade added the comment: I cannot reproduce this (macOS, Python 3.10, pip 22.0.4). As xtreak said, it's probably caused by using a very old version of pip (9.0.1 from Nov 6, 2016), so let's close it. Please let us know if it happens again, and whether updating pip helps. -- nosy: +hugovk stage: needs patch -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue36795> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36329] use the right python "make -C Doc/ serve"
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +30406 pull_request: https://github.com/python/cpython/pull/32354 ___ Python tracker <https://bugs.python.org/issue36329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36329] use the right python "make -C Doc/ serve"
Hugo van Kemenade added the comment: I've made PRs for this: CPython Docs: https://github.com/python/cpython/pull/32354 Devguide: https://github.com/python/devguide/pull/826 Also set this bpo for Python 3.11. -- versions: +Python 3.11 -Python 3.8 ___ Python tracker <https://bugs.python.org/issue36329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41165] [Python 3.10] Remove APIs deprecated long enough
Hugo van Kemenade added the comment: ## unittest What's needed to move forward with removing the deprecated aliases? A deprecation warning is shown for `python3 -m unittest test_bar` and `python3 test_bar.py` (tested Python 3.6-3.10). No deprecation warning is shown for `python setup.py test`, however, both setuptools and pytest have deprecated/discouraged `python setup.py test`: https://github.com/pypa/setuptools/pull/1878 https://github.com/pytest-dev/pytest/pull/5546 https://github.com/pytest-dev/pytest/issues/5534 Docs already mention they are deprecated: https://docs.python.org/3/library/unittest.html#deprecated-aliases > At a bare minimum you should list removed features in the 3.9 changelog and > porting guide as "will be removed in 3.10". I would even argue to add > deprecation warnings to the code in 3.9 (with permission from the RM). If the > RM is against deprecation warnings, then it might be good idea to postpone > removal to 3.11. So at this stage (3.10 in RC), do we need to list them in the 3.11 changelog and porting guide as "will be removed in 3.12"? -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue41165> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45124] Remove deprecated bdist_msi command
New submission from Hugo van Kemenade : The bdist_msi command was deprecated in Python 3.9 by bpo-39586 (commit 2d65fc940b897958e6e4470578be1c5df78e319a). It can be removed in Python 3.11. PR to follow. -- components: Distutils messages: 401216 nosy: dstufft, eric.araujo, hugovk priority: normal severity: normal status: open title: Remove deprecated bdist_msi command versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45124> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45124] Remove deprecated bdist_msi command
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +26619 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28195 ___ Python tracker <https://bugs.python.org/issue45124> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39586] Deprecate bdist_msi: use bdist_wheel instead
Hugo van Kemenade added the comment: Following this deprecation in Python 3.9, please see https://bugs.python.org/issue45124 / https://github.com/python/cpython/pull/28195 to remove the deprecation in Python 3.11. -- ___ Python tracker <https://bugs.python.org/issue39586> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45129] Remove deprecated reuse_address parameter from create_datagram_endpoint()
New submission from Hugo van Kemenade : The reuse_address parameter was deprecated in Python 3.9 by bpo-37228. It can be removed in Python 3.11. PR to follow. -- components: asyncio messages: 401290 nosy: asvetlov, hugovk, yselivanov priority: normal severity: normal status: open title: Remove deprecated reuse_address parameter from create_datagram_endpoint() versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45129] Remove deprecated reuse_address parameter from create_datagram_endpoint()
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +26632 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28207 ___ Python tracker <https://bugs.python.org/issue45129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45132] Remove deprecated __getitem__ methods
New submission from Hugo van Kemenade : The __getitem__ methods of xml.dom.pulldom.DOMEventStream, wsgiref.util.FileWrapper and were deprecated in Python 3.8 by bpo-9372 / GH-8609. They can be removed in Python 3.11. -- components: Library (Lib) messages: 401322 nosy: hugovk priority: normal severity: normal status: open title: Remove deprecated __getitem__ methods versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45132> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45132] Remove deprecated __getitem__ methods
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +26647 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28225 ___ Python tracker <https://bugs.python.org/issue45132> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
New submission from Hugo van Kemenade : In the configparser module, these have been deprecated since Python 3.2: * the SafeConfigParser class, * the filename property of the ParsingError class, * the readfp method of the ConfigParser class, They can be removed in Python 3.11. -- components: Library (Lib) messages: 401644 nosy: hugovk priority: normal severity: normal status: open title: Remove configparser deprecations versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +26708 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28292 ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45173] Remove configparser deprecations
Hugo van Kemenade added the comment: Also, the LegacyInterpolation class is deprecated since Python 3.2 but with no DeprecationWarning. A quick sampling of GitHub results shows only copies of CPython's configparser.py and test_configparser.py https://github.com/search?l=Python&p=1&q=LegacyInterpolation+extension%3Apy+language%3APython+language%3APython&ref=advsearch&type=Code No use found in the top 200 PyPI packages. Is it safe to remove now, or should it raise DeprecationWarning for a couple of releases first? -- ___ Python tracker <https://bugs.python.org/issue45173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42135] [importlib] Deprecate find_module() & find_loader() mplementations
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 1.0 -> 2.0 pull_requests: +26725 pull_request: https://github.com/python/cpython/pull/28312 ___ Python tracker <https://bugs.python.org/issue42135> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45320] Remove deprecated inspect functions
New submission from Hugo van Kemenade : inspect.getargspec was deprecated in docs since 3.0 (https://docs.python.org/3.0/library/inspect.html?highlight=getargspec#inspect.getargspec), raising a DeprecationWarning since 3.5 (bpo-20438, https://github.com/python/cpython/commit/3cfec2e2fcab9f39121cec362b78ac235093ca1c). inspect.formatargspec was deprecated in docs since 3.5 (https://docs.python.org/3.5/library/inspect.html?highlight=getargspec#inspect.formatargspec), raising a DeprecationWarning since 3.8 (bpo-33582, https://github.com/python/cpython/commit/46c5cd0f6e22bdfbdd3f0b18f1d01eda754e7e11). Undocumented inspect.Signature.from_function and inspect.Signature.from_builtin in docs and by raising a DeprecationWarning since 3.5 (bpo-20438, https://github.com/python/cpython/commit/3cfec2e2fcab9f39121cec362b78ac235093ca1c). These can be removed in Python 3.11. -- components: Library (Lib) messages: 402860 nosy: hugovk priority: normal severity: normal status: open title: Remove deprecated inspect functions versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45320> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45320] Remove deprecated inspect functions
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +26989 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28618 ___ Python tracker <https://bugs.python.org/issue45320> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33582] formatargspec deprecated but does not emit DeprecationWarning.
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 6.0 -> 7.0 pull_requests: +26991 pull_request: https://github.com/python/cpython/pull/28618 ___ Python tracker <https://bugs.python.org/issue33582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20438] inspect: Deprecate getfullargspec?
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 11.0 -> 12.0 pull_requests: +26990 pull_request: https://github.com/python/cpython/pull/28618 ___ Python tracker <https://bugs.python.org/issue20438> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45320] Remove deprecated inspect functions
Hugo van Kemenade added the comment: Of the 188 repos I managed to clone of 200 top PyPI packages, looks like these 9 are still calling them: botocore client_python cython google-api-python-client grpc ipython pycodestyle pyrsistent wrapt Details at https://github.com/python/cpython/pull/28618#issuecomment-930524790 -- ___ Python tracker <https://bugs.python.org/issue45320> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45837] Fix turtle deprecations
New submission from Hugo van Kemenade : turtle's settiltangle was deprecated in Python 3.1: "Deprecated since version 3.1." https://docs.python.org/3.10/library/turtle.html#turtle.settiltangle says of settiltangle: And the reason: "`Turtle.tiltangle()` has been enhanced in functionality: it now can be used to get or set the tiltangle. `Turtle.settiltangle()` has been deprecated." https://docs.python.org/3.10/library/turtle.html#changes-since-python-3-0 However, in docstrings, tiltangle was accidentally marked as deprecated: "Deprecated since Python 3.1" https://github.com/python/cpython/blob/v3.10.0/Lib/turtle.py#L2880 Neither tiltangle nor settiltangle raise DeprecationWarnings. So let's: * Correct tiltangle's docstring to say it's not really deprecated * Update settiltangle's docstring to say it is deprecated * Add a DeprecationWarning to settiltangle * Internally call self.tiltangle instead of self.settiltangle BPO references: 2009 https://bugs.python.org/issue5923 - settiltangle originally deprecated, with rationale. 2010 https://bugs.python.org/issue7888 - the mixup was discovered and apparently corrected in py3k and release31-maint. I've not done the SCM archaeology to discover why this regressed. 2020 https://bugs.python.org/issue41165 - both mentioned as deprecated, mixup not noted. -- components: Library (Lib) messages: 406536 nosy: hugovk priority: normal severity: normal status: open title: Fix turtle deprecations versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45837> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45837] Fix turtle deprecations
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +27853 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29618 ___ Python tracker <https://bugs.python.org/issue45837> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45837] Fix turtle deprecations
Change by Hugo van Kemenade : -- pull_requests: +27861 pull_request: https://github.com/python/cpython/pull/29629 ___ Python tracker <https://bugs.python.org/issue45837> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45837] Fix turtle deprecations
Change by Hugo van Kemenade : -- pull_requests: +27862 pull_request: https://github.com/python/cpython/pull/29630 ___ Python tracker <https://bugs.python.org/issue45837> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45903] What’s New In Python 3.11: wrong reference to Signature.from_callable
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +28045 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29813 ___ Python tracker <https://bugs.python.org/issue45903> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45320] Remove deprecated inspect functions
Change by Hugo van Kemenade : -- pull_requests: +28046 pull_request: https://github.com/python/cpython/pull/29813 ___ Python tracker <https://bugs.python.org/issue45320> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45903] What’s New In Python 3.11: wrong reference to Signature.from_callable
Hugo van Kemenade added the comment: Thanks Jakub! I've made https://github.com/python/cpython/pull/29813 to fix it. -- ___ Python tracker <https://bugs.python.org/issue45903> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39586] Deprecate bdist_msi: use bdist_wheel instead
New submission from Hugo van Kemenade : According to the "Deprecate bdist_wininst" discussion (July 2019), bdist_msi can be deprecated: https://discuss.python.org/t/deprecate-bdist-wininst/1929 Victor Stinner wrote: "Now the question is if someone here wants to go further is deprecate all distutils commands except sdist and bdist_wheel? Steve Dower wants to deprecate bdist_msi as well: I’m not sure who use bdist_msi. It’s another form of GUI installer, so it’s similar to bdist_wininst. I would also strongly encourage to use bdist_wheel rather than bdist_msi." Brett Cannon wrote: "Probably a good idea, but I personally don’t have the time." Steve Dower wrote: "I think the others are fine to leave (though if people who work more closely with those tools want to say drop them then I’m fine with that too). "bdist_msi and bdist_exe don’t integrate with any other package managers, can’t be integrated with any other installer besides our own Python installer, and in any case are worse than simply copying the files. (If we had a bdist_msm I’d be slightly more sympathetic, but we don’t and probably should not :) ) "I also don’t necessarily think that wheels are always the alternative, particularly for embedded scenarios, but I do think that the fewer options we provide by default will help people find the option they actually need, rather than assuming that because it’s “blessed” it must see correct." And in "Remove distutils bdist_wininst command" (February 2020): https://discuss.python.org/t/remove-distutils-bdist-wininst-command/3115 Victor Stinner wrote: "I don’t plan to remove bdist_msi, even if wheel packages are now recommended." Steve Dower wrote: "We should, though. Installing a package using an MSI is worse than an EXE, as it leaves far more cruft behind if you don’t uninstall it before changing/removing the Python install. "Standalone apps should bundle everything, like pynsist or briefcase. GPO deployment should create their own MSI with everything they want in the bundle and deploy that. Perhaps someone can make an “installer” based on the py.exe launcher (which I believe supports an attached zip file) that will use pip and a local/embedded wheel. "But we should really discourage package installs that don’t support venv and/or leave cruft behind." Victor Stinner wrote: "If you want to see it disappear, you should start by deprecating it in Python 3.9. It would be a first step." PR to follow. See also: * https://bugs.python.org/issue37481 "Deprecate bdist_wininst: use bdist_wheel instead" * https://bugs.python.org/issue39541 "distutils: Remove bdist_wininst (Windows .exe installers) in favor of bdist_wheel (.whl)" -- components: Distutils, Windows messages: 361633 nosy: dstufft, eric.araujo, hugovk, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Deprecate bdist_msi: use bdist_wheel instead versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue39586> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39586] Deprecate bdist_msi: use bdist_wheel instead
Change by Hugo van Kemenade : -- keywords: +patch pull_requests: +17790 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18415 ___ Python tracker <https://bugs.python.org/issue39586> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37324] collections: remove deprecated aliases to ABC classes
Change by Hugo van Kemenade : -- nosy: +hugovk nosy_count: 4.0 -> 5.0 pull_requests: +22611 pull_request: https://github.com/python/cpython/pull/23754 ___ Python tracker <https://bugs.python.org/issue37324> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41268] 3.9-dev regression? TypeError: exec_module() missing 1 required positional argument: 'module'
New submission from Hugo van Kemenade :
For the past 3 months we've been testing Pillow on Travis CI using 3.9-dev,
which Travis builds nightly from the 3.9 branch.
Two days ago the 3.9-dev build passed, but it failed yesterday with the same
Pillow commit, and all subsequent builds.
* Last pass: https://travis-ci.org/github/python-pillow/Pillow/jobs/706015838
* First fail: https://travis-ci.org/github/hugovk/Pillow/jobs/706476038
Diffing the logs, here's the CPython commits for each:
platform linux 3.9.0b4+ (heads/3.9:edeaf61, Jul 7 2020, 06:29:52)
platform linux 3.9.0b4+ (heads/3.9:1d1c574, Jul 8 2020, 07:05:21)
Diff of those commits:
https://github.com/python/cpython/compare/edeaf61b6827ab3a8673aff1fb7717917f08f003..1d1c5743400bdf384ec83eb6ba5b39a355d121e3
It's also failing with the most recent:
platform linux 3.9.0b4+ (heads/3.9:e689789, Jul 9 2020, 07:57:24)
I didn't see anything obvious to cause it, so thought I'd better report it here
to be on the safe side.
Our tracking issue: https://github.com/python-pillow/Pillow/issues/4769
Here's the traceback:
Finished processing dependencies for Pillow==7.3.0.dev0
python3 selftest.py
Traceback (most recent call last):
File "/home/travis/build/hugovk/Pillow/selftest.py", line 6, in
from PIL import Image, features
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/Image.py",
line 94, in
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/_imaging.py",
line 8, in
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/_imaging.py",
line 7, in __bootstrap__
TypeError: exec_module() missing 1 required positional argument: 'module'
Makefile:59: recipe for target 'install-coverage' failed
make: *** [install-coverage] Error 1
Traceback (most recent call last):
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
line 495, in _importconftest
return self._conftestpath2mod[key]
KeyError: PosixPath('/home/travis/build/hugovk/Pillow/conftest.py')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/python/3.9-dev/lib/python3.9/runpy.py", line 197, in
_run_module_as_main
return _run_code(code, main_globals, None,
File "/opt/python/3.9-dev/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pytest/__main__.py",
line 7, in
raise SystemExit(pytest.main())
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
line 105, in main
config = _prepareconfig(args, plugins)
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
line 257, in _prepareconfig
return pluginmanager.hook.pytest_cmdline_parse(
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/hooks.py",
line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/manager.py",
line 93, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/manager.py",
line 84, in
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
line 203, in _multicall
gen.send(outcome)
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/helpconfig.py",
line 90, in pytest_cmdline_parse
config = outcome.get_result()
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
line 80, in get_result
raise ex[1].with_traceback(ex[2])
File
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
line 187, in _multicall
res = hook_impl.function(*args)
File
"/home/travis/vi
[issue41268] 3.9-dev regression? TypeError: exec_module() missing 1 required positional argument: 'module'
Hugo van Kemenade added the comment: Okay, looks like this is actually a setuptools issue, introduced in version 47.3.2. Reported: https://github.com/pypa/setuptools/issues/2246 -- ___ Python tracker <https://bugs.python.org/issue41268> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41282] Deprecate and remove distutils
Change by Hugo van Kemenade : -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue41282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41917] Python 3.9rc2 fails to install matplotlib
Hugo van Kemenade added the comment: This probably isn't an issue with CPython 3.9.0 itself, but rather third-party libraries needing to add 3.9 support and provide wheels, and they may be waiting for 3.9.0 to be officially released (due out today!). Here's a PR to add Python 3.9 support to Kiwi (aka kiwisolver): https://github.com/nucleic/kiwi/pull/88 -- nosy: +hugovk ___ Python tracker <https://bugs.python.org/issue41917> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
