Change by Mark Dickinson :
--
nosy: -mark.dickinson
___
Python tracker
<https://bugs.python.org/issue44470>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Mark Shannon :
We are making lots of changes to the code object.
We should clearly document all the changes in one place and explain the new
design well before 3.11 beta.
--
assignee: docs@python
components: Documentation
messages: 396432
nosy: Mark.Shannon, docs
Change by Mark Shannon :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Shannon added the comment:
Thanks for the reproducer.
--
assignee: -> Mark.Shannon
___
Python tracker
<https://bugs.python.org/issue44297>
___
___
Py
Mark Dickinson added the comment:
Thanks! Closing.
--
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue44426>
___
___
Python-bugs-lis
Mark Shannon added the comment:
New changeset c3f52b4d707a78eb342372a2be00f3eb846a05b9 by Mark Shannon in
branch 'main':
bpo-44486: Make sure that modules always have a dictionary. (GH-26847)
https://github.com/python/cpython/commit/c3f52b4d707a78eb342372a2be00f3eb846a05b9
Mark Dickinson added the comment:
I'd suggest reporting this on the kivy bug tracker: https://github.com/kivy/kivy
This tracker is for the Python core language, and this doesn't look like a
problem caused by a bug in Python.
--
nosy: +mark.dickinson
resolution: -> third party
st
Change by Mark Shannon :
--
keywords: +patch
pull_requests: +25428
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26847
___
Python tracker
<https://bugs.python.org/issu
New submission from Mark Shannon :
It is possible to create a module without a dictionary:
m = types.ModuleType.__new__(types.ModuleType)
But that is the only way to create to a module without a dict; all other means
of creating a module, both in Python and in the C API, result in a fully
Mark Dickinson added the comment:
> Perhaps we should just borrow from the documentation for the power operator,
> which says [...]
That sounds good to me.
--
___
Python tracker
<https://bugs.python.org/i
Mark Dickinson added the comment:
The bug here is that https://docs.python.org/3.11/library/parser.html is
visible at all, given that the parser module no longer exists in 3.10 or 3.11.
@Samuel: Do you see this on any other documentation nodes, or just on
parser.html? I can reproduce
Mark Shannon added the comment:
Hmm, I'm a bit puzzled by that.
Did you test with 3.10b3 or the latest build from the 3.10 branch with the fix
to https://bugs.python.org/issue44297 included?
--
___
Python tracker
<https://bugs.python.
Mark Shannon added the comment:
With the latest 3.10, I get:
File "/home/mark/test/test.py", line 13, in
next(bar().__await__(), None)
File "/home/mark/test/test.py", line 10, in bar
return [chunk async for chunk in foo()]
File "/home/mark/test/test.py&
Mark Shannon added the comment:
This appears to be a duplicate of https://bugs.python.org/issue44297
--
___
Python tracker
<https://bugs.python.org/issue44
Mark Shannon added the comment:
New changeset fb68791a26e157ed3cdeb409c8d8b6cddc7535bd by Mark Shannon in
branch 'main':
bpo-44337: Improve LOAD_ATTR specialization (GH-26759)
https://github.com/python/cpython/commit/fb68791a26e157ed3cdeb409c8d8b6cddc7535bd
Mark Shannon added the comment:
New changeset 7674c83d81905d6afe989ca3f93f08b7939b057c by Mark Shannon in
branch '3.10':
bpo-44297: Fix missing line number in generator expressions (GH-26821)
https://github.com/python/cpython/commit/7674c83d81905d6afe989ca3f93f08b7939b057c
Mark Shannon added the comment:
I think this is a combination of https://bugs.python.org/issue44297 and the
PREDICT macros.
I don't have a windows machine to confirm this on, but I suspect that if you
rewrite `doit` as:
def doit():
o = ((1,2), (3,4))
o
Change by Mark Shannon :
--
pull_requests: +25402
pull_request: https://github.com/python/cpython/pull/26821
___
Python tracker
<https://bugs.python.org/issue44
Mark Shannon added the comment:
New changeset 82e5c28af7049c4f5343c808f172cbe2e145f49b by Mark Shannon in
branch 'main':
bpo-44297: Fix missing line number in generator expressions (GH-26801)
https://github.com/python/cpython/commit/82e5c28af7049c4f5343c808f172cbe2e145f49b
Mark Dickinson added the comment:
I think this should be good now.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> pending
___
Python tracker
<https://bugs.python.or
Mark Dickinson added the comment:
New changeset 533bff4e9fe221a7c9cf12795fd2d002e87bfa6a by Miss Islington (bot)
in branch '3.9':
bpo-44426: Fix use of the C keyword 'default' as a variable name (GH-26798)
(GH-26805)
https://github.com/python/cpython/commit
Mark Dickinson added the comment:
New changeset 139c5778c26aaf25b51fcfabd88c99ba728beaea by Miss Islington (bot)
in branch '3.10':
bpo-44426: Fix use of the C keyword 'default' as a variable name (GH-26798)
(GH-26804)
https://github.com/python/cpython/commit
Mark Dickinson added the comment:
New changeset 291848195f85e23c01adb76d5a0ff9c6eb7f2614 by Mark Dickinson in
branch 'main':
bpo-44426: Fix use of the C keyword 'default' as a variable name (GH-26798)
https://github.com/python/cpython/commit/291848195f85e23c01adb76d5a0ff9c6eb7f2614
Change by Mark Shannon :
--
keywords: +patch
pull_requests: +25382
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26801
___
Python tracker
<https://bugs.python.org/issu
Mark Shannon added the comment:
Thanks Anthony, that's a big help.
--
___
Python tracker
<https://bugs.python.org/issue44297>
___
___
Python-bugs-list mailin
Mark Shannon added the comment:
Ned, is this a regression (does 3.9 do the right thing on Windows) or an
inconsistency between Mac and Windows?
I suspect this might have something to do with the PREDICT macros. If that the
were the case 3.9 should show the same inconsistency between Windows
Change by Mark Dickinson :
--
assignee: mark.dickinson ->
___
Python tracker
<https://bugs.python.org/issue29282>
___
___
Python-bugs-list mailing list
Un
Mark Dickinson added the comment:
Eric: any thoughts on this?
It's looking like a "won't fix" to me. Regardless of what we think the "right"
thing to do is, making the float behaviour stricter would be a backwards
compatibility break, and relaxing the Decimal behav
Mark Dickinson added the comment:
Yes, this looks closeable. Thank you!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Dickinson added the comment:
Fixed in GH-26798 (not yet merged). With that change, the documentation builds
cleanly for me with Python 3.9.5 / Sphinx 4.0.2 / blurb 1.0.8 /
python-docs-theme 2021.5, using the command
$ python -m sphinx -b html -W . build/html
Change by Mark Dickinson :
--
pull_requests: +25379
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/26798
___
Python tracker
<https://bugs.python.org/issu
Change by Mark Dickinson :
--
assignee: docs@python -> mark.dickinson
___
Python tracker
<https://bugs.python.org/issue44426>
___
___
Python-bugs-list mai
Mark Shannon added the comment:
New changeset 0982ded179f280176868c1c4eccf77bf70687816 by Mark Shannon in
branch 'main':
bpo-44032: Move pointer to code object from frame-object to frame specials
array. (GH-26771)
https://github.com/python/cpython/commit
Mark Dickinson added the comment:
Thanks; this looks like an easy fix, then. No time right now, but I'll aim to
get to it at some point before the end of the weekend, if no-one beats me to it.
--
___
Python tracker
<https://bugs.python.
Change by Mark Shannon :
--
pull_requests: +25357
pull_request: https://github.com/python/cpython/pull/26771
___
Python tracker
<https://bugs.python.org/issue44
Mark Shannon added the comment:
No problem, I've added a simple test.
--
stage: patch review ->
___
Python tracker
<https://bugs.python.org/issue2>
___
_
Change by Mark Shannon :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue2>
___
Change by Mark Shannon :
--
keywords: +patch
pull_requests: +25355
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26768
___
Python tracker
<https://bugs.python.org/issu
New submission from Mark Shannon :
When calling frame.clear(), the globals (and builtins) are cleared.
This is not the case in 3.10. We should restore the 3.10 behavior, as there is
no reason not to.
Victor, you've mentioned this problem. Did you have a specific example I can
add as a test
Change by Mark Shannon :
--
assignee: Mark.Shannon -> eric.snow
___
Python tracker
<https://bugs.python.org/issue43693>
___
___
Python-bugs-list mai
Mark Dickinson added the comment:
Thanks. That one's a genuine keyword. Looks like what we probably need to do is
get a list of all these errors, so that they can all be fixed at once.
Presumably running without the "-W" flag would make t
Mark Dickinson added the comment:
> and we can certainly change it
Done. Closing here, but I've opened a Sphinx issue at
https://github.com/sphinx-doc/sphinx/issues/9354
--
nosy: -miss-islington
resolution: -> fixed
stage: patch review -> resolved
status: open -> clo
Mark Dickinson added the comment:
New changeset c689e0a7e2a25621da82f22cc64d089eae05e753 by Miss Islington (bot)
in branch '3.10':
bpo-44426: Use of 'complex' as a C variable name confuses Sphinx; change it to
'num'. (GH-26744) (GH-26760)
https://github.com/python/cpython/commit
Mark Dickinson added the comment:
New changeset 686c6f303a6e9e54b50401be0ae3dc6aa2fcf05a by Miss Islington (bot)
in branch '3.9':
bpo-44426: Use of 'complex' as a C variable name confuses Sphinx; change it to
'num'. (GH-26744) (GH-26761)
https://github.com/python/cpython/commit
Mark Dickinson added the comment:
New changeset 7247f6f433846c6e37308a550e8e5eb6be379856 by Mark Dickinson in
branch 'main':
bpo-44426: Use of 'complex' as a C variable name confuses Sphinx; change it to
'num'. (GH-26744)
https://github.com/python/cpython/commit
Change by Mark Shannon :
--
pull_requests: +25344
pull_request: https://github.com/python/cpython/pull/26759
___
Python tracker
<https://bugs.python.org/issue44
Mark Shannon added the comment:
New changeset ab030d6f9d73e7f6c2213c2e308d1ceb04761485 by Sergey Fedoseev in
branch 'main':
bpo-38211: Clean up type_init() (GH-16257)
https://github.com/python/cpython/commit/ab030d6f9d73e7f6c2213c2e308d1ceb04761485
--
nosy: +Mark.Shannon
Change by Mark Dickinson :
--
assignee: -> mark.dickinson
___
Python tracker
<https://bugs.python.org/issue44357>
___
___
Python-bugs-list mailing list
Un
Mark Dickinson added the comment:
I think this can be closed now.
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Mark Dickinson added the comment:
New changeset 8d0b2ca493e236fcad8709a622c1ac8ad29c372d by Mark Dickinson in
branch '3.10':
[3.10] bpo-43475: Add what's new entry for NaN hash changes (GH-26725)
(GH-26743)
https://github.com/python/cpython/commit/8d0b2ca493e236fcad8709a622c1ac8ad29c372d
Change by Mark Dickinson :
--
keywords: +patch
pull_requests: +25329
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26744
___
Python tracker
<https://bugs.python.org/issu
Change by Mark Dickinson :
--
pull_requests: +25328
pull_request: https://github.com/python/cpython/pull/26743
___
Python tracker
<https://bugs.python.org/issue43
Mark Dickinson added the comment:
New changeset 1d10bf0bb9409a406c56b0de8870df998637fd0f by Mark Dickinson in
branch 'main':
bpo-43475: Add what's new entry for NaN hash changes (GH-26725)
https://github.com/python/cpython/commit/1d10bf0bb9409a406c56b0de8870df998637fd0f
Mark Dickinson added the comment:
As a test, gcc and clang both seem happy to treat this as valid C. I think
Sphinx is wrong to reject this.
mdickinson@mirzakhani Desktop % cat test.c
typedef struct {
double real;
double imag;
} Py_complex;
Py_complex _Py_c_neg(Py_complex complex
Mark Dickinson added the comment:
Hmm. It's probably not the best name, and we can certainly change it.
But I'm a bit confused by the error message: `complex` isn't a keyword in
either C or C++, so I'm not sure why Sphinx thinks it is.
--
nosy: +mark.dickinson
New submission from Mark Final :
Hi,
We build Python 3.7 from source in-house for Windows, Linux and macOSX.
It's been noticed that 'dirty' has been appended to sys.version in our builds,
even though the source tree has not been modified from a git clone. This only
happens for Linux
Change by Mark Dickinson :
--
pull_requests: +25315
pull_request: https://github.com/python/cpython/pull/26725
___
Python tracker
<https://bugs.python.org/issue43
Mark Shannon added the comment:
This is going in the wrong direction.
Rather than add more complex instructions for use only by pattern matching, we
need to simplify the individual operations and re-use existing instructions.
That way pattern matching can benefit from the general performance
Mark Shannon added the comment:
What does "seem wrong" mean?
What exactly is the problem?
--
___
Python tracker
<https://bugs.python.org/issue44417>
___
__
Change by Mark Shannon :
--
pull_requests: +25306
pull_request: https://github.com/python/cpython/pull/26718
___
Python tracker
<https://bugs.python.org/issue44
Mark Shannon added the comment:
New changeset eecbc7c3900a7f40d8498b151db543a202c72f74 by Mark Shannon in
branch 'main':
bpo-44338: Port LOAD_GLOBAL to PEP 659 adaptive interpreter (GH-26638)
https://github.com/python/cpython/commit/eecbc7c3900a7f40d8498b151db543a202c72f74
Mark Dickinson added the comment:
> Does this change need to be mentioned in What's New?
Yes, I think so, given that it's a change to documented behavior. It's also
something that third party packages (like NumPy) potentially need to be aw
Mark Dickinson added the comment:
@Serhiy: can this be closed again? Does GH-26679 need to be backported to the
3.10 branch?
--
___
Python tracker
<https://bugs.python.org/issue43
Mark Dickinson added the comment:
@realead
> This change makes life harder for people trying to get sane behavior with
> sets [...]
Yes, code that assumes that all NaNs have the same hash value will need to
change. But that doesn't seem unreasonable for objects that are already
cons
Change by Mark Dickinson :
--
pull_requests: +25287
pull_request: https://github.com/python/cpython/pull/26703
___
Python tracker
<https://bugs.python.org/issue36
Change by Mark Dickinson :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Dickinson added the comment:
New changeset 4a42cebf6dd769e2fa4e234a9e91093b3ad1cb63 by Mark Dickinson in
branch 'main':
bpo-44339: Fix math.pow corner case to comply with IEEE 754 (GH-26606)
https://github.com/python/cpython/commit/4a42cebf6dd769e2fa4e234a9e91093b3ad1cb63
Change by Mark Dickinson :
--
nosy: +mark.dickinson
___
Python tracker
<https://bugs.python.org/issue44400>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Mark Dickinson :
--
pull_requests: +25277
pull_request: https://github.com/python/cpython/pull/26690
___
Python tracker
<https://bugs.python.org/issue36
Mark Dickinson added the comment:
> That is, do we want NaNs to sort to the beginning of the list, or the end?
FWIW, NumPy chooses to sort NaNs to the end of the list:
https://numpy.org/doc/stable/reference/generated/numpy.sort.html
--
___
Pyt
Mark Dickinson added the comment:
> We should consider biting the bullet and revising the default NaN sort order.
If we went that route, I think we wouldn't need to consider payload or
identity. We could just do:
NaN < NaN -> False
NaN < non-NaN -> T
Change by Mark Gordon :
--
keywords: +patch
nosy: +msg555
nosy_count: 3.0 -> 4.0
pull_requests: +25251
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26664
___
Python tracker
<https://bugs.python.org/i
Mark Dickinson added the comment:
> 2921 is the smallest integers for which math.sqrt(x) > x**0.5
This is platform-dependent. On my machine, for example, `math.sqrt(2921) ==
2921**0.5` returns `True`.
I don't see a lot of value in additional tests here; we're only wrapping the
lib
Mark Dickinson added the comment:
I can't reproduce this on my Mac laptop (using Python builds from MacPorts).
Numbers for both x**2 and x*x are fairly stable across Python 3.2 to Python
3.10. There's some variation, but nothing close to the same extent that Steven
is seeing.
Here are my
Mark Dickinson added the comment:
All done; closing. Thank you for the contribution!
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Mark Dickinson added the comment:
New changeset ac867f10b49322e25f34d2d8abd8e63c86834750 by Ajith Ramachandran in
branch 'main':
bpo-44357:Add `math.cbrt()` function: Cube Root (GH-26622)
https://github.com/python/cpython/commit/ac867f10b49322e25f34d2d8abd8e63c86834750
Change by Mark Dickinson :
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue44364>
___
___
Pyth
New submission from Mark Dickinson :
New changeset 90cd4330329a99e52f7141db5e0a469d30088e66 by Ajith Ramachandran in
branch 'main':
bpo-44364:Add non integral tests for `sqrt()` (#26625)
https://github.com/python/cpython/commit/90cd4330329a99e52f7141db5e0a469d30088e66
Change by Mark Shannon :
--
pull_requests: +25226
pull_request: https://github.com/python/cpython/pull/26639
___
Python tracker
<https://bugs.python.org/issue44
Change by Mark Shannon :
--
keywords: +patch
pull_requests: +25225
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26638
___
Python tracker
<https://bugs.python.org/issu
Change by Mark Shannon :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Shannon added the comment:
Yes. Simpler is good.
I think it will also be better for performance:
In general, we don't know what X is in `from Y import X`. It could be a module
or anything else.
However, if we are accessing an attribute it is quite likely to be a module or
class
Mark Shannon added the comment:
It looks like I've been a bit unfair to the address sanitizer.
It does appear to produce incorrect locations sometimes, but that's not really
a false positive and the reports are generally useful.
--
___
Python
Mark Shannon added the comment:
New changeset 54cb63863f19a7c64d9a3a5fd97bdfc0dd7ab374 by Mark Shannon in
branch 'main':
bpo-44348: Move trace-info to thread-state (GH-26623)
https://github.com/python/cpython/commit/54cb63863f19a7c64d9a3a5fd97bdfc0dd7ab374
Mark Shannon added the comment:
New changeset e117c0283705943189e6b1aef668a1f68f3f00a4 by Mark Shannon in
branch 'main':
bpo-44337: Port LOAD_ATTR to PEP 659 adaptive interpreter (GH-26595)
https://github.com/python/cpython/commit/e117c0283705943189e6b1aef668a1f68f3f00a4
Mark Dickinson added the comment:
See also #11986, which this report is essentially a duplicate of.
I think it may be time to implement `math.ieee754_total_order` (after suitable
bikeshedding about the name), so that one can do
sorted(my_list_of_floats, key=math.ieee754_total_order
Mark Shannon added the comment:
No, this is done
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Shannon added the comment:
This line seems to be responsible for most of the failures:
https://github.com/python/cpython/blob/main/Objects/frameobject.c#L985
Which does appear to be a true positive.
--
___
Python tracker
<ht
Mark Shannon added the comment:
What commit are you running that on?
--
___
Python tracker
<https://bugs.python.org/issue44363>
___
___
Python-bugs-list mailin
Change by Mark Dickinson :
--
nosy: +mark.dickinson
___
Python tracker
<https://bugs.python.org/issue44364>
___
___
Python-bugs-list mailing list
Unsubscribe:
Mark Dickinson added the comment:
If we *really* wanted to bikeshed on the name, back in 1991 Kahan wrote:
> Perhaps the last problem is the hardest: choosing the program's name. Ideally
> it should need no explanation, but a limitation upon its length may preclude
> that. Altho
Mark Shannon added the comment:
I still get quite a few failures on the main branch.
It seems like ceval.c:1600 upsets the sanitizer, at least for gcc.
There isn't anything wrong with that line, but as I plan to change it anyway I
guess it doesn't matter:
https://github.com/python/cpython
Change by Mark Shannon :
--
pull_requests: +25209
pull_request: https://github.com/python/cpython/pull/26624
___
Python tracker
<https://bugs.python.org/issue44
Mark Dickinson added the comment:
@Victor: Yep, the name is pretty standard. Not just C, but JavaScript, Java, R,
and likely a lot of other languages that I haven't checked.
--
___
Python tracker
<https://bugs.python.org/issue44
Change by Mark Shannon :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Mark Dickinson added the comment:
There's also a decent chance that a libm implementation of cbrt will be
correctly rounded, while `x**(1/3)` is highly unlikely to be so.
--
___
Python tracker
<https://bugs.python.org/issue44
Mark Dickinson added the comment:
> Perhaps because it is so easy to write x**(1/3), and if you want a real root
> of negative argument, it is -(-x)**(1/3).
I consider `x**(1/3)` to be a trap and a bug magnet: many people won't realise
that the correct spelling for their sit
Mark Shannon added the comment:
If I run the following on main
./configure --with-address-sanitizer
make clean
make -j12 test
I get 22 failures.
So something is broken.
test_lib2to3 does fork; at least it does when I run it under gdb
Change by Mark Shannon :
--
nosy: +Mark.Shannon
nosy_count: 9.0 -> 10.0
pull_requests: +25208
pull_request: https://github.com/python/cpython/pull/26623
___
Python tracker
<https://bugs.python.org/issu
New submission from Mark Shannon :
Running the buildbot for https://github.com/python/cpython/pull/26595
results in failures:
https://buildbot.python.org/all/#/builders/581/builds/63
Which claim that the address calculation in `LOAD_ATTR_MODULE` is out of bounds.
The tests pass with an added
901 - 1000 of 17965 matches
Mail list logo