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
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/issu
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
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
Change by Hugo van Kemenade :
--
pull_requests: +30234
pull_request: https://github.com/python/cpython/pull/32153
___
Python tracker
<https://bugs.python.org/issue47
Change by Hugo van Kemenade :
--
pull_requests: +30235
pull_request: https://github.com/python/cpython/pull/32154
___
Python tracker
<https://bugs.python.org/issue47
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
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
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
Hugo van Kemenade added the comment:
Here's a devguide PR: https://github.com/python/devguide/pull/822
--
___
Python tracker
<https://bugs.python.org/issue47
Change by Hugo van Kemenade :
--
assignee: hugovk ->
___
Python tracker
<https://bugs.python.org/issue47126>
___
___
Python-bugs-list mailing list
Unsubscrib
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/issu
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
Change by Hugo van Kemenade :
--
pull_requests: +30169
pull_request: https://github.com/python/cpython/pull/32082
___
Python tracker
<https://bugs.python.org/issue47
Change by Hugo van Kemenade :
--
nosy: +hugovk
___
Python tracker
<https://bugs.python.org/issue47061>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Hugo van Kemenade :
--
pull_requests: +30087
pull_request: https://github.com/python/cpython/pull/31998
___
Python tracker
<https://bugs.python.org/issue47
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/issu
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 t
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/issu
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/issu
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 depre
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):
Change by Hugo van Kemenade :
--
pull_requests: +29268
pull_request: https://github.com/python/cpython/pull/31084
___
Python tracker
<https://bugs.python.org/issue45
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/issue45
Change by Hugo van Kemenade :
--
pull_requests: -29106
___
Python tracker
<https://bugs.python.org/issue45173>
___
___
Python-bugs-list mailing list
Unsub
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/issu
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
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/issu
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
Change by Hugo van Kemenade :
--
pull_requests: +29106
pull_request: https://github.com/python/cpython/pull/30927
___
Python tracker
<https://bugs.python.org/issue45
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
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
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
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":
--- proto
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.g
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/i
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/i
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.p
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/i
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.p
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.p
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 patche
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.p
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
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/issu
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/issu
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/issue46
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
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/issue45
Change by Hugo van Kemenade :
--
pull_requests: +28046
pull_request: https://github.com/python/cpython/pull/29813
___
Python tracker
<https://bugs.python.org/issue45
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/issu
Change by Hugo van Kemenade :
--
pull_requests: +27862
pull_request: https://github.com/python/cpython/pull/29630
___
Python tracker
<https://bugs.python.org/issue45
Change by Hugo van Kemenade :
--
pull_requests: +27861
pull_request: https://github.com/python/cpython/pull/29629
___
Python tracker
<https://bugs.python.org/issue45
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/issu
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 i
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
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/issu
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/issu
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/issu
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
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/issu
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=1
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/issu
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
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/issu
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
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/issu
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
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
<ht
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/issu
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
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
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/issue24
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/issu
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
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/issue43
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
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/issu
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
Change by Hugo van Kemenade :
--
nosy: +hugovk
___
Python tracker
<https://bugs.python.org/issue41282>
___
___
Python-bugs-list mailing list
Unsubscribe:
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/issue24
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
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/issue41
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
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&quo
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/issu
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 i
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
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
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
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
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
Hugo Osvaldo Barrera added the comment:
The problem is that the datetime/strftime documentation describes "%c" as:
Locale’s appropriate date and time representation.
However, this is not really accurate (this is not the *default* behaviour),
that's why I was mentioning the cla
Hugo Osvaldo Barrera added the comment:
It would seem that
locale.setlocale(locale.LC_TIME, "")
fixes the issue. However, there seems to be no mention on this on the relevant
documentation page[1], which is actually the source of my confusion.
As a "fix" to this issue
New submission from Hugo Osvaldo Barrera:
As the the posix spec for strftime:
%c The preferred date and time representation for the current locale.
%x The preferred date representation for the current locale without the time.
However, python doesn't seem to respect this:
$ python3.5 -c
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
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
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
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__
Hugo Lopes Tavares added the comment:
I just caught a bug because on Python 3 `HTTPMessage` has `get_param`, while on
Python 2 there is `getparam`, with a different method signature. I am trying to
figure out a solution so my code can run in both python 2 and 3 without ifs on
python version
1 - 100 of 113 matches
Mail list logo
