[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: One true positive today: https://github.com/python/cpython/pull/32355 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21956] Doc files deleted from repo are not deleted from docs.python.org.
Julien Palard added the comment: This is resolved since https://github.com/python/docsbuild-scripts/pull/28. It could still happen in very specific conditions, but not for a long time, see: https://github.com/python/docs-community/issues/41#issuecomment-1088462199= -- nosy: +mdk resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue21956> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset d0e696e05d4aaca1f1cde72a5c3326ca3d0f5c24 by Julien Palard in branch 'main': bpo-42238: [doc]: A make sucpicious false positive. (GH-32329) https://github.com/python/cpython/commit/d0e696e05d4aaca1f1cde72a5c3326ca3d0f5c24 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +30388 pull_request: https://github.com/python/cpython/pull/32329 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset bdc497496548e30fa208a8d98c30bf6d1833ac4c by Julien Palard in branch 'main': bpo-42238: [doc]: make suspicious: false positive. (GH-32292) https://github.com/python/cpython/commit/bdc497496548e30fa208a8d98c30bf6d1833ac4c -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: One true positive and one false positive this week, see: - 7f9c084fdec7ddcfe8855aa79f98545591ae2261 - ec8906fb5930b1f078e2a2170cdf445e6c6faf57 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +30354 pull_request: https://github.com/python/cpython/pull/32292 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45953] Statically allocate interpreter states as much as possible.
Julien Palard added the comment: > Since you seem to be challenging the value of 9, my question to you > is, why do you care what the refcount of 1 is? Yesterday I was teaching Python, and we were speaking of integer immutability, names being "labels to objects" and so on, and I was showing the memory layout of all of this by hand on a whiteboard while "prooving" my drawings using an interpreter. While doing so came a question like "So, many modules can use the object int(1)?" So I answered yes, told that I expected many reuse of 1, and went importing sys.getrefcount to show them. And boom, it printed 100209 so I bugged for a few seconds, the value was obviously not the real refcount, and was also obviously bumped by a constant like 1, so I went inspecting why and found this commit. I have nothing against keeping 9, but in the other hand it could surprise other people, maybe we should at least document it near sys.getrefcount. -- ___ Python tracker <https://bugs.python.org/issue45953> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45953] Statically allocate interpreter states as much as possible.
Julien Palard added the comment: Hum, and why 9? I am probably missing something obvious but 1 should be enough to ensure the value never hits 0. Except for refcount bugs obviously, but I don't think this is the right reason? -- ___ Python tracker <https://bugs.python.org/issue45953> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45953] Statically allocate interpreter states as much as possible.
Julien Palard added the comment:
Since
https://github.com/python/cpython/commit/121f1f893a39d0b58d3d2b5597505c154ecaac2a,
`sys.getrefcount(1)` is surprising:
>>> __import__("sys").getrefcount(1)
100210
Should sys.getrefcount try to "fix" the value like by returning
`PyREFCNT(object) % 9`? (But using a define to avoid the "magic,
copy/pasted value").
--
nosy: +mdk
___
Python tracker
<https://bugs.python.org/issue45953>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset ec8906fb5930b1f078e2a2170cdf445e6c6faf57 by Julien Palard in branch 'main': bpo-42238: [doc] Some lines moved in rst, but had hardcoded lineno in susp-ignored.csv. (GH-32070) https://github.com/python/cpython/commit/ec8906fb5930b1f078e2a2170cdf445e6c6faf57 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +30159 pull_request: https://github.com/python/cpython/pull/32070 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +30067 pull_request: https://github.com/python/cpython/pull/31977 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: News: Hitting 3 months without a true positive from `make suspicious`, looks like sphinxlint starting to take over properly, I hope to close this issue soon (like in a few months maybe). Also sphinxlint attracted some contributors [1] \o/ [1] https://github.com/sphinx-contrib/sphinx-lint -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset b878b3af0b3a9e3ab3ffcaf90a4066dfb3bb7cac by Julien Palard in branch 'main': bpo-42238: [doc] moving from rstlint.py to sphinx-lint. (GH-31097) https://github.com/python/cpython/commit/b878b3af0b3a9e3ab3ffcaf90a4066dfb3bb7cac -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44006] symbol documentation still exists
Julien Palard added the comment: Oh, it's ~unrelated, but thanks for the heads up, I overlooked a Sentry error :D It's related to: https://github.com/python/docsbuild-scripts/issues/122, let's track it there. (The visible effects are the same: the full build, reponsible for deleting the file is failing, while the quick (html only, not removing files) build succeed, so the old HTML files are kept if PDF builds are failing...) -- resolution: -> fixed status: open -> closed ___ Python tracker <https://bugs.python.org/issue44006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +29282 pull_request: https://github.com/python/cpython/pull/31097 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: Georg, I was able to move forward: - https://github.com/sphinx-contrib/sphinx-lint - https://pypi.org/project/sphinx-lint/ Does everything looks good to you? Next step would be to remove rstlint.py from Docs/tools and add a dependency to rstlint from the Makefile (for make check), so the CI uses sphinx-lint. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: OK, we have: https://github.com/sphinx-contrib/sphinx-lint Ping me if you want rights :) -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment:
> You gave me a small shock, but I checked and it was only 11/12 years ago :D
HAha! Either I misstyped 12 as 21, either I'm bad at math, sorry for the shock
;)
> I'm fine with moving this out of tree; please coordinate with the Sphinx
> maintainers whether it should be an "official" extension or completely
> separate.
They propose [1] to have it in sphinx-contrib ("A collection of Sphinx
extensions maintained by their respective authors. It is not an official part
of Sphinx."), what do you think?
[1] https://github.com/sphinx-doc/sphinx/issues/10143#issuecomment-1025093280
--
___
Python tracker
<https://bugs.python.org/issue42238>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset 44afdbd5af4503e376148e9404b9c7a4f595b1fe by Julien Palard in branch 'main': bpo-42238: [doc] Avoid hardcoding fast-moving lines in susp-ignored.csv. (GH-30981) https://github.com/python/cpython/commit/44afdbd5af4503e376148e9404b9c7a4f595b1fe -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +29160 pull_request: https://github.com/python/cpython/pull/30981 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: I slowly started to work on rstlint in its own tree because working in a single file felt inconfortable. The more I advanced in this direction the more it made sense to me: - I first added tests, I may have been able to do so in the cpython tree though. - It would ease the publication of it to pypi.org so it can be used by other projects. - It may ease contributions (some non-core-devs could be given rights to the repo, which make sense as it's not really Python related but more Sphinx related). It currently looks like this: https://github.com/JulienPalard/sphinxlint but should obviously be moved to github.com/python/ if we adopt this direction. So what do you think? (cc Georg as the main author of the script) If so I'd also like to rename the thing, it's currently named `rstlint`, but it's more a `sphinxlint` as Sphinx has adds a lot to rst and existing rst linters does not handle Sphinx well. -- nosy: +georg.brandl ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +29059 pull_request: https://github.com/python/cpython/pull/30879 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46507] enabling cProfile to profile code given as an argument "à la" timeit
Change by julien tayon : -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/issue46507> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46507] enabling cProfile to profile code given as an argument "à la" timeit
New submission from julien tayon : well, you want to use python3 -mcProfile -othis.prof 'oneliner in python to test something' And weirdly enough this normally expected behaviour does not work. It's because last argument is expected to be the path of the script name to profile. But, it can be fixed easily with no downside Since it is an expected behaviour and is minimal changing anything in documentation or news seems to superfluous An exemple of « this is a standard de fait » is the fact that the awesome module of vstinner timeit does this already. https://github.com/python/cpython/pull/30859 -- components: Library (Lib) messages: 411517 nosy: jul2, vstinner priority: normal pull_requests: 29042 severity: normal status: open title: enabling cProfile to profile code given as an argument "à la" timeit type: enhancement versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue46507> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To and other address headers
Julien Castiaux added the comment: Hello there, Friendly reminder that this issue is still open and that there is a pull request ready. We continue to face the issue in production and our customers are getting upset. Can you provide us a schedule when this issue will be addressed? So that we can decide either to wait our to start thinking about possible mitigations our side? Regards, Julien -- ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46318] asyncio and ssl: ResourceWarning: unclosed transport
Julien Palard added the comment: Probably related to https://bugs.python.org/issue44011 and https://github.com/MagicStack/uvloop/pull/385 -- ___ Python tracker <https://bugs.python.org/issue46318> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45729] [doc] "history and license" link has wrong target
Julien Palard added the comment: > dev docs direct to `/license.html` which redirects to `/3/license.html` All docs are redirecting to `/license.html`, this allow it to work also out of docs.python.org. > 3.9 docs have the same; wouldn’t it be better to have `/3.9/license.html`? It's maybe a slight better yes (the page should be the same so I don't know if it make real difference), but doing so means a bit of complexity, which I don't think is worth it. I tried to keep it simple for this fix (the previous state was "links to the current page" which was worse). -- ___ Python tracker <https://bugs.python.org/issue45729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46318] asyncio and ssl: ResourceWarning: unclosed transport
Julien Palard added the comment: I don't know if it's related but _SSLPipe._shutdown_cb looks never called, in: self._sslobj.unwrap() self._sslobj = None self._state = _UNWRAPPED if self._shutdown_cb: self._shutdown_cb() the unwrap() call seems to always raise (The operation did not complete (read) (_ssl.c:2756)), thus never calling `self._shutdown_cb()`. -- ___ Python tracker <https://bugs.python.org/issue46318> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45729] [doc] "history and license" link has wrong target
Julien Palard added the comment: I checked on docs.python.org and it's fixed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue45729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45729] [doc] "history and license" link has wrong target
Change by Julien Palard : -- keywords: +patch pull_requests: +28728 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30527 ___ Python tracker <https://bugs.python.org/issue45729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45729] [doc] "history and license" link has wrong target
Julien Palard added the comment: This should be fixed in python-docs-theme==2022.1. I'll close the issue when I actually see the fix applied on docs.python.org. -- nosy: +mdk ___ Python tracker <https://bugs.python.org/issue45729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46318] asyncio and ssl: ResourceWarning: unclosed transport
Julien Palard added the comment: Feel like SSLProtocol's connection_lost should "bubble up" the info by calling SSLProtocolTransport's close. But I'm no familiar with this stack. -- ___ Python tracker <https://bugs.python.org/issue46318> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46318] asyncio and ssl: ResourceWarning: unclosed transport
Julien Palard added the comment: Related to: https://bugs.python.org/issue23243 -- ___ Python tracker <https://bugs.python.org/issue46318> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46318] asyncio and ssl: ResourceWarning: unclosed transport
New submission from Julien Palard :
Originally opened at: https://github.com/aio-libs/aiohttp/issues/6071
Reproducer:
import asyncio
class DumbProtocol(asyncio.Protocol):
def connection_made(self, transport):
print("Connection made")
self.transport = transport
def data_received(self, data):
print("Data received: {!r}".format(data))
async def main():
loop = asyncio.get_running_loop()
for i in range(2):
_, _ = await loop.create_connection(DumbProtocol, "python.org",
443, ssl=True)
while True:
print("Waiting for the server to close the connection...")
await asyncio.sleep(10)
asyncio.run(main())
Using this reproducer I get a ResourceWarning:
Data received: b"HTTP/1.0 408 Request Time-out\r\nCache-Control:
no-cache\r\nConnection: close\r\nContent-Type:
text/html\r\n\r\n408 Request Time-out\nYour browser didn't
send a complete request in time.\n\n\n"
/usr/lib/python3.9/asyncio/sslproto.py:320: ResourceWarning: unclosed
transport
_warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
Object allocated at (most recent call last):
File "/usr/lib/python3.9/asyncio/sslproto.py", lineno 445
self._app_transport = _SSLProtocolTransport(self._loop, self)
I can also reproduce it on current master.
--
components: asyncio
messages: 410156
nosy: asvetlov, mdk, yselivanov
priority: normal
severity: normal
status: open
title: asyncio and ssl: ResourceWarning: unclosed transport
versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue46318>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: Another true positive for make suspicious: WARNING: [c-api/apiabiversion:70] ":macro" found in "the same format as the c:macro:" I'm working on implementing it on rstlint, in the meantime I opened: => https://github.com/python/cpython/pull/30149 to fix this occurrence. This show that the current version of rstlint catches two mores \o/ -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To and other address headers
Julien Castiaux added the comment: Hello there, There is a pull-request on github, had to modify `_refold_parse_tree` but I could keep the diff quite small. It is properly tested and it is waiting a review :) We have a patch at work so it is *absolutely not* urgent, feel free to review it *anytime*. Since we are using the Ubuntu LTS version of python, we might be interested by a backport till 3.7, quite honestly I'm happy it was flag as a security issue :D -- ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To and other address headers
Change by Julien Castiaux : -- keywords: +patch pull_requests: +28107 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29881 ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: A new false positive in b48ac6fe38b2fca9963b097c04cdecfc6083104e: +++ b/Misc/NEWS.d/next/Tests/2021-11-23-12-36-21.bpo-45878.eOs_Mp.rst @@ -0,0 +1,2 @@ +Test ``Lib/ctypes/test/test_functions.py::test_mro`` now uses +``self.assertRaises`` instead of ``try/except``. It's been only one month since the last true positive, so I'll still watching this closely... -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: /!\ rstlint did triggered some false positive: https://github.com/python/cpython/pull/29389/commits/f8ea20a0b51711b1c352c4aa4663cb953e7ebdc8 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +27893 pull_request: https://github.com/python/cpython/pull/29652 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +27867 pull_request: https://github.com/python/cpython/pull/29636 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: A new false positive today from 31b3a70edb1216bdc8fab3b2eafd8ddb00487f41: https://docs.python.org/dev/reference/datamodel.html#class-getitem-versus-getitem in: should be called:: from inspect import isclass def subscribe(obj, x): """Return the result of the expression `obj[x]`""" make suspicious whines about the backticks. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45667] Better error message on failing to create a venv due to failing ensurepip
New submission from Julien Palard : Currently if ensurepip fails for a reason or another, for example if a wrong module gets imported: $ touch http.py $ python3.10 -m venv .venv Error: Command '['/tmp/.venv/bin/python3.10', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1. the error is not helpfull. Maybe venv should just dump the stderr from ensurepip so we can learn a bit more about it (it's « understandable » in ensurepip traceback that it's in relation with http.py, in the given example.) -- messages: 405297 nosy: mdk priority: normal severity: normal status: open title: Better error message on failing to create a venv due to failing ensurepip ___ Python tracker <https://bugs.python.org/issue45667> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45633] Py_GT listed twice in Doc/extending/newtypes.rst
New submission from Julien Palard : In Doc/extending/newtypes one can read: > This function is called with two Python objects and the operator as > arguments, where the operator is one of Py_EQ, Py_NE, Py_LE, Py_GT, Py_LT or > Py_GT. It bet one of them should be Py_GE. (I let this one as an easy first contrib.) -- assignee: docs@python components: Documentation keywords: easy messages: 405119 nosy: docs@python, mdk priority: normal severity: normal status: open title: Py_GT listed twice in Doc/extending/newtypes.rst ___ Python tracker <https://bugs.python.org/issue45633> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45596] Python opens the ./ file on exception while using -c
New submission from Julien Palard : When running `python -c 'raise ValueError'` Python tries to open the '' file, so: $ echo Coucou > '' $ python -c 'raise ValueError' Traceback (most recent call last): File "", line 1, in Coucou ValueError -- messages: 404922 nosy: mdk priority: normal severity: normal status: open title: Python opens the ./ file on exception while using -c ___ Python tracker <https://bugs.python.org/issue45596> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45501] [idea] Successfully creating a venv could print a message.
New submission from Julien Palard : I realized that many students get surprised by `python -m venv .venv` not printing anything, a few even think it completly failed. I'm OK teaching them this is normal, as `mv`, `cp`, `rm`, `django-admin startproject`, ... does not print neither when they succeed. But I fear many other Python users could be surprised too and not have a teacher around to reassure them. I kept this as a status-quo for years but thinking of it today I though « And why not telling them how to activate the venv? » Would'nt it be great to have: $ python3 -m venv .venv Environment created successfully, activate it using: source .venv/bin/activate or PS C:\Users\Admin> python3 -m venv .venv Environment created successfully, activate it using: .venv\Scripts\Activate.ps1 and so on? A `-q`/`--quiet` could be added for scripts creating venvs. -- messages: 404132 nosy: mdk priority: normal severity: normal status: open title: [idea] Successfully creating a venv could print a message. ___ Python tracker <https://bugs.python.org/issue45501> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45495] IDLE: Add match and case
New submission from Julien Palard : In IDLE, when hitting Ctrl-space on `matc` or `cas`, there's no completion to `match` and `case. References: https://mail.python.org/archives/list/d...@python.org/thread/DRZIHLQU25JUD7IQKCOIIKI4ADB746MA/ -- assignee: terry.reedy components: IDLE messages: 404083 nosy: mdk, terry.reedy priority: normal severity: normal status: open title: IDLE: Add match and case versions: Python 3.10, Python 3.11 ___ Python tracker <https://bugs.python.org/issue45495> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: DING DING DING DING DING DING, a new one today, and a true positive for `make suspicious`, fixed in: https://github.com/python/cpython/pull/28988/files (along with the test added to rstlint) -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45411] Add Mimetypes for Subtitle Files
Julien Palard added the comment: New changeset d74da9e140441135a4eddaef9a37f00f32579038 by Josephine-Marie in branch 'main': bpo-45411: Update mimetypes.py (GH-28792) https://github.com/python/cpython/commit/d74da9e140441135a4eddaef9a37f00f32579038 -- ___ Python tracker <https://bugs.python.org/issue45411> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New suspicious today: [library/typing:1011] "`" found in "# Type of ``val`` is narrowed to ``list[str]``." But it's only because the old one with List[str] instead of list[str] was in susp-ignored.csv, so I just fixed susp-ignored.csv in https://github.com/python/cpython/pull/28827. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +27143 pull_request: https://github.com/python/cpython/pull/28827 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use better HTML and separate CSS
Julien Palard added the comment: New changeset c91b6f57f3f75b482e4a9d30ad2afe37892a8ceb by Julien Palard in branch 'main': bpo-10716: Migrating pydoc to html5. (GH-28651) https://github.com/python/cpython/commit/c91b6f57f3f75b482e4a9d30ad2afe37892a8ceb -- ___ Python tracker <https://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45411] Add Mimetypes for Subtitle Files
Julien Palard added the comment: Those two looks legit to me. -- nosy: +mdk ___ Python tracker <https://bugs.python.org/issue45411> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use better HTML and separate CSS
Julien Palard added the comment: Does someone want to review https://github.com/python/cpython/pull/28651? -- ___ Python tracker <https://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28206] signal.Signals not documented
Julien Palard added the comment: New changeset 9be930f9b169fb3d92693670ae069df902709b83 by Bibo-Joshi in branch 'main': bpo-28206: Document signals Handlers, Sigmasks and Signals enums (GH-28628) https://github.com/python/cpython/commit/9be930f9b169fb3d92693670ae069df902709b83 -- nosy: +mdk ___ Python tracker <https://bugs.python.org/issue28206> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32523] inconsistent spacing in changelog.html
Julien Palard added the comment: This still happen, but it's hard to tell if it'll happen from blurb, as when it's two paragraphs consisting of a text and a list it does not happen, sphinx just put the list as a sublist and it's clean. I don't want to tell people stop using list, it's very readable. Also sometimes having a paragraph, a list, then one or two more paragraphs looks usefull, see examples in [1]. [1]: https://github.com/python/core-workflow/pull/274#issuecomment-931387938 So I'm no longer trying to fix it in blurb. -- ___ Python tracker <https://bugs.python.org/issue32523> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use better HTML and separate CSS
Julien Palard added the comment: Tried myself at it. I'm not a front-end guy, fasten your seatbelts. I tried to keep it minimal, but after some work the change is not that small, I focused on the HTML modernization only, not the design (to try to land at least a first step toward modernization). -- ___ Python tracker <https://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use better HTML and separate CSS
Change by Julien Palard : -- pull_requests: +27019 pull_request: https://github.com/python/cpython/pull/28651 ___ Python tracker <https://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset 37272f5800ee1e9fcb2da4a1766366519b9b3d94 by Julien Palard in branch 'main': bpo-42238: [doc] remove unused, and deduplicate, suspicious ignore rules. (GH-28137) https://github.com/python/cpython/commit/37272f5800ee1e9fcb2da4a1766366519b9b3d94 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +26576 pull_request: https://github.com/python/cpython/pull/28137 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset 21fa8547921d28b80b8a88d034081cab000d5480 by Julien Palard in branch 'main': bpo-42238: [doc] Some more make suspicious false positives. (GH-27945) https://github.com/python/cpython/commit/21fa8547921d28b80b8a88d034081cab000d5480 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: 10 false positives today, see: https://github.com/python/cpython/pull/27945/files I think I now need to put a deadline on this issue, let's say: one year without true positives and I drop it, so 2021-07-19 for now. (In the meantime, I continue to convert each true positives to rstlint, I converted 3 of them so far.) -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +26391 pull_request: https://github.com/python/cpython/pull/27945 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To
Julien Castiaux added the comment: Hello David, Victor, Thank you for the triage, it reminds me about this issue. David, the solution I tried last month was wrong, it was breaking (for good reasons) tons of unittests. It seems to me that there is indeed no other solution than to bloat the re-folding function a bit more and to fix the dbquotes there as your last email suggested. I agree with you that the code will be even messier, honestly I spent quite some time understanding the _refold_parse_tree function and I don't feel like patching it. Regards, On 11.08.21 14:57, STINNER Victor wrote: > STINNER Victor added the comment: > > I change the issue type to security. The bug can be abused to send emails to > the wrong email address. > > -- > nosy: +vstinner > type: behavior -> security > > ___ > Python tracker > <https://bugs.python.org/issue44637> > ___ -- ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: Another one \o/ Fix in: https://github.com/python/cpython/pull/27238 It is: :func:pdb.main Detected by make suspicious as: WARNING: [whatsnew/changelog:320] ":func" found in ": Refactor argument processing in :func:pdb.main to simplify" WARNING: [whatsnew/changelog:320] ":pdb" found in ": Refactor argument processing in :func:pdb.main to simplify" I added a test in the same PR to spot this one in rstlint. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +25787 pull_request: https://github.com/python/cpython/pull/27238 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To
Julien Castiaux added the comment: Update, it works fine with the compat32 policy -- ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44637] Quoting issue on header Reply-To
Julien Castiaux added the comment: Hello David, I'm working in the same company as Baptiste and I'm trying to solve the problem. The issue is indeed related to the folding algorithm, the DBQUOTE character is lost in the parse_tree AST thus when the folding algo split the children to find a sweat spot to split the line it doesn't re-introduce the DBQUOTE and instead inject the content of the BareQuotedString right away. I'm working on a fix which consist of adding two DBQUOTE, one at the beginning and one at the end, of the BareQuotedString token when it is created (_header_value_parser.py@get_bare_quoted_string()). I was inspired by how the angles < and > are injected around the AddrSpec token in a AngleAddr token. Right now my fix isn't correct, there are some unittest falling. I'm trying to get it working and hopefully get back to you with a nice pull-request :) Regards, Julien -- ___ Python tracker <https://bugs.python.org/issue44637> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset 01331f1a3cf86fd308e9a134bb867bf01fb191f5 by Julien Palard in branch 'main': bpo-42238: rstlint: Add two new checks. (GH-26966) https://github.com/python/cpython/commit/01331f1a3cf86fd308e9a134bb867bf01fb191f5 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +25530 pull_request: https://github.com/python/cpython/pull/26966 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: Another true positive: ... versionchanged:: 3.11 from : 6cb145d23f5cf69b6d7414877d142747cd3d134c / https://github.com/python/cpython/pull/26820 I also think it can be implemented in rstlint. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44470] 3.11 docs.python.org in Polish not English?
Julien Palard added the comment: > My computer is only configured for English. Running Firefox 90.0b9 (64-bit) > on macOS 11.4 (20F71). To add to this, it had nothing to do with your setup, the file was just lying here on the server due to the previous build happening on the same hierarchy. That's why adding a git clean fixed it. Next time you find a similar issue you can easily test if it's dependent on your setup or not by trying a curl in command-line: $ curl https://docs.python.org/3.11/library/parser.html curl sends very simple requests, without looking at your locale preferences, like: GET /3.11/library/parser.html HTTP/1.1 Host: docs.python.org User-Agent: curl/7.74.0 Accept: */* so it permit to easily disambiguate if it's tied to your browser or not. -- ___ Python tracker <https://bugs.python.org/issue44470> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44470] 3.11 docs.python.org in Polish not English?
Julien Palard added the comment: Thanks all for reporting and following on the issue. The fix on docsbuild script worked as expected and the page now 404 as expected as it does no logner exists in 3.11: https://docs.python.org/3.11/library/parser.html -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue44470> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: The previous one could probably be implemented in rstlint using (an equivalent of): git grep ':[a-z]\+:``[^:` ]+``' Doc/ Maybe specialized to known roles, like the script specializes to known directives. -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: Spotted a true positive in b19f45533942e4ad7ddf9d2d94f8b87c6f746bce: :const:``None`` (I'm trying to build a true positive list, to have usefull cases where suspicious is usefull, so in the long term I can maybe implement those cases in rslint instead.) -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44470] 3.11 docs.python.org in Polish not English?
Julien Palard added the comment: I added a git clean in docsbuild scripts to switch from one version to another: https://github.com/python/docsbuild-scripts/commit/1397a8dbe4c73744757ad24764baeb393842f30b It should be enough to correctly start fresh from one lang to another and from one version to another. Let's check next time the cron runs (daily) if it's fixed. -- ___ Python tracker <https://bugs.python.org/issue44470> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44470] 3.11 docs.python.org in Polish not English?
Julien Palard added the comment: Hi all! Thanks for reporting! I'm taking a look at it. -- assignee: docs@python -> mdk ___ Python tracker <https://bugs.python.org/issue44470> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: New changeset 227a09325e7bf82ecd303b4696c054a086b29a00 by Julien Palard in branch 'main': bpo-42238: Doc CI: Disable suspicious checks. (GH-26575) https://github.com/python/cpython/commit/227a09325e7bf82ecd303b4696c054a086b29a00 -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Change by Julien Palard : -- pull_requests: +25163 pull_request: https://github.com/python/cpython/pull/26575 ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43504] Site linked in docs, effbot.org, down
Change by Julien Palard : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43504> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43504] Site linked in docs, effbot.org, down
Change by Julien Palard : -- keywords: +easy, newcomer friendly ___ Python tracker <https://bugs.python.org/issue43504> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44006] symbol documentation still exists
Julien Palard added the comment: I `rm -fr 3.10` on the doc server yesterday, so it started 3.10 from scratch today and the file were properly removed. -- ___ Python tracker <https://bugs.python.org/issue44006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44006] symbol documentation still exists
Julien Palard added the comment: After the cron passed, and after purging the HTTP cache, it now 404: $ curl https://docs.python.org/3.10/library/symbol.html 404 Not Found Thanks for noticing! -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue44006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44006] symbol documentation still exists
Julien Palard added the comment: This is interesting! Also notice the footer: Last updated on Jul 26, 2020. I checked on the docsbuild server and found the `symbol.html` file was marked as modified today (probably by the build cron) (and it contains the "Last updated on Jul 26, 2020" string, yes). I think the explanation may be that Sphinx does not remove a file from the html output when it's rst counterpart is removed (which may be legitimate, Sphinx can't guess the rst was there before, so it can't distinguish if it's a human generated file that should be kept, or an old file to delete). There's however no links pointing to it (apart when switching version from 3.9 to 3.10 using the version switcher). I'm removing the files manually as is: docsbuild@docs:/srv/docsbuild/3.10$ rm cpython-*/Doc/build/html/library/symbol.html I'll let the daily cron update docs.python.org (to ensure it does the job). -- ___ Python tracker <https://bugs.python.org/issue44006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43971] documentation: no spacing around default args in annotated function
Julien Palard added the comment: Thanks Mohamed for the issue and Terry for fixing it. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43971> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43922] Double dots in quopri transported emails
Julien Castiaux added the comment: Fix deployed in the third party -- resolution: -> third party stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43922> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43954] Possible missing word on unittest doc
Julien Palard added the comment: As far as this issue is concerned, it's fixed. The discussion about this feature not working can continue in the appropriate issue (23882) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43954] Possible missing word on unittest doc
Julien Palard added the comment: New changeset 2abbd8f2add5e80b86a965625b9a77ae94a101cd by Zackery Spytz in branch 'master': bpo-43954: Fix a missing word in the unittest docs (GH-25672) https://github.com/python/cpython/commit/2abbd8f2add5e80b86a965625b9a77ae94a101cd -- ___ Python tracker <https://bugs.python.org/issue43954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43922] Double dots in quopri transported emails
Julien Castiaux added the comment: Hello David, The third party smtp software that causes troubles have been identified ! We are still investigating how to fix the problem at its root, ultimately this "fix" would not even be necessary. I'll keep you informed, just don't review or close the PR yet. Regards, -- ___ Python tracker <https://bugs.python.org/issue43922> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43954] Possible missing word on unittest doc
Julien Palard added the comment: > I propose to remove the namespace package support entirely. I'm no unittest expert, but I have nothing against removing it. I totally agree to at least remove it from the doc while it does not work. -- ___ Python tracker <https://bugs.python.org/issue43954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42238] Deprecate suspicious.py?
Julien Palard added the comment: I should have monitored this more closely, I started monitoring it weekly, then life got over until today when I'm even surprised to see activity on the issue, sry! (Surprise leading me to investigate why I had not received notifications from bpo, leading me to a bug in my sieve filter...) I counted, during your releases `make suspicious` spotted: - 1 true positive in 20ac34772aa9805ccbf082e700f2b033291ff5d2 - 1 false positive in 20ac34772aa9805ccbf082e700f2b033291ff5d2 - 1 true positive in 57f21db3f629649dbd7c4531078b6a2104896411 - 1 false positive in de833b601319da15d90c8f3cd3c44d239d6d5924 if I missed none, the success ratio is not good (which is already known). What I'm aiming to do in this issue is to list the true positives over time, by passing the tool manually from time to time, to try to see what kind of rule is usefull in such a tool, and ultimately try to spot those errors in a reliable way. I'd go for removing it from both release process and the CI, this would lower pressure on RMs and contributors, while easing the study of the tool in this issue. I even consider removing it from the Makefile / tools hierarchy to ensure nobody runs it, because if someone run it locally during its contribution process it may hide true positives from me (leading me to think there's no true positives and the tool is useless). -- ___ Python tracker <https://bugs.python.org/issue42238> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43954] Possible missing word on unittest doc
New submission from Julien Palard : In https://docs.python.org/3/library/unittest.html I see: > Note that you need to the top level directory too. Trying to guess, the missing word may be "specify": > Changed in version 3.4: Test discovery supports namespace packages for start > directory. Note that you need to specify the top level directory too. (e.g. > python -m unittest discover -s root/namespace -t root). Am I right? -- assignee: docs@python components: Documentation messages: 392060 nosy: docs@python, mdk, methane priority: normal severity: normal status: open title: Possible missing word on unittest doc versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue43954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43922] Double dots in quopri transported emails
Julien Castiaux added the comment: Hello David, thank you for your quick answer. I tried to keep it minimal with some unittests. Could you point me some resources to learn how to properly write a custom content manager ? -- ___ Python tracker <https://bugs.python.org/issue43922> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43922] Double dots in quopri transported emails
Change by Julien Castiaux : -- keywords: +patch pull_requests: +24281 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25562 ___ Python tracker <https://bugs.python.org/issue43922> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43922] Double dots in quopri transported emails
New submission from Julien Castiaux :
Hello,
We received multiple bug reports about broken links in rich html emails.
Sometime, in some emails, a link like https://example.com";> would
become https://example..com>, notice the double dot.
After multiple researches both in the Python email source code and in the RFC,
it turns out that Python correctly implements the standard but that the distant
(non-python) smtp server used by some of our customers doesn't.
The various email standard state the following:
1) As a single dot (".", chr(0x2e)) in a line ends the SMTP transmission, such
single dots must be escaped when they are part of the message. RFC 5321,
section 4.5.2 requires to escape all dots when they appear at the beginning of
a line, using a dot as escape symbol. That is, when the user message contains:
"\r\n.\r\n", it is escaped to "\r\n..\r\n". The other smtp side is responsible
to remove the extra dot.
2) When we transport the email body using the quoted-printable encoding, RFC
2045 requires each line to have maximum 78 characters and define a single equal
("=", chr(0x3d)) as soft-warp sequence to fold lines too long. The RFC does
only require to split the line outside of a quoted character (cannot split in
the middle of "=2E"). Like any other character, it is allowed to split the line
before a dot.
Take the following example:
from email.message import EmailMessage
from email.policy import SMTP
msg = EmailMessage(policy=SMTP)
msg.set_context("Hello there, just need some text to reach that seventy-six
character, example.com")
#
^
#
78th char
print(msg.as_string())
# Content-Type: text/plain; charset="utf-8"
# Content-Transfer-Encoding: quoted-printable
# MIME-Version: 1.0
#
# Hello there, just need some text to reach that seventy-six character,
example=
# .com
When the message is sent over smtp, smtplib escapes the line ".com" to become
"..com" as required by the RFC. So no problem in the python implementation, it
is the other side that is buggy.
But! We have two solutions to "fix" the other side, the problem is that they do
not correctly parse lines starting with a dot. A solution would be to ensure no
line starts with the dot character. Two solutions : (1) quoted-printable encode
dots when they are at the beginning of a line, (2) prevent the line folding
code from splitting a line before a dot.
(1) is allowed by the RFC, any character can be quoted-printable encoded even
those that have a safe ascii representation already. In our "example=\n.com"
example above, we can qp the code: "example=\n=2Ecom". The line starts with a
"2" instead of a dot and the content is the same.
(2) is allowed by the RFC, the RFC only states that a line must be at most 78
chars long, it also states it is allowed to fold a line anywhere but in a
quoted-printable sequence. It is safe to split a line earlier than the 78th
character. In our "example=\n.com" example above, we could split the line at
the 77th character: "exampl=\ne.com". The line starts with a "e" instead of a
dot and the content is the same.
A pull request is coming shortly.
--
components: email
messages: 391698
nosy: Julien Castiaux, barry, r.david.murray
priority: normal
severity: normal
status: open
title: Double dots in quopri transported emails
type: enhancement
versions: Python 3.11
___
Python tracker
<https://bugs.python.org/issue43922>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43330] xmlrpc.Server URI query and fragment are discarded from HTTP query since py3
Julien Castiaux added the comment: Duplicate of 43433 -- message_count: 1.0 -> 2.0 pull_requests: +23871 resolution: -> duplicate status: open -> closed pull_request: https://github.com/python/cpython/pull/25057 ___ Python tracker <https://bugs.python.org/issue43330> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43570] pyspecific.py > AuditEvent mess with translations
Change by Julien Palard : -- keywords: +patch pull_requests: +23704 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24945 ___ Python tracker <https://bugs.python.org/issue43570> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43570] pyspecific.py > AuditEvent mess with translations
New submission from Julien Palard : In case an `.. audit-event::` has a content, Sphinx gets confused: It will provide both "auto-generated" and the content in po files, for interactivehook for example we have: #: library/sys.rst:953 msgid "" "Raises an :ref:`auditing event ` ``cpython.run_interactivehook`` " "with argument ``hook``." msgstr "" #: library/sys.rst:955 msgid "" "Raises an :ref:`auditing event ` ``cpython.run_interactivehook`` " "with the hook object as the argument when the hook is called on startup." msgstr "" "Lève un :ref:`évènement d'audit ` ``cpython.run_interactivehook`` " "avec l'objet de point d'entrée comme argument lorsqu'il est appelé au " "démarrage." Which is not needed as only the content is used to render the doc, but it's the least issue. The issue is that Sphinx will then check the used one (content) against the translation of the auto-generated one leading it to trigger a warning on case the :ref: used don't match, typically for: .. audit-event:: sys.unraisablehook hook,unraisable sys.unraisablehook Raise an auditing event ``sys.unraisablehook`` with arguments ``hook``, ``unraisable`` when an exception that cannot be handled occurs. The ``unraisable`` object is the same as what will be passed to the hook. If no hook has been set, ``hook`` may be ``None``. Sphinx will compare the auto-generated one: Raises an :ref:`auditing event ` ``sys.unraisablehook`` with arguments ``hook``, ``unraisable``. Against our translated one (Lève un évènement d'audit ...). Issue is, as in "Raise an auditing event" there's no :ref:, but as we translated "Raises an :ref:`auditing event `" we used one, Sphinx whines about inconsistent term references. As far as I understand it, it's related, or near, the: if self.content: self.state.nested_parse(self.content, self.content_offset, pnode) else: n, m = self.state.inline_text(text, self.lineno) pnode.extend(n + m) part of pyspecific.py. -- assignee: docs@python components: Documentation messages: 389169 nosy: docs@python, mdk, steve.dower priority: normal severity: normal status: open title: pyspecific.py > AuditEvent mess with translations versions: Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue43570> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
