Braden Groom added the comment:
> In other words, the documentation looks sufficient to me as-is, and adding
> special wording for this would only make it longer than it should be.
I agree with Victor here. It seems like this can be closed. There haven't been
any comments from o
Braden Groom added the comment:
It seems like this can be closed unless we want to remove the current header in
argparse.py.
--
nosy: +bradengroom
___
Python tracker
<https://bugs.python.org/issue17
Change by Braden Groom :
--
pull_requests: +9523
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue16516>
___
___
Python-bugs-list mai
Braden Groom added the comment:
The file contents that you've provided aren't valid base64. I think the
traceback that you've received is a reasonable one.
--
nosy: +bradengroom
___
Python tracker
<https://bugs.pyt
Braden Groom added the comment:
Victor, FWIW I don't need this functionality and your suggestion on the PR
seems reasonable to me. I only picked up this issue as a way to become familiar
with contributing to the project. I'm okay with closing both the PR and the
ticket.
-
Braden Groom added the comment:
https://github.com/python/cpython/pull/10159
--
nosy: +bradengroom
___
Python tracker
<https://bugs.python.org/issue14
Change by Braden Groom :
--
pull_requests: +9481, 9482, 9483
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue14856>
___
___
Python-
Change by Braden Groom :
--
pull_requests: +9481, 9482
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue14856>
___
___
Python-bugs-lis
Change by Braden Groom :
--
pull_requests: +9481
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue14856>
___
___
Python-bugs-list mai
Braden Groom added the comment:
Ah. Thank you
--
___
Python tracker
<https://bugs.python.org/issue33710>
___
___
Python-bugs-list mailing list
Unsubscribe:
Braden Groom added the comment:
Thanks! I'll check out the linked PR. I've seen a few deprecation issues that I
couldn't pick up just because I wasn't clear on the deprecation process. Is
this documented anywhere in the development guides? I wasn't able to find it if
Change by Braden Groom :
--
pull_requests: +9450
stage: test needed -> patch review
___
Python tracker
<https://bugs.python.org/issue1154351>
___
___
Python-
Braden Groom added the comment:
What's the process for deprecating functions? Do we just start by adding a note
in the docs?
--
___
Python tracker
<https://bugs.python.org/is
Change by Braden Groom :
--
nosy: +bradengroom
___
Python tracker
<https://bugs.python.org/issue33710>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Braden Groom :
--
keywords: +patch
pull_requests: +9433
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34145>
___
___
Py
Braden Groom added the comment:
I agree with Paul. This is probably simple enough for applications to
implement. It also doesn't make sense to add either of these if the precedent
was set by rejecting DateTime previously.
--
___
Python tr
Braden Groom added the comment:
I could try adding JSON and YAML argument types if that's what we want to do.
--
nosy: +bradengroom
___
Python tracker
<https://bugs.python.org/is
Change by Braden Groom :
--
pull_requests: +9246
___
Python tracker
<https://bugs.python.org/issue32321>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Braden Groom :
--
keywords: +patch
pull_requests: +9234
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
19 matches
Mail list logo