Guido van Rossum added the comment:
For the record, I'm with Martin -- there are many existing uses that we
can't just legislate away.
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.
Guido van Rossum added the comment:
I don't see why the refactoring has to maintain the same logic bug as
the original. I'm with Skip & Jeffrey.
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.pyt
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue1696199>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
[Copy of a post I just made to python-dev]
I'm with Martin. In these days of distributed version control systems, I
would think that the effort for the Haiku folks to maintain a branch of
Python in their own version control would be minimal. It is l
Guido van Rossum added the comment:
I think this is my fault. I should have used the proper repr() of the
filename in the repr() of a file object from the beginning, then this
wouldn't have been a problem.
I think we should let this rest for Python 2.x (except for fixing the
test
New submission from Guido van Rossum :
I am attaching a file encoded in UTF-16 (with bom) which causes the
stream codec employed by the file reader to barf when reading by lines.
However reading the file in binary mode and decoding it in one fell
swoop works fine, and reading the whole text
Guido van Rossum added the comment:
Dang. Already fixed in trunk. (Is it fixed in 3.0.1 too?)
--
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Guido van Rossum added the comment:
@Gregory, that sounds like an odd enough use case to skip. However you
might want to look for __length_hint__ before giving up?
OTOH unless the use case is real, why not support it but making it slow?
___
Python tracker
Guido van Rossum added the comment:
I think it's fine if it returns an int iff the first arg is an int. In
other languages this would be overloaded as follows:
round(int)int
round(float)float
round(int, int)int
round(float, int)float
--
assignee: gvanr
Guido van Rossum added the comment:
Well, that would leave a function whose return *type* depends on the
*value* of one of the arguments, which I find very ugly.
I don't know why you think rounding an int to X (X>0) digits after the
decimal point should return a float -- it's not
Guido van Rossum added the comment:
I'm sorry, but I don't see a significant difference between $10 and
$10.00. If you want to display a certain number of digits, use "%.2f" %
x. And trust me, I'm not doing this for Fortran's sake.
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue2159>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
@gpsmith: Way to go!
@gpolo: Alas, test discovery is now a much harder problem because it
depends on using conventions for test naming. Unless all existing
implementations use the same conventions, it's hard to see how to
replace them. Please bring th
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue1835>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Beats me. I personally haven't had the pleasure to use either so I can't
decide. Maybe a vote or a bake-off?
___
Python tracker
<http://bugs.python.
Changes by Guido van Rossum :
___
Python tracker
<http://bugs.python.org/issue3871>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/o
Guido van Rossum added the comment:
I don't think a PEP is needed, and I do think ipaddr.py is ready for
inclusion. All that you really need is a core developer to champion the
inclusion.
___
Python tracker
<http://bugs.python.org/i
Guido van Rossum added the comment:
If changes to ipaddr could make things easier for netaddr's support of
advanced features, please do propose those changes!
___
Python tracker
<http://bugs.python.org/i
Guido van Rossum added the comment:
Playing tricks where compile-time and run-time see slightly different types is
probably more productive than trying to revert a PR that was in Python 3.9 and
3.10. :-)
I'm not opposed to supporting generic NamedTuple, but I expect the fix will
neve
Guido van Rossum added the comment:
This still hasn't been fixed. I suspect that a new patch should be produced and
uploaded as a PR. It looks pretty simple.
--
keywords: +easy
nosy: +gvanrossum
versions: +Python 3.10, Python 3.11, Python 3.7, Python 3.8, Pytho
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue46896>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
I don't think that `except A|B` looks better than `except (A, B)`, so I am
against this proposal. Exception matching is its own special thing (e.g. it
doesn't honor virtual subclasses) and we shouldn't h
Guido van Rossum added the comment:
New changeset f537b2a4fb86445ee3bd6ca7f10bc9d3a9f37da5 by Andrew Svetlov in
branch 'main':
bpo-46771: Implement asyncio context managers for handling timeouts (GH-31394)
https://github.com/python/cpython/commit/f537b2a4fb86445ee3bd6ca7f10bc9
Guido van Rossum added the comment:
I'm closing this, the asyncio.timeout() context manager has been merged. Thanks
Andrew!
@agronholm you said you were interested in tweaking the cancellation behavior
some more. If you're still interested, let's discuss that in a separa
Guido van Rossum added the comment:
Good think I forgot to close the issue. ;-)
--
___
Python tracker
<https://bugs.python.org/issue46771>
___
___
Python-bug
Guido van Rossum added the comment:
Alas, I have no idea. I don't even recall what copy_with() is for (it was
apparently introduced in 3.7). Possibly vopy_with() is wrong here? I imaging
some of this has to do with the special casing needed so that repr() of an
empty Tuple type do
Guido van Rossum added the comment:
I've recently dabbled a bit in some new primitives for asyncio, and based on
that experience I think this would be very useful.
IIRC Trio does this (presumably at considerable cost) in userland.
--
___
P
Guido van Rossum added the comment:
Before we land GH-31840 we should have a somewhat more public discussion (e.g.
on python-dev or maybe in Async-SIG, https://discuss.python.org/c/async-sig/20;
or at least here) about deprecating the cancel message. I'm all for it but
certainly
Guido van Rossum added the comment:
Okay.
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue46843>
___
___
Guido van Rossum added the comment:
New changeset 29624e769c5c3c1e59c6acc8b69383ead53e8a9f by Victor Stinner in
branch 'main':
bpo-31415: importtime was made by Inada Naoki (GH-31875)
https://github.com/python/cpython/commit/29624e769c5c3c1e59c6acc8b69383
New submission from Guido van Rossum :
At least on Windows and macOS, this repro shows that frozen modules are on in a
dev build:
Mac:
~/cpython$ ./python.exe -c 'import os; print(os._exists.__code__)'
", line 41>
~/cpython$ ./python.exe -Xfrozen_modules=off -c 'impor
Change by Guido van Rossum :
--
type: -> behavior
versions: +Python 3.11
___
Python tracker
<https://bugs.python.org/issue47017>
___
___
Python-bugs-list mai
Guido van Rossum added the comment:
The link
https://github.com/facebookincubator/cinder/blob/cinder/3.8/Python/ceval.c#L6617
points to something that I wouldn't associate with the subject. @Dino, could
you provide a new link (preferably a permalink)?
FWIW rather than dynamically che
Guido van Rossum added the comment:
I can't yet confirm a regression in 3.11 (the main branch, currently) compared
to 3.10. See my adventures in
https://github.com/faster-cpython/ideas/discussions/315.
--
___
Python tracker
&
Guido van Rossum added the comment:
@Dennis, if/when the PR looks good to you, you can merge it.
--
___
Python tracker
<https://bugs.python.org/issue47
Guido van Rossum added the comment:
Andrew, would you be interested in investigating this? I can't even follow the
flow through asyncio that causes the observed behavior (though I seem to have
confirmed it).
--
nosy: +asvetlov
___
Python tr
Guido van Rossum added the comment:
Nevertheless, the example code still hangs after calling sys.exit(). I can't
quite tell where it is hanging.
--
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
With python built from main I get:
/Users/guido/test_sys_exit_in_exception_handler.py:12: DeprecationWarning:
There is no current event loop
loop = asyncio.get_event_loop()
Got error, exiting
Exception ignored in: >
Traceback (most recent call l
Guido van Rossum added the comment:
I think I'm with Serhiy, I don't understand the hesitance to transform
tuple[*Ts][int, str] into tuple[int, str].
What would be an example of a substitution that's too complex to do?
--
___
Guido van Rossum added the comment:
I will wait until there is a draft PR to review, or until you ping me.--
--Guido (mobile)
--
___
Python tracker
<https://bugs.python.org/issue46
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue7946>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
title: Add vectorcall for generica alias object -> Add vectorcall for generic
alias object
___
Python tracker
<https://bugs.python.org/issu
Guido van Rossum added the comment:
Start here:
https://docs.google.com/document/d/18CXhDb1ygxg-YXNBJNzfzZsDFosB5e6BfnXLlejd9l0/edit
AFAICT the SC hasn't made up their minds about this.
--
___
Python tracker
<https://bugs.python.org/i
Guido van Rossum added the comment:
I'd like to look at this as a case of simplifying something to its simplest
canonical form, but no simpler. This is what the existing fixed-typevar
expansion does: e.g. tuple[str, T, T][int] becomes tuple[str, int, int].
I propose that we try to agr
Guido van Rossum added the comment:
Andrew, thanks for explaining this.
The key thing I was missing was that the root cause of the problem is that
Future.__del__ is trying to log an error about the un-awaited task by calling
the exception handler directly. That actually feels a little dodgy
Guido van Rossum added the comment:
New changeset 0360e9f34659e7d7f3dae021b82f78452db8c714 by Andrew Svetlov in
branch 'main':
bpo-46829: Deprecate passing a message into Future.cancel() and Task.cancel()
(GH-31840)
https://github.com/python/cpyt
Guido van Rossum added the comment:
Fixed by deprecating the message argument to cancel(). It will be removed in
3.13.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bug
Guido van Rossum added the comment:
I’m sorry, my brain hurts when trying to understand my own code for super.
Hopefully someone younger can look at this.--
--Guido (mobile)
--
___
Python tracker
<https://bugs.python.org/issue44
Guido van Rossum added the comment:
New changeset 785cc6770588de087d09e89a69110af2542be208 by Kumar Aditya in
branch 'main':
bpo-46429: tweak deepfreeze output (#32107)
https://github.com/python/cpython/commit/785cc6770588de087d09e89a69110a
Guido van Rossum added the comment:
So IIUC the "autosuper" idea is to assign a special instance of super to
self.__super, so that you can write self.__super.method(...) to invoke a super
method, using the magic of __private variables, instead of having to write
super(class
Guido van Rossum added the comment:
Please don’t try to “fix” anything. The value is only useful if you
understand the implementation. It should map straightforwardly to what’s in
memory.
On Mon, Mar 28, 2022 at 05:16 STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
&
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue45100>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
I used 9 in deepfreeze.py to signify "immortal object". It has been
copied by others (small integers are essentially immortal too). I wasn't too
sure that the refcount wouldn't go below zero if the interpreter is repea
Guido van Rossum added the comment:
Looks like there may be a new plan where we solve a smaller problem (overloads)
in the context of typing only.
--
___
Python tracker
<https://bugs.python.org/issue45
Guido van Rossum added the comment:
Thanks, let's close the issue as "won't fix".
--
resolution: -> wont fix
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<ht
Change by Guido van Rossum :
--
nosy: +eric.snow, gvanrossum
___
Python tracker
<https://bugs.python.org/issue46197>
___
___
Python-bugs-list mailing list
Unsub
Guido van Rossum added the comment:
Okay let's close it then. :-)
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Guido van Rossum added the comment:
Yeah, I see no description of what you can do with an unbound super object in
the docs (https://docs.python.org/3/library/functions.html#super), and
experimentation with it does not reveal any useful functionality.
You may want to open a new issue for
Guido van Rossum added the comment:
I don't mind reorganizing this, but I would insist that we keep code using old
undocumented things (like the sre_* modules) working for several releases,
using the standard deprecation approach.
--
___
P
Guido van Rossum added the comment:
> See bpo-47185: code.replace(co_code=new_code) no longer catch exceptions on
> Python 3.11.
Surely the bigger issue is that the contents of new_code itself must be totally
different? Also there are other tables that need to be adjusted if you real
Guido van Rossum added the comment:
How would you compute the exception table from the bytecode? There are no clues
in the bytecode about where the try and except blocks are.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.
Guido van Rossum added the comment:
1. If we're reorganizing anyway, I see no reason to keep the old names.
2. For maximum backwards compatibility, I'd say keep as much as you can, as
long as keeping it won't interfere with the
Guido van Rossum added the comment:
[Victor]
> Do you consider that .replace() must reject changing co_code if other tables
> are not updated?
I simply don't believe it can always do that correctly, so I believe it should
not do it.
> Debugging tables are not strictly re
Guido van Rossum added the comment:
At this point I think it's worth filing a new bug proposing to deprecate 1-arg
super(), pointing out the broken usages that search found.
--
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
This idea just cannot work. Take these two functions:
def f():
foo()
try:
bar()
except:
pass
def g():
try:
foo()
bar()
except:
pass
Using dis to look at their disassembly, the only hint that in f
Guido van Rossum added the comment:
If you think the changes to .replace() should be documented just open a new
bpo. You made this issue about your various proposals to change .replace().
--
___
Python tracker
<https://bugs.python.org/issue47
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue47236>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
So is the conclusion that this should be closed as "not a bug"?
--
___
Python tracker
<https://bugs.python.o
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue47234>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
> -_Py_DECREF (pgo hard reject)
What exactly does "pgo hard reject" mean? I Googled it and found no hits
besides this very issue.
I am trying to redefine the top three from this error log as macros, but since
I still don't have stable
Change by Guido van Rossum :
--
pull_requests: +30425
pull_request: https://github.com/python/cpython/pull/32387
___
Python tracker
<https://bugs.python.org/issue45
Guido van Rossum added the comment:
We need to move on this, because the outcome of this discussion is a release
blocker for 3.11b1 -- the next release!
--
priority: normal -> release blocker
type: -> behavior
___
Python tracker
Guido van Rossum added the comment:
@Ewout, the current workaround (until pydevd is fixed) is to add
-Xfrozen_modules=off to the Python command line.
--
___
Python tracker
<https://bugs.python.org/issue1666
Guido van Rossum added the comment:
Using `__wrapped__` if present sounds like a good idea. Ivan, what do you think?
Netzeband, have you considered submitting a PR with the necessary changes (and
tests and docs)?
--
___
Python tracker
<ht
Guido van Rossum added the comment:
Maybe we should tag this issue "newcomer friendly"? It seems a pretty open
and shut case.
--
___
Python tracker
<https://bugs.python.o
Guido van Rossum added the comment:
PEP 8 intentionally allows users to choose whether to put the operator at the
start or end of the line (as long as they're consistent within a file or
project). This is to avoid a barrage of "style fixes" that are just noise.
But PE
Guido van Rossum added the comment:
Thanks Josh! The automated backport to 3.7 didn't work, that's okay, so I'll
close this now. (Though if you want to experiment with the cherry-picker tool
go ahead.)
--
resolution: -> fixed
stage: patch review -> resolved
s
Guido van Rossum added the comment:
It never occurred to me that making b&b an b|b return bool would be considered
a bad thing just because ~b is not a bool. That's like complaining that 1+1
returns an int rather than a float for consistency with 1/2 returning a float.
Becaus
Guido van Rossum added the comment:
> > Because bool is embedded in int, it's okay to return a bool value *that
> > compares equal to the int from the corresponding int operation*.
> Agreed that it's okay, but I'd like to understand why it's considered
&g
Guido van Rossum added the comment:
s/book/bool/
--
___
Python tracker
<https://bugs.python.org/issue37831>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue30413>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Yes, I still feel like this and I find it applies here. (Note that the module
already has two variants of fnmatch(), so it's nothing new in this context.)
--
___
Python tracker
<https://bugs.py
Guido van Rossum added the comment:
It should not go on the numeric tower.
--
--Guido (mobile)
--
___
Python tracker
<https://bugs.python.org/issue26
Guido van Rossum added the comment:
Making an existing stdlib class generic has to be considered carefully,
otherwise it may break backward compatibility.
As I wrote in the typeshed issue, I actually think the status quo is fine. But
I'd like to hear you out about how it causes proble
Guido van Rossum added the comment:
Sounds like you are mixing up analyzing .pyi and .py files.
Anyway, let's not do this.
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https:
Guido van Rossum added the comment:
The decision has been made to get rid of TargetScopeError and instead just use
SyntaxError. PEP 572 was updated already. We're just waiting for someone
(Serhiy?) to review Nick's patch, PR #15131.
--
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue37806>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
I agree -- this was added to Emacs a long time ago and it makes a big
difference for people (like myself) who do a lot of work in Emacs shell
windows. I imagine it's the same for IDLE.
--
nosy: +gvanr
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue37827>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue37953>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
assignee: -> benjamin.peterson
nosy: -gvanrossum
title: Race in PyThread_release_lock - can lead to MEMORY CORRUPTION and
DEADLOCK -> Race in PyThread_release_lock - can lead to memory corruption and
de
Guido van Rossum added the comment:
Congrats! Let's party.
--
___
Python tracker
<https://bugs.python.org/issue35224>
___
___
Python-bugs-list mailing list
Guido van Rossum added the comment:
Thank you Raymond.
Luna, are you still interested?
--
___
Python tracker
<https://bugs.python.org/issue34805>
___
___
Pytho
Guido van Rossum added the comment:
It's just a small doc change right? I'd just makle a PR and see if Raymond
accepts it.
--
___
Python tracker
<https://bugs.python.o
Guido van Rossum added the comment:
Sorry to burst your bubble, but I don't see a reason to include this in the
stdlib. Is there any reason why it can't be a dependency living on PyPI just
like the packages you used in the example (numpy, pandas)?
Surely this isn't a categ
Guido van Rossum added the comment:
I'm going to close this. I find your example hard to understand. If you want to
discuss this on python-ideas or discourse, go ahead, but this is not ready for
a PEP or for stdlib inclusion.
--
resolution: -> wont fix
stage: -> reso
Guido van Rossum added the comment:
I feel that this is a relatively minor issue, and not worth breaking "working"
code over. Some more pedantic tool like a linter or type checker would be a
better place to start diagnosing this.
--
Guido van Rossum added the comment:
I am going to recommend sticking to the status quo, i.e. Andrew's improvements
to asyncio.Stream should stay. The rest of this message is an elaboration.
The new perfect composable Streams design is just that -- a design. Many things
could go wrong i
Guido van Rossum added the comment:
We're intentionally holding back on the places where we allow unparenthesized
walrus operators.
There are some tricky issues in this particular bit of syntax -- look at this
line in the grammar:
https://github.com/python/cpython
Guido van Rossum added the comment:
@xtreak do you think we need to keep this issue open then?
--
___
Python tracker
<https://bugs.python.org/issue38
1701 - 1800 of 5533 matches
Mail list logo