Guido van Rossum added the comment:
Łukasz, can I please have a decision on whether to backport this bugfix to 3.9?
See my comment about that:
https://github.com/python/cpython/pull/21553#pullrequestreview-452895735
--
___
Python tracker
<ht
Guido van Rossum added the comment:
I think mentioning this in the docs is the best we can do in 3.9, and for 3.10
the point will be moot. The next release is release candidate 1, so we're well
past the point where we can implement new function
Guido van Rossum added the comment:
I've reviewed your first PR (#21509).
Regarding your second one, I think there's a misunderstanding. With "pydoc" I
didn't mean "the Python docs". IMO the documentation of f-strings in the
language reference is suff
Guido van Rossum added the comment:
This looks like a useful addition. I hope someone will take up the review!
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue40
Guido van Rossum added the comment:
Łukasz, what do you think of backporting this to 3.9?
--
nosy: +gvanrossum, lukasz.langa
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Why not add Travis-CI and AppVeyor?
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41328>
___
___
Guido van Rossum added the comment:
Either remove it or close this issue as won’t fix.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
This surely is some application corner case. Closing.
--
nosy: +gvanrossum
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
Is this really worth our attention? In 3.10 this will be irrelevant.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
We should not do this, it would expose internals that we need to keep private.
The right approach would be to keep things as bytes.
--
nosy: +gvanrossum
resolution: -> wont fix
stage: -> resolved
status: open -&g
Guido van Rossum added the comment:
There already is a decent set of examples. I think a Snake game is a worthy
addition.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Waiting for someone to submit a PR.
--
___
Python tracker
<https://bugs.python.org/issue41314>
___
___
Python-bugs-list m
Guido van Rossum added the comment:
Marking this as "easy". People are welcome to submit PRs that fix the wording
in one or a small number of modules called out in Serhiy's list.
--
keywords: +easy
nosy: +gvanrossum
___
Python
Guido van Rossum added the comment:
We might get more help with this issue if the process of updating the help()
output were better documented. I recently looked into what it would take to add
"FSTRINGS" to the "topics" list, and it's quite complicated -- I only
Guido van Rossum added the comment:
Sorry, I realize what's wrong here. When we switched to the new PEG parser (the
"pegen" you saw mentioned in the warning) we switched to a new grammar file.
You have to change Grammar/python.gram instead of Grammar/Grammar.
We couldn
Guido van Rossum added the comment:
There are some difficulties with removing Grammar/Grammar, since it is used to
generate the full grammar in the reference docs (Doc/reference/grammar.rst).
Producing a similar grammar from the PEG grammar is currently painful because
our PEG grammar
Guido van Rossum added the comment:
@ned This will need your assistance to merge the 3.7 backport IIUC.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Never mind, Miss Islington failed to backport to 3.7, so let's forget about
that.
--
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/is
Guido van Rossum added the comment:
This can be closed. It needs docs though; there's a separate issue for that
(issue40814).
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python t
Guido van Rossum added the comment:
Alternatively, we at least need a section of documentation for things like
`list[int]` and `dict[str, float]`.
--
___
Python tracker
<https://bugs.python.org/issue40
Guido van Rossum added the comment:
Hm, recursive type aliases are an interesting issue. We may be able to do
better there for 3.10, even if we can't fix it for 3.9 (or at least not for
3.9.0).
But in the meantime maybe you can come up with a PR that adds a note to the
typing docs in
Guido van Rossum added the comment:
In general, "4.0" means "never", and for some deprecations that seems totally
appropriate. I wouldn't worry about it. I'm closing this issue now that all
three PRs have been merged. Thanks for your contribution!
Guido van Rossum added the comment:
New changeset f117cef25b5ffc4db9fbe373ddb65e14f59f0397 by Shankar Jha in branch
'master':
bpo-39868: Add documentation for Assignment Expressions (walrus, PEP 572)
(#18851)
https://github.com/python/cpython/commit/f117cef25b5ffc4db9fbe373ddb65e
Guido van Rossum added the comment:
Congratulations SHANKAR JHA. Thank you for your contribution.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10, Python 3.9
___
Python tracke
Change by Guido van Rossum :
--
pull_requests: +20765
pull_request: https://github.com/python/cpython/pull/21624
___
Python tracker
<https://bugs.python.org/issue40
Guido van Rossum added the comment:
There’s probably also something in configure.in that can switch this on.
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue41340>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<https://bugs.python.org/issue41380>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Thank you Joseph Perez! Looking forward to more of your contributions.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
Thank you Abhijeet! Looking forward to more of your contributions.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
See also https://github.com/python/cpython/pull/19969 (Pablo's attempt at
replacing the grammar in the reference docs with something derived from
Grammar/python.gram).
--
___
Python tracker
&
Guido van Rossum added the comment:
I guess the design space is wide open.
Does parso have to be pure Python? If not, we could generate C code like we do
for CPython's parser. Now, that doesn't work for incremental parsing, but I did
an alternative implementation that uses a sta
Guido van Rossum added the comment:
Those are really good observations and proposals, Ezio! I agree that it might
be better to separate them into a new issue. Can you also review
https://github.com/python/cpython/pull/21552 (the second PR here by
amaajemyfren)? Maybe it would actually make
Guido van Rossum added the comment:
It's basically an accident that the only f-strings docs are in the language
reference. Yes, they should be there, and the text there is pretty good *for
the reference*, but there isn't much about them elsewhere outside of the
tutorial, so everyt
Guido van Rossum added the comment:
New changeset 72cabb2aa636272e608285f5a6ba83b62be9be4e by Pablo Galindo in
branch 'master':
bpo-40939: Use the new grammar for the grammar specification documentation
(GH-19969)
https://github.com/python/cpyt
Change by Guido van Rossum :
--
pull_requests: +20782
pull_request: https://github.com/python/cpython/pull/21641
___
Python tracker
<https://bugs.python.org/issue40
Guido van Rossum added the comment:
The old parser is completely gone from the 3.10 branch. Closing.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
New changeset e6b2d93f0c3891827f609ecac1ced21e1626ed0a by Guido van Rossum in
branch '3.9':
[3.9] bpo-40939: Use the new grammar for the grammar specification
documentation (GH-19969) (#21641)
https://github.com/python/cpyt
Guido van Rossum added the comment:
I think your PR 21552 and any work you're doing on pydoc could go under the new
issue 41411 that Ezio just opened.
--
___
Python tracker
<https://bugs.python.org/is
Change by Guido van Rossum :
--
pull_requests: +20785
pull_request: https://github.com/python/cpython/pull/21645
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
I declare this a duplicate of issue 38119.
--
nosy: +gvanrossum
resolution: -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder: -> resource tracker destroys shared memory segments when other
processes shoul
Guido van Rossum added the comment:
@Davin, could you merge one or the other of the PRs that fix this? Presumably
also backport to 3.9 and 3.8 (but that's up to you and the release manager).
--
nosy: +gvanrossum
versions: +Python 3.10
___
P
Guido van Rossum added the comment:
New changeset e962e3f65a086d9d3b848483fd01215d96ecc5f9 by Guido van Rossum in
branch '3.9':
[3.9] bpo-41045: Document debug feature of f-strings ('=') (GH-21509) (GH-21645)
https://github.com/python/cpython/commit/e962e3f65a086d9d3b84
Change by Guido van Rossum :
--
pull_requests: +20786
pull_request: https://github.com/python/cpython/pull/21647
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Whether the data was retrieved over a network has nothing to do with it.
There are complementary ways of guessing what data you are working with --
guess based on the filename extension or sniff based on the contents of the
file (or downloaded data
Guido van Rossum added the comment:
New changeset 3baff21f5bb8db7fa1c15788a8f82fa040a90d5d by Guido van Rossum in
branch '3.8':
[3.8] bpo-41045: Document debug feature of f-strings ('=') (GH-21509) (#21647)
https://github.com/python/cpython/commit/3baff21f5bb8db7fa1c1
Guido van Rossum added the comment:
Thanks Ama Aje My Fren! You can transfer your other PR to a different bpo issue
by editing the subject on GitHub.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
_
Change by Guido van Rossum :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
Can you file a separate bug report for the license link? We may need to review
that with the lawyer, to see if we can use AFL 3.0, since AFL 2.1 seems
obsolete.
--
___
Python tracker
<https://bugs.python.
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41420>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
I've sent an email to our lawyer.
--
___
Python tracker
<https://bugs.python.org/issue41420>
___
___
Python-bugs-list m
Guido van Rossum added the comment:
Note that there already is something in the tutorial about f-strings (in
inputoutput.rst, labeled tut-f-strings), and the intro has a link to their
reference manual description in the "see also&quo
Guido van Rossum added the comment:
When the standard says "trust the filename" it is talking to the
application, not to the sniffing library. The library should provide the
tool for applications to follow the standard, but I don't see a reason why
we would have to enforce h
Guido van Rossum added the comment:
A few options present themselves:
- We could switch to AFL 3.0 (https://opensource.org/licenses/AFL-3.0). This
will require some review by our lawyer.
- We could link to another copy of AFL 2.1. Honestly the original one seems
pretty odd.
- We could
Guido van Rossum added the comment:
I also found what looks like a copy of AFL 2.1 on Python's own wiki:
https://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq/AFL-2.1
(Of course, being a wiki, this has the disadvantage of being publicly editable.
:-)
Yet another option pre
Guido van Rossum added the comment:
Which patch are you referring to? Is it already merged?
--
___
Python tracker
<https://bugs.python.org/issue40360>
___
___
Guido van Rossum added the comment:
Okay, so if you know what to do please do it. ;-)
--
___
Python tracker
<https://bugs.python.org/issue40360>
___
___
Pytho
Guido van Rossum added the comment:
New changeset fe928b32daca184e16ccc0ebdc20314cfa776b98 by Karthikeyan
Singaravelan in branch '3.9':
[3.9] bpo-40360: Handle PendingDeprecationWarning in test_lib2to3. (GH-21694)
(GH-21697)
https://github.com/python/cpyt
Guido van Rossum added the comment:
I agree with Luciano's conclusion and have nothing to add other than to
encourage him to submit a PR for the docs. (I know he already submitted a
PR to refactor the docs. Honestly I lost track of that one. Luciano, if you
need my review for that one, p
Guido van Rossum added the comment:
You're going to have to ignore that status or skip the offending files.
--
nosy: +gvanrossum
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https:
Guido van Rossum added the comment:
New changeset ab72fdeb82c3ab045b480cd4bb4f928c12653ecb by Luciano Ramalho in
branch 'master':
bpo-40979: refactored typing.rst; (mostly) same content, new sub-sections and
ordering (#21574)
https://github.com/python/cpyt
Guido van Rossum added the comment:
Thank you so much for your hard work and flexibility! The chapter is in much
better shape now.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracke
Guido van Rossum added the comment:
Thanks, I was looking for this.
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
So per the stackoverflow explanation you shouldn’t do that? Should we close
this?
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Maybe you’ll get some explanation or pointers on python-list. Or were you
volunteering to write something?
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Looks like a duplicate of https://bugs.python.org/issue38119
--
nosy: +gvanrossum
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
I don't think that waiting another six months is going to make this happen
either. Maybe you can petition realpython.com to publish something about this.
Honestly it sounds like this ties too many different topics together to easily
fit in the li
Guido van Rossum added the comment:
I don't know anything about Docker, so I can't help you there. Please don't
reopen the issue again.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<https://bu
Guido van Rossum added the comment:
If you don't even know whether it's Python, Docker or Kubernetes you really
need to ask somewhere else. Plenty of user groups around.
Python detects tty using the standard UNIX isatty() function.
To a tty we always get line buffering.
To a fil
Guido van Rossum added the comment:
Could you submit a PR then? I don't think I've looked at that module in 20
years.
--
___
Python tracker
<https://bugs.python.o
Change by Guido van Rossum :
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue32623>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
No, that is up to the static type checker. With PEP 563 nearing completion in
Python 3.10 we will in fact be ignoring all annotations silently.
--
resolution: -> not a bug
stage: -> resolved
status: open -&g
Guido van Rossum added the comment:
I recommend bringing this new proposal up on python-dev or python-ideas, to get
more eyeballs on the ideas before attempting implementation. One immediate
worry I have is that if the reference counter is maintained in the shared
memory segment, every
Guido van Rossum added the comment:
Sorry to rain on your parade, but couldn’t this be a new package on PyPI?
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue41
Guido van Rossum added the comment:
Wrong issue, sorry. (Bpo bug?)
--
___
Python tracker
<https://bugs.python.org/issue41474>
___
___
Python-bugs-list mailin
Guido van Rossum added the comment:
Hm, the fix would seem simple enough. Can you submit a PR? It would be nice if
it had a test as well.
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Guido van Rossum :
--
nosy: +gvanrossum
nosy_count: 4.0 -> 5.0
pull_requests: +20959
pull_request: https://github.com/python/cpython/pull/21830
___
Python tracker
<https://bugs.python.org/issu
Guido van Rossum added the comment:
New changeset 7b3ceaa71051d811bfee0b62ef9cb0fd2121c7ee by Miss Islington (bot)
in branch '3.8':
[3.8] bpo-41504: Add links to asttokens, leoAst, LibCST and parso to ast docs
(GH-21773) (GH-21829)
https://github.com/python/cpyt
Guido van Rossum added the comment:
The master commit was e3c971ccfa58afcb2656b71b95e10b9703f2ad32 (somehow because
the commit message didn't contain the bpo-41504 tag the automation didn't work
flawlessly).
--
___
Python track
Guido van Rossum added the comment:
New changeset d1d6a1c6abf76b27c247ead8a8872011db77cf58 by Guido van Rossum in
branch '3.9':
[3.9] bpo-41504: Add links to asttokens, leoAst, LibCST and parso to ast docs
(GH-21773) (GH-21830)
https://github.com/python/cpyt
Guido van Rossum added the comment:
Thanks!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10, Python 3.8
___
Python tracker
<https://bugs.python.or
Change by Guido van Rossum :
--
pull_requests: +20970
pull_request: https://github.com/python/cpython/pull/21843
___
Python tracker
<https://bugs.python.org/issue40
Guido van Rossum added the comment:
New changeset b3ad2ca56afc6a56c9a6e7b419bc05e8e5b15e19 by Guido van Rossum in
branch '3.9':
[3.9] bpo-40979: refactored typing.rst; (mostly) same content, new sub-sections
and ordering (GH-21574) (#21843)
https://github.com/python/cpyt
Guido van Rossum added the comment:
I think it makes sense to remove the `async` from the definition in
AbstractEventLoop.
If you want to help, you can submit a PR to do it.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.
New submission from Guido van Rossum :
We need stub versions of ParamSpec and Concatenate added to typing.py, plus
tests that ensure these actually work in all situations required by the PEP.
(It's not so important to ensure that they raise exceptions at runtime in cases
where the PEP
Change by Guido van Rossum :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Guido van Rossum added the comment:
Not nice to snip the traceback.
--
___
Python tracker
<https://bugs.python.org/issue41613>
___
___
Python-bugs-list mailin
Guido van Rossum added the comment:
Closing, this is out of date. EXACT_TOKEN_TYPES has been moved to token.py in
3.8 and is now automatically generated from Grammar/Tokens. 3.7 is too old to
fix.
--
nosy: +gvanrossum
resolution: -> out of date
stage: -> resolved
status
Guido van Rossum added the comment:
As you,can tell from thencode this by design. The child,must create a new event
loop explicitly,ifmitmwants to use asyncio, and all,existing Futures are off
limits.
Fork is dangerous. Don't use unless you understand it.
--
nosy: +gvanr
Change by Guido van Rossum :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue41616>
___
___
Python-bugs-list
Guido van Rossum added the comment:
I'm with Raymond. Closing.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Guido van Rossum added the comment:
New changeset 838316db08a8e3174e4cf8db233ff69d388b3f5c by Karthikeyan
Singaravelan in branch '3.8':
[3.8] bpo-41624: fix documentation of typing.Coroutine (GH-21952). (#21983)
https://github.com/python/cpyt
Guido van Rossum added the comment:
New changeset c01a7edc67e2c2e13a6d9513f111f27761786e27 by Karthikeyan
Singaravelan in branch '3.9':
[3.9] bpo-41624: fix documentation of typing.Coroutine (GH-21952) (#21982)
https://github.com/python/cpython/commit/c01a7edc67e2c2e13a6d9513f111f2
Change by Guido van Rossum :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Guido van Rossum :
--
resolution: -> works for me
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from Guido van Rossum :
I just noticed a subtle discrepancy between the old parser and the PEG parser.
Consider this syntax error:
```
if x {a}: pass
```
The old parser places the caret at the '{':
```
$ python3.8 -c 'if x { a } : pass'
File ""
Guido van Rossum added the comment:
I think it’s reasonable to expect sys.argv to have at least one item,
possibly empty. The proposed fix of setting it to [“”] seems right to me.
--
--Guido (mobile)
--
___
Python tracker
<https://bugs.python.
Guido van Rossum added the comment:
Something just occurred to me. What if the caller has already set
says.argv? We shouldn’t overwrite it. Or what if they only set it (later)
if not already set. Would we break their code?
--
--Guido (mobile
Guido van Rossum added the comment:
Got it.
On Sun, Aug 30, 2020 at 15:28 Terry J. Reedy wrote:
>
>
> Terry J. Reedy added the comment:
>
>
>
> sys.argv cannot be set until sys exists. As I mentioned above, subsequent
> calls before finalization must continue to
Guido van Rossum added the comment:
FWIW the PSF board approved the change.
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue39883>
___
___
2901 - 3000 of 5563 matches
Mail list logo