Guido van Rossum added the comment:
[Barry]
> I know the PEP defines TargetScopeError as a subclass of SyntaxError, but it
> doesn't really explain why a subclass is necessary. I think seeing
> "TargetScopeError" will be a head scratcher. Why not just SyntaxError
Guido van Rossum added the comment:
But we don't do that with any of the other (many) errors detected by later
passes of the compiler. Those report dozens of SyntaxErrors, with good
descriptive messages. Users can search the web for those messages too.
Also, I doubt that many people
Guido van Rossum added the comment:
If you and Nick both feel strongly about this please take it to python-dev,
I'm sure we'll get closure quickly there.
--
___
Python tracker
<https://bugs.python.o
Guido van Rossum added the comment:
> 1. Should I create a new function in the `ast` module that exposes that C
> function in Python in order to use it in `Lib/inspect.py`?
> 2. Would it be better to just re-use the _AST to string_ implementation in
> `Tools/unparse.py`?
I would
Guido van Rossum added the comment:
Let's not do this. We've survived this long.
--
___
Python tracker
<https://bugs.python.org/issue16837>
___
___
Guido van Rossum added the comment:
That’s correct. Mind making a PR?
--
___
Python tracker
<https://bugs.python.org/issue37814>
___
___
Python-bugs-list mailin
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue37808>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
> What is better, Tuple[()] or Literal[()]?
In this context, Tuple[()] is better, as the discussion is about how to write
the type of various tuples. Tuple[()] is just the edge case of the type of the
empty tuple.
Josh, please sign the CLA and adjust
Guido van Rossum added the comment:
Let's continue on the current path -- add Fraction.as_integer_ratio().
Note that as_integer_ratio() is not part of the Numbers API, it is an optional
protocol.
You can count me out for Jeroen's __ratio_
Guido van Rossum added the comment:
I don't have time to review this, sorry.
--
___
Python tracker
<https://bugs.python.org/issue37808>
___
___
Pytho
Guido van Rossum added the comment:
This issue is closed, but you can open a new issue to flag this in the docs.
--
___
Python tracker
<http://bugs.python.org/issue1
Guido van Rossum added the comment:
Skimming the issue I can't even figure out what the task is -- Cheryl, I
suppose you have, could you post a brief summary of your plan here?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
I've tried thinking though a few scenarios, and I think I'm +1 (or at least
+0 or +0.5) on the proposed change to locals(), and of course I'm happy
that we're going to specify its behavior better.
--
__
Guido van Rossum added the comment:
You nailed it, Emily! This is not a bug (though the docs could be a bit more
upfront about this -- just having "cache" in the name doesn't cut it these days
:-).
If either Serhiy or Raymond agrees they can close the issue (we won't wait
Changes by Guido van Rossum :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue21998>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Yeah, I think a short PEP would be helpful here.
--
___
Python tracker
<http://bugs.python.org/issue17960>
___
___
Python-bug
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue11798>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
How do you define "urgent data"? Is this just the third category of select(),
Read, Write, Exceptional? I don't know if that should be considered urgent,
it's just "out of band" IIRC.
--
___
Guido van Rossum added the comment:
Do you have a specific use case where it's important to access the remaining
data? ISTM that this is happening when the connection is lost and then it
shouldn't matter how much of the data you read or not -- the connection was
broken before the r
Guido van Rossum added the comment:
The Redis example doesn't sound valid to me, as (IIUC) it closes the connection
immediately?
--
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
We seem to have a failure to communicate. I'm sure your example code "works",
but you're not showing what's in the data it receives that is important for the
app to read (your example just prints it).
And surely your app sho
Guido van Rossum added the comment:
But half closed state is already supported.
On Jul 7, 2017 2:37 AM, "Dima Tisnek" wrote:
>
> Dima Tisnek added the comment:
>
> It seems Guido sets a higher bar on the proposed change.
>
> @pfreixes, if you can show that this c
Guido van Rossum added the comment:
IMO you haven't demonstrated a need, you are just complaining that you
don't like it.
--
___
Python tracker
<http://bugs.python.o
Guido van Rossum added the comment:
Yes.
--
___
Python tracker
<http://bugs.python.org/issue27364>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Please find a list like python-list (comp.lang.python) to ask for help with
your problem.
Also please stop adding people to the nosy list.
--
stage: -> resolved
status: open -> closed
___
Python tracker
Guido van Rossum added the comment:
So top ope in tickets about this issue or you will be banned.
On Jul 13, 2017 8:46 AM, "Sanket" wrote:
>
> New submission from Sanket:
>
> import threading
> import subprocess
>
> def B():
> while True:
>
Guido van Rossum added the comment:
There's no need. You seem to have accidentally shown a use case for getting the
buffered data -- it can contain an error message explaining why the connection
was closed.
--
___
Python tracker
Guido van Rossum added the comment:
On python-dev Raymond agreed to reopen the issue and consider Jelle's
implementation (https://github.com/python/cpython/pull/2736).
--
nosy: +gvanrossum
___
Python tracker
<http://bugs.python.org/is
Guido van Rossum added the comment:
Thanks Raymond and Jelle.
The bar for a reimplementation in C is much higher (though we'll have to agree
that Jelle's version is fast enough before we reject it).
The bar for backporting this to 3.6 is much higher as well and I think it&#x
Guido van Rossum added the comment:
Yeah, it looks like the standard `_pickle` and `pickle` solution would work
here.
--
___
Python tracker
<http://bugs.python.org/issue28
Guido van Rossum added the comment:
At least one use of Indexable (by whatever name, but this rolls off the tongue
the easiest) would be the metaclass in typing.py that allows one to write
List[int] -- there's no containter here!
The "drowning out" seems purely subjective --
Guido van Rossum added the comment:
Yes we will need a deprecation period for this starting with 3.7. It's fine
not to import names newly added to collections.abc in 3.7 (i.e. collections
would have to explicitly import everything that it got via * i
Guido van Rossum added the comment:
The copying approach likely won't work because there will be code that uses
isinstance(x, collections.abc.Sequence) and other code that uses isinstance(x,
collections.Sequence) and they'll expect both
Guido van Rossum added the comment:
I think it's not worth the hack that Serhiy suggests. But we should make
some noise around this change in the 3.7 announcement.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue30985>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
> > there's no way to end the loop on the producing side.
> I might be missing something, but can't something similar be said of
> queue.get()?
That's my point, actually. If you are wrapping the Queue protocol with
__aiter__
Guido van Rossum added the comment:
Alexander, can you summarize the status of this issue? Maybe we can move
forward for 3.7?
--
___
Python tracker
<http://bugs.python.org/issue24
Guido van Rossum added the comment:
I haven't reviewed the code, but given Tim Peters' response (which matches my
own gut feeling) we should just allow/support tz offsets with second-precision
(and deal with the default formatting issues in a backwards compatible way, of
course)
Guido van Rossum added the comment:
Please do! I have no opinion on %::z but maybe you can find inspiration in the
Zen of Python. :-)
--
___
Python tracker
<http://bugs.python.org/issue24
Guido van Rossum added the comment:
So that's an infinite loop right?
--
___
Python tracker
<http://bugs.python.org/issue28777>
___
___
Python-bugs-list m
Guido van Rossum added the comment:
I think the proposed change is not worth it. Developments in type checking (in
particular overloading) make it unambiguous what the return type will be from
just a static inspection of the call site. (Given that the _UNSET value is
intended to be private
Guido van Rossum added the comment:
I don't think this is worth it.
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.pyth
Guido van Rossum added the comment:
Let's not do this.
--
resolution: -> rejected
stage: test needed -> resolved
status: open -> closed
___
Python tracker
<http://bugs.pyth
Guido van Rossum added the comment:
Given the date from that comment I assume that I told Raymond this during the
2016 core sprint. I can't recall that conversation but I am still pretty
worried about using an RLock. (What if someone slightly more insane decides to
call get() from inside
Guido van Rossum added the comment:
Before I spend more time reviewing your patch, can you please explain what you
mean by "sphinx fails to find these"? Is there a particular dead link on
docs.python.org or a specific query you typed in the search box that failed to
find the def
Guido van Rossum added the comment:
Thanks, I am a little closer to understanding now.
> once intersphinx looks at the Tuple during documentation generation it
> deduces it actually is of type class
How does intersphinx deduce this? Also, does it run when we generate the Python
docs, o
Guido van Rossum added the comment:
OK, I think Sphinx is way too complicated for its own good, and it's arguably
not the fault of Python's documentation that this doesn't work for you.
I would like to close this issue as "won't fix", except... in a sense Tuple
Guido van Rossum added the comment:
Agreed; the Queue class has a bunch of rarely used functionality rolled
in...
Why was task management ever added?
--
___
Python tracker
<http://bugs.python.org/issue14
Guido van Rossum added the comment:
Oh well. While it is undoubtedly useful I wish we had had more experience and
factored the API differently. Ditto for the maxsize=N feature.
So, while it's not too late, perhaps we should indeed follow Antoine's advice
and implement a different
Guido van Rossum added the comment:
I've heard many anecdotal complaints about the lack of speed of ABCs. Even if
it doesn't affect core Python startup, it does affect startup of apps, and if
people are afraid to use them because of this, it's reasonable to try to do
som
Guido van Rossum added the comment:
Can't you just submit a PR? It's so easy now!
--
___
Python tracker
<https://bugs.python.org/issue26858>
___
___
Guido van Rossum added the comment:
For modules, __name__ is the fully-qualified name, and that's fine.
But for classes and functions __name__ is just the "given name" from the syntax
(whatever came after 'def' or 'class') and that's not fine -- for anyt
Guido van Rossum added the comment:
Given Nick's feedback (and imagining what this would do to some codebases I
know) I think this idea is dead, sadly. A helper function just doesn't give
enough value, so let's not pursue that (it's easy to write the helper you
want, it
Guido van Rossum added the comment:
And thanks for working it through! It was a valuable exercise.
--
___
Python tracker
<https://bugs.python.org/issue13
Guido van Rossum added the comment:
@benjamin can you post your patch as a PR so you'll get credit for it?
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
> Why not simply document the fact that read ahead in Python 2.7
> is not thread-safe and leave it at that ?
Program bugs should not crash the interpreter. (ctypes excepted.)
--
___
Python tracker
Guido van Rossum added the comment:
I'm afraid I no longer have all the details of this design in my head, and I
have no idea what the fix does (and no time to read up on everything).
The OP says "If you do not await gather" -- what happens if you *do* await it?
Do the tasks
Guido van Rossum added the comment:
> if you change run_forever with run_until_complete, then behavior changes:
> success_coro(5) will not be executed
Oh, that's a red herring. The reason is that the event loop stops when you use
run_complete(), but the execution of success_coro(
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue34995>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Given that this is in collections, I don't object. Ivan, what do you say?
--
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
Do not change this. I'd rather see it documented that importlib can import any
name as long as it doesn't contain a dot, slash or backslash.
(Clearly the fact that Django loads it is an additional argument that this
should be supported, not
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue34850>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
What's the use case for subclassing DateTime? These classes were not designed
with subclassing as a use case in mind.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/is
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue32417>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
OK.
--
___
Python tracker
<https://bugs.python.org/issue32417>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
No, I consider this is a documentation problem. I don't recall why the docs say
that (I don't even know if they still say that or whether Martijn misread
them), but IMO this should not be changed.
--
Guido van Rossum added the comment:
Luna and I talked a bit about this offline and we decided not to merge the PR
(nor the original patch, which is the same). Instead Luna will add a note to
the docs explaining the caveat.
--
nosy: +gvanrossum
Guido van Rossum added the comment:
Luna discovered that has actually been fixed in 3.8 (i.e. the master branch),
by making {}.get hashable. So I'm closing this as fixed.
--
resolution: -> fixed
stage: patch review -> resolved
status: ope
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue35517>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue17561>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue23057>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
A rejected PEP still exists in perpetuity, and can still be used as a
reference. Also, the reason for PEP 258's rejection is not that it is invalid,
but that it's not slated for stdlib inclusion. So I think that the reference is
still useful, a
Guido van Rossum added the comment:
For reference, the OP reported the issue initially at
https://github.com/python/psf-infra-meta/issues/17 (but it was closed because
that's not the right tracker).
The y1y2y3y4 etc. are multiplications (mangled by not quoting the code in
GitHub and
Guido van Rossum added the comment:
I agree.
On Thu, Jan 10, 2019 at 11:24 PM Serhiy Storchaka
wrote:
>
> Serhiy Storchaka added the comment:
>
> This is a common mistake. Even the default implementation of object.__ne__
> had a bug, fixed only 4 years ago in issue21408. The
New submission from Guido van Rossum :
(This started at
https://discuss.python.org/t/merge-typed-ast-back-into-cpython/377. It's
somewhat related to https://bugs.python.org/issue7.)
I now have a thorough understanding of what typed_ast does, and I think it
would be straightforwa
Guido van Rossum added the comment:
You’d be surprised how tenacious old versions are.
Anywa, I am working on this on my copious spare time — you can follow my
progress at
https://github.com/gvanrossum/cpython/tree/ast-type-comments?files=1
Guido van Rossum added the comment:
See also issue35766.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue24119>
___
___
Python-bugs-list m
Change by Guido van Rossum :
--
keywords: +patch, patch
pull_requests: +11427, 11428
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Guido van Rossum :
--
keywords: +patch
pull_requests: +11427
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Guido van Rossum :
--
keywords: +patch, patch, patch
pull_requests: +11427, 11428, 11429
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Guido van Rossum added the comment:
It's been a somewhat well-known idiom for modules to replace themselves in
sys.modules with an object that implements some special behaviors (e.g. dynamic
loading). This "just works" and AFAIK people have been doing this for ages.
Typical
Guido van Rossum added the comment:
OK, I don't see a bug here. The docs for sys.modules are pretty vague -- I
don't believe they imply that all values in sys.modules must have every
attribute of a Module object.
--
resolution: -> wont fix
stage: test needed ->
New submission from Guido van Rossum :
Pgen is literally the oldest piece of technology in the CPython repo -- it was
the first thing I wrote for Python over 29 years ago. It's not aged well, and
building it requires various #if[n]def PGEN hacks in other parts of the code;
it also de
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue15248>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
This is huge!
I do recall there are some minor edge cases where the implementation currently
doesn't match the PEP. Could you summarize those here, and add your
recommendation (e.g. change the PEP, fix the code, wait and see) with
motiv
Guido van Rossum added the comment:
The PR is ready for reviews now.
--
___
Python tracker
<https://bugs.python.org/issue35766>
___
___
Python-bugs-list mailin
Guido van Rossum added the comment:
Option 2 sounds best. I am also not against adding __spec__ but I think we
should support the idiom regardless, and I don’t consider this a bug in the
typing module — at best there’s a slight improvement.
On Sun, Jan 27, 2019 at 6:50 AM Nick Coghlan wrote
Guido van Rossum added the comment:
@eamanu, feel free to submit a PR. I won't be available to guide you through
the steps; there are other forums e.g. Zulip.
--
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
Thanks!
--
___
Python tracker
<https://bugs.python.org/issue35806>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Also the tests now all pass; for now I am happy with the solution I found for
the indentation error (see
https://github.com/python/cpython/pull/11645#issuecomment-456627216).
--
___
Python tracker
<ht
Change by Guido van Rossum :
--
pull_requests: +11573
___
Python tracker
<https://bugs.python.org/issue35766>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
pull_requests: +11573, 11574
___
Python tracker
<https://bugs.python.org/issue35766>
___
___
Python-bugs-list mailing list
Unsub
Change by Guido van Rossum :
--
pull_requests: +11573, 11574, 11575
___
Python tracker
<https://bugs.python.org/issue35766>
___
___
Python-bugs-list mailin
Guido van Rossum added the comment:
Emily, I think this would be as simple as making a tiny change to
Grammar/Grammar and running make regen-grammar. Can you take care of that?
--
assignee: -> emilyemorehouse
stage: -> needs patch
___
Guido van Rossum added the comment:
Thanks, Karthikeyan! Can you submit that as a PR?
--
___
Python tracker
<https://bugs.python.org/issue35877>
___
___
Pytho
Guido van Rossum added the comment:
I can confirm it, but I don't understand it yet. Somehow the type_comment
fields get an extra reference count and are never freed. How are other string
fields handled?
--
___
Python tracker
&
Guido van Rossum added the comment:
OK, let me make a PR, I found another leak for type:ignore.
On Fri, Feb 1, 2019 at 9:22 AM Pablo Galindo Salgado
wrote:
>
> Pablo Galindo Salgado added the comment:
>
> The extra referenced happen here in Python-ast.c :
>
> value
Guido van Rossum added the comment:
> ast2obj_string increments it once and the setattr does it again and then
> there is only one Py_DECREF.
Actually I don't understand how this is the leak. Adding another
Py_DECREF(value) causes an immediate crash. I've been trying to fol
3301 - 3400 of 5563 matches
Mail list logo
