Raymond Hettinger added the comment:
this is well formed xml and has nothing to do with tail.
In fact, it does have something to do with tail.
The 'TEXT' is a captured as the tail of element b:
root3 = ET.fromstring('ab/TEXT/a')
root3[0].tail
'TEXT'
--
nosy: +eli.bendersky,
Tim Golden added the comment:
Jaivish Kothari,
Thanks for making the effort to contribute. Can I suggest you have a
look at the Core Mentorship site:
http://pythonmentors.com/
and perhaps join the Core Mentorship list:
http://mail.python.org/mailman/listinfo/core-mentorship
TJG
Stefan Behnel added the comment:
I agree that the wording in the documentation isn't great:
text
The text attribute can be used to hold additional data associated with the
element. As the name implies this attribute is usually a string but may be any
application-specific object. If the
Changes by Claudiu Popa pcmantic...@gmail.com:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21423
___
___
Changes by Claudiu Popa pcmantic...@gmail.com:
--
nosy: +Claudiu.Popa
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21423
___
___
Python-bugs-list
Claudiu Popa added the comment:
Hello,
Can anyone review the last patch? Hopefully it is the final version, since the
beta is really at the corner and I definitely would like to have this in 3.5.
--
___
Python tracker rep...@bugs.python.org
Eric Reynolds added the comment:
In the meantime here is a workaround
https://gist.github.com/ericremoreynolds/2d80300dabc70eebc790
--
nosy: +ericreynolds
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4356
Jérôme Laurens added the comment:
Since the text and tail notions seem tightly coupled, I would vote for a more
detailed explanation in the text doc and a forward link in the tail
documentation.
text
The text attribute holds the text between the element's begin tag and the
next tag or
Roundup Robot added the comment:
New changeset 661cdbd617b8 by Raymond Hettinger in branch 'default':
Issue #23910: Optimize property() getter calls. Patch by Joe Jevnik
https://hg.python.org/cpython/rev/661cdbd617b8
--
nosy: +python-dev
___
Python
New submission from Petr Viktorin:
A note in the docs for the u format unit saus NULs are not allowed, but the
previous sentence says they aren't accepted.
--
assignee: docs@python
components: Documentation
files: 0002-Remove-obsolete-note-in-argument-parsing-docs.patch
keywords: patch
Changes by A. Jesse Jiryu Davis je...@emptysquare.net:
--
nosy: +emptysquare
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10544
___
___
New submission from Matt Johnston:
asyncio.Event.wait() doesn't seem to be cancelled by asyncio.wait_for(). Ctrl-c
in the attached example produces output below. I'm not certain the code is
correct though the documentation for wait_for() suggests it should work.
Without the wait_for() it
New submission from Petr Viktorin:
imp.reload() and importlib.reload() docs state::
If a module is syntactically correct but its initialization fails, the first
:keyword:`import` statement for it does not bind its name locally, but does
store a (partially initialized) module object
Jérôme Laurens added the comment:
Erratum
def innertext(elt):
return (elt.text or '') +''.join(innertext(e)+(e.tail or '') for e in elt)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24079
R. David Murray added the comment:
Not to my eyes. It clearly says that if no formatting string is specified, the
default is used, and that formatTime is used only if the message string
contains asctime. Up to Vinay whether he thinks it is worth adding something
like which does not include
Jérôme Laurens added the comment:
The totsstring(..., method='text') is not suitable for the inner text because
it adds the tail of the top element.
A proper implementation would be
def innertext(elt):
return (elt.text or '') +''.join(innertext(e)+e.tail for e in elt)
that can be
New submission from Buck Evan:
In the attached example I show that there's a significant memory overhead
present whenever a pre-compiled pyc is not present.
This only occurs with more than 5225 objects (dictionaries in this case)
allocated. At 13756 objects, the mysterious pyc overhead is 50%
New submission from Paul Moore:
Although the new generator methods introduced in PEP 342 are documented, the
term coroutine is not defined anywhere. In particular, the fact that Python
coroutines work in conjunction with an event loop rather than transferring
control directly between each
Marco Paolini added the comment:
KeyboardInterrupt is not handled gently by asyncio (see
https://groups.google.com/d/msg/python-tulip/sovg7EIBoXs/m7U-0UXqzSQJ)
you could cancel all tasks in the signal handler:
...
def sig_interrupt():
print('interrupt')
for task in
Vinay Sajip added the comment:
Perhaps I'll just change it to say
... the default value of '%(message)s' is used, which just includes the message
in the logging call. To have additional items of information in the formatted
output (such as a timestamp), see other placeholder variables ...
Buck Evan added the comment:
Also, we've reproduced this in both linux and osx.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24085
___
___
Martijn Pieters added the comment:
I'd be happy to provide a patch for the DictWriter.writerows code; I was
naively counting on it accepting an iterable and that it would not pull the
whole sequence into memory (while feeding it gigabytes of CSV data).
--
nosy: +mjpieters
Antoine Pitrou added the comment:
This is transitory memory consumption. Once the source is compiled to bytecode,
memory consumption falls down to its previous level. Do you care that much
about it?
--
nosy: +pitrou
___
Python tracker
New submission from Trevor Bekolay:
I was having an issue installing a package in Python 3, which installed
properly in Python 2. This is the error message I got:
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
... snip unhelpful traceback
New submission from SpaceOne:
Just add an argument with metavar='[PROTOCOL://]HOST[:PORT]' ([...] twice in
the string) causes the following traceback:
Traceback (most recent call last):
File curl.py, line 182, in module
arguments = parser.parse_args()
File
Łukasz Langa added the comment:
Agreed that this can be addressed now for Python 3.5.
--
assignee: - lukasz.langa
versions: +Python 3.5 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2651
Anthony Sottile added the comment:
Adding `import gc; gc.collect()` doesn't change the outcome afaict
--
nosy: +asottile
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24085
___
Raymond Hettinger added the comment:
Marking as rejected because 0 works fine and accepting None just complicates
the parsing and documentation without any incremental benefit.
--
resolution: - rejected
status: open - closed
___
Python tracker
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23572
___
___
Jaivish Kothari added the comment:
Thank you Tim.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24005
___
___
Python-bugs-list mailing list
Changes by Ned Deily n...@acm.org:
--
nosy: +lukasz.langa
versions: +Python 3.5 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24086
___
Guido van Rossum added the comment:
You can't just drop the middle sentence. Awkward though it is, it is attempting
to describe that the generator object controls suspension and resumption of the
stack frame representing execution of the generator function's body.
--
Mark Lawrence added the comment:
List of just about everything that's in the header file but not in the rst file
as I'm not sure which bits you normally wouldn't bother with.
Py_USING_UNICODE
Py_UNICODE_SIZE
Py_UNICODE_WIDE
Py_UNICODE_COPY
Py_UNICODE_FILL
Py_UNICODE_HIGH_SURROGATE
Łukasz Langa added the comment:
This is expected behaviour but I agree the error message should be improved.
There are people using interpolation in .pypirc, if you don't want that, just
use a double % sign and it will do the right thing. You don't have to change
your password.
I'll leave
Changes by Ned Deily n...@acm.org:
--
nosy: +georg.brandl
stage: - patch review
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24084
___
Łukasz Langa added the comment:
Yes, this needs addressing.
--
assignee: - lukasz.langa
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23572
___
New submission from Jim Jewett:
https://docs.python.org/3/reference/expressions.html#yield-expressions
Current:
When a generator function is called, it returns an iterator known as a
generator. That generator then controls the execution of a generator function.
The execution starts when one
Antoine Pitrou added the comment:
It seems we (like the benchmarks posted) are spending a whole lot of time on
something that's probably not relevant to any real-world situation.
If someone has actual code that suffers from this, it would be good to know
about it.
(note by the way that
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23910
___
Marc-Andre Lemburg added the comment:
I checked the registry to find the correct root. This would be
Software\Microsoft\VisualStudio\.
However, VC 9.0 no longer seems to set the variables the method is looking for,
so even if the .__root attribute problem gets fixed, the method would not find
New submission from Marc-Andre Lemburg:
Trying to use .get_msvc_path() on an distutils.msvccompiler.MSVCCompiler()
instance raises an AttributeError:
MSVCCompiler instance has no attribute '_MSVCCompiler__root'
The reason seems to be that self.__root is not set for Win x64 in .__init__().
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +brett.cannon, eric.snow, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24081
___
R. David Murray added the comment:
Printing the actual value feels more consistent with the documented API, so I'm
in favor of that (ie: don't let errors pass silently). I'm sure someone
somewhere is depending on this :(, but I see you have versions marked for 3.5
only, which makes sense to
R. David Murray added the comment:
Per the discussion in issue 5845, I'm setting this to release blocker to make
sure it gets committed before the next release. I'm also adding 3.4 as I think
this is a bug. Any objections to that?
--
nosy: +larry
priority: normal - release blocker
New submission from Romuald Brunet:
When running pstats with functions that take less than 0.5 millisecond (per
call for example), the value shown is '0.000, which isn't really helpful.
This patch aims to show the value in microseconds instead of seconds for values
that would otherwise be
45 matches
Mail list logo