Stefan Behnel added the comment:
And another patch update that should avoid any potential performance
regressions due to the additional type check.
--
Added file: http://bugs.python.org/file39119/fix_stopiteration_crash.patch
___
Python tracker
Changes by irdb dalba.w...@gmail.com:
--
nosy: +irdb
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16893
___
___
Python-bugs-list mailing list
Martin Panter added the comment:
In Issue 22468, I posted a patch which encourages using TarInfo directly, and
hopefully clarifies that gettarinfo() is only for OS files. I think that should
cover the documentation aspect of this bug, although an enhancement to
synthesize TarInfo objects for
Eric Snow added the comment:
Ionel Cristian Mărieș added the comment:
What exactly are you proposing? Getting rid of AttributeError masking?
That isn't really a practical thing to consider, so no. :) Instead
I'm suggesting there isn't a lot of justification to change the
behavior of
Martin Falatic added the comment:
FYI, I'm currently using calls into Tkinter to get more detailed version info.
Some methods work better than others... I've outlined my attempts below for
reference (the last tcl_ver and tk_ver outputs are the ones I'm using, even
though they are somewhat
Martin Panter added the comment:
Of course in a new release, the functions could actually grow support for
keywords, sidestepping the problem. Issue 8706 proposes to do this.
And see Issue 13386 about the conventions for optional arguments more generally.
--
Martin Panter added the comment:
I am posting a documentation patch which I hope should clarify that objects
like GzipFile won’t work automatically with gettarinfo(). It also has other
modifications to address Issue 21996 (name must be text) and help with Issue
22208 (clarify non-OS files
Ned Deily added the comment:
I am im favor of adding documentation for the existing tkinter TclVerion and
TkVersion attributes to the tkinter section of the Standard Library reference
as well as documenting a form of tkinter.Tcl().call('info', 'patchlevel')
and/or tkinter.Tk().call('info',
Eric Snow added the comment:
Ionel Cristian Mărieș added the comment:
It's not. Did you see the example with iter()/__iter__? It does convert
the AttributeError into a TypeError.
callable and iter are not the same thing though. callable checks for
a capability. iter invokes a capability.
Martin Panter added the comment:
See also Issue 23738, which identifies some functions whose documentation
already suggests they accept keywords. Perhaps these functions could be
prioritized.
Also, I think “version changed” notices should be added in the documentation
when a function grows
Martin Panter added the comment:
When a parameter is optional but does not have a simple default value, I
suggest using some obviously invalid pseudocode, such as
function(arg1, arg2=automatic, see text)
See Issue 8706 about adding more support for keyword arguments. See also Issue
23738 for
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +berker.peksag
resolution: fixed -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23994
___
Ionel Cristian Mărieș added the comment:
On Mon, Apr 20, 2015 at 2:59 AM, Eric Snow rep...@bugs.python.org wrote:
However, that is consistent across Python and has been this
way for a long time (so there are backward compatibility concerns that
cannot be ignored).
It's not. Did you see
Ryan Gonzalez added the comment:
That's the thing; my repo has no python.c!
On April 19, 2015 7:39:19 PM CDT, Cyd Haselton rep...@bugs.python.org wrote:
Cyd Haselton added the comment:
Ryan,
That fix is in the android_segfault patch, but it's for frozenmain.c
not python.c
I cloned from
Cyd Haselton added the comment:
Ryan,
That fix is in the android_segfault patch, but it's for frozenmain.c not
python.c
I cloned from master on Fri/Sat. Will double-check commit tomorrow but I think
the problem is with the unpatched python.c
--
Ionel Cristian Mărieș added the comment:
On Mon, Apr 20, 2015 at 2:59 AM, Eric Snow rep...@bugs.python.org wrote:
It not a problem currently for callable. It is one you are proposing
to introduce. It is one which current users of callable don't have to
worry about.
Were do we draw the
Martin Panter added the comment:
Over in Issue 22468, I posted a documentation patch which includes wording to
address this bug.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21996
___
Eric Snow added the comment:
Here's an updated patch, with the PEP 489 changes merged in. Only one test
isn't passing and it is due to something in the pip that is bundled into
ensurepip. I'll work on fixing that when I have some time. I'm sure there's
documentation near the bundle that
Eric Snow added the comment:
s/PEP 489/PEP 488/
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23911
___
___
Python-bugs-list mailing list
Martin Panter added the comment:
A test case for this that would trigger when memory debugging is enabled could
look something like the following. Would it be appropriate to add it to the
test suite?
a = bytearray(10)
size = sys.getsizeof(a)
a.pop() # Defeat expanding buffer off-by-one quirk
Guido van Rossum added the comment:
Uh, wait. Who's patching anything? That breaks the warranty.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24004
___
Terry J. Reedy added the comment:
Ned, I was indeed thinking of creating the string upon startup.
Martin: Works, using ? using what?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23982
Raymond Hettinger added the comment:
I'll add James' suggested wording, but with the reversed-order suggested by
David Murray.
--
assignee: docs@python - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
Raymond Hettinger added the comment:
Unless there are some serious objections, I propose to close this on the basis
of practicality beats purity (and as David Murray noted, there may not be a
pure answer). Eric Snow's comments are dead-on.
AFAICT, there isn't a real problem here and the API
Raymond Hettinger added the comment:
Please don't add a new notation that makes the docs less readable than they are
now. For the most part, the existing docs have done a great job communicating
how to use our functions. Please don't undo 20 years of tradition because it
bugs you.
Raymond Hettinger added the comment:
Skip or Barry, do you want to look at this?
--
assignee: - skip.montanaro
nosy: +skip.montanaro
stage: needs patch - patch review
versions: -Python 3.3
___
Python tracker rep...@bugs.python.org
Mauro Rodrigues added the comment:
Hi guys!
Here is a patch for the fileinput module, with some names beyond
fileinput.fileno: fileinput.hook_compressed, fileinput.hook_encoded as
mentioned in the docs https://docs.python.org/3/library/fileinput.html
This is my first patch as well, so
Georg Brandl added the comment:
Yeah, agreed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24005
___
___
Python-bugs-list mailing list
Tim Golden added the comment:
(Laughs). I admit, I was so close to the trees, I missed the fact that
the doc is, as you say, a What's New, and for Python 2.4. Agree that to
change this now would be somewhat ludicrous.
If some similar patch were proposed to some more current, relevant
Siegfried Gevatter added the comment:
Thomas, could you take another look? I did update the patch.
Thanks! :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12606
___
Serhiy Storchaka added the comment:
Supporting keyword arguments has performance loss. For fast builtins it make be
significant. We should defer adding keyword arguments support until more
efficient parsing will implemented. Note that it is easier to implement
efficient argument parsing for
Ilia Kurenkov added the comment:
As my contribution during the sprints at PyCon 2015, I've tweaked Jervis's
patch a little and updated the tests/docs to work with Python 3.5.
My only real change was placing the basic reader object inside a generator
expression that filters out empty lines.
Serhiy Storchaka added the comment:
Actually it is not hard to me to apply the patch locally and regenerate clinic
output if I need it. I propose this patch for mainstream only because think
that it can be helpful for someone other. Thanks to moving all generated code
into separated files,
Serhiy Storchaka added the comment:
I were aware that this can propagate some not well appropriate docstrings from
abstract base classes, but Martin expose worse problem: inheriting a docstring
by the method with changed signature.
Perhaps we should check if a signature of overriding method
Mert Bora Alper added the comment:
I think this was just overlooked when implementing argparse. Most code out
there is likely to get the executable name using:
os.path.basename(sys.argv[0])
Which is going to do exactly what you are seeing here when sys.argv[0] ends
with a /.
feel
Brett Cannon added the comment:
LGTM
--
assignee: - christian.heimes
nosy: +brett.cannon
stage: patch review - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23998
___
101 - 136 of 136 matches
Mail list logo