Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21197
___
___
Python-bugs-list
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21171
___
___
Python-bugs-list
Changes by Éric Araujo mer...@netwok.org:
--
assignee: - lukasz.langa
nosy: +lukasz.langa
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21186
___
Éric Araujo added the comment:
Thanks for the report.
If the python.org links can be found in the Internet Archive, then one could
find the new addresses to use by looking for the same message on
http://www.python.org/pipermail/python-dev/2000-March/
Would you be willing to try that?
Éric Araujo added the comment:
Thanks for the report. Is it an issue in the docstrings, the HTML
documentation or both?
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21198
Xavier de Gaye added the comment:
FWIW this generator expression can be evaluated with the 'interact' command:
--Return--
/test/comprehension.py(5)foo()-None
- pdb.set_trace()
(Pdb) interact
*interactive*
all(x limit for x in items)
True
(Pdb)
--
nosy: +xdegaye
Matthias Dahl added the comment:
@vinay.sajip: No problem. Jedi is a auto-completion library. It does not add
any links anywhere. It naturally has to know about which venvs you use so it
can find all modules and their sources to process them. Thus, you (or the
implementation using Jedi) pass
Ontje Lünsdorf added the comment:
I think there may be a bug in doctest which is getting exposed by Python 3.4
new handling of reference cycles. I've attached a simpler example with a global
variable.
There's no error if you run the code directly, the global variable still exists
during the
Xavier de Gaye added the comment:
The runcode() method of InteractiveInterpreter in code.py uses the
'self.locals' dictionary as the 'globals' parameter of the invoked exec()
function. And the do_interact() method of Pdb instantiates
InteractiveInterpreter with 'locals' as a merge of the
Changes by Florent Xicluna florent.xicl...@gmail.com:
--
nosy: +flox
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21202
___
___
Python-bugs-list
Jurko Gospodnetić added the comment:
Thanks for looking into this Xavier.
Could someone reopen this issue so it can gets looked at again?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21161
Changes by mk mige...@gmail.com:
--
nosy: +migel.k
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15716
___
___
Python-bugs-list mailing list
New submission from Szieberth Ádám:
I faced this particular issue by writing decorators for asyncio coroutines.
I even posted a question to SO:
http://stackoverflow.com/questions/23015626/how-to-decorate-an-asyncio-coroutine-to-retain-its-name
However, since that I realized the problem is
Richard Oudkerk added the comment:
I added some comments.
Your problem with lost data may be caused by the fact you call ov.cancel() and
expect ov.pending to tell you whether the write has/will succeed. Instead you
should use ov.getresult() and expect either success or an aborted error.
New submission from Ram Rachum:
Otherwise people could MITM our passwords.
--
components: Demos and Tools
messages: 215970
nosy: cool-RR
priority: normal
severity: normal
status: open
title: Provide legit HTTPS certificate for http://bugs.python.org/, redirect
HTTP to HTTPS
Changes by Mark Dickinson dicki...@gmail.com:
--
assignee: docs@python - mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20624
___
Changes by Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de:
--
nosy: +wolma
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21204
___
___
Eric Snow added the comment:
After pulling up to tip and sticking in the basic **kwargs change, the results
on the benchmark suite imply a refleak somewhere. As soon as I sort that out
I'll push up the updated patch.
--
___
Python tracker
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16991
___
___
Python-bugs-list
Mark Dickinson added the comment:
Adding Brian Quinlan to the nosy list.
I don't see an easy way around this other than documenting it and recommending
that people do explicit executor shutdown where necessary.
Weakref callbacks are dangerous things. Weakref callbacks that acquire a lock
at
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21204
___
___
Python-bugs-list
Changes by Eric V. Smith e...@trueblade.com:
--
assignee: eric.smith - docs@python
nosy: +docs@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7951
___
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20128
___
___
Python-bugs-list mailing
Changes by koobs koobs.free...@gmail.com:
--
nosy: +koobs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20123
___
___
Python-bugs-list mailing
New submission from Steven Hiscocks:
I've seen an issue with using urandom on Python 3.4. I've traced down to fd
being closed (not by core CPython, but by third party library code). After
this, access to urandom fails.
I assume this is related to persistent fd for urandom in
Ned Deily added the comment:
Please report issues with bugs.python.org to its issue tracker (Help - Report
Tracker Problem): http://psf.upfronthosting.co.za/roundup/meta/
--
nosy: +ned.deily
resolution: - invalid
stage: - committed/rejected
status: open - closed
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21207
___
___
Python-bugs-list
R. David Murray added the comment:
This issue should have gone back to being a release blocker after the alpha
release to fix the tab-as-indent issue, but obviously that didn't happen (I
forgot about it myself). Please open a new issue requesting a fix for this bug
(that tab doesn't work as
R. David Murray added the comment:
Can you suggest how to improve the docs?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20010
___
___
Aaron Meurer added the comment:
Nowhere at https://docs.python.org/3.5/library/time.html#time.strftime is it
indicated that %z behaves differently on different platforms. What it *does*
say is
%z Time zone offset indicating a positive or negative time difference from
UTC/GMT of the form
Aaron Meurer added the comment:
I also just noticed that the %z entry in the table wasn't added until the
Python 3.3 docs, although it apparently works at least in OS X in Python 2.7 (I
can't test Windows right now). Was it supposed to be one of the additional
directives supported on certain
Changes by Nikolaus Rath nikol...@rath.org:
Added file: http://bugs.python.org/file34792/issue15955_r3.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15955
___
Nikolaus Rath added the comment:
Seems as if no one has an opinion on this at all:
https://mail.python.org/pipermail/python-dev/2014-April/133739.html
What next?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20578
Chris Angelico added the comment:
I agree that current behaviour is a bit confusing; also, the implication is
that deleting from the dictionary while you have an iterator may leave some
hanging references around the place, which raises a red flag in my mind (maybe
something else might find
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
nosy: +belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19414
___
___
Antoine Pitrou added the comment:
Well, if a third-party library decides to close fds it doesn't own, that
library should have a bug reported to it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21207
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21169
___
___
Steven Hiscocks added the comment:
I agree in part, but it's quite common to close fd's in some cases like in a
child process after using os.fork(). There is no way, as far as I'm aware, to
identify which fd is associated with /dev/urandom to keep it open; or anyway to
reopen it such that
New submission from Karl Richter:
As arguments with type bool are the only ones whose values can be manipulated
without passing an option to the argument on CLI, the default behavior for
those should be changed from ignoring options to failing when options are
specified. Consider the
Martin v. Löwis added the comment:
I put some review into rietveld. In addition, please avoid code duplication of
more than three subsequent lines of code.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20578
Martin v. Löwis added the comment:
Nikolaus, can you please restate from scratch what the issue is? If the issue
is still the one you posed in msg214776, I think the issue should be closed as
invalid - it's *not* the case that there is no good reason for TextIOWrapper
not accepting any
Karl Richter added the comment:
I've been mistaken about the behavior if no argument is specified (then the
argument value is None), so this is a bug!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21208
Nikolaus Rath added the comment:
My usecase is that I have a binary stream class that internally uses
memoryviews. I would like to read text data from this stream and thus
encapsulate it in a TextIOWrapper. Currently, TextIOWrapper (correctly) expects
read() to return bytes and fails if it
Nikolaus Rath added the comment:
Thanks for the review! Attached is a new patch. I was actually pretty careful
to avoid any code duplication.. are you refering to the readinto1()
implementations for BytesIO and BufferedReader in Lib/_pyio.py?
--
Added file:
Martin v. Löwis added the comment:
Put up a new review.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20578
___
___
Python-bugs-list mailing
Josiah Carlson added the comment:
No, the problem is that that ov.cancel() will attempt to cancel the IO, but a
subsequent ov.getresult(True) doesn't always return what was *actually* written
to the pipe unless you explicitly wait for the result to be available. But even
if you explicitly
New submission from Richard Kiss:
import asyncio
import os
def t1(q):
yield from asyncio.sleep(0.5)
q.put_nowait((0, 1, 2, 3, 4, 5))
def t2(q):
v = yield from q.get()
print(v)
q = asyncio.Queue()
asyncio.get_event_loop().run_until_complete(asyncio.wait([t1(q), t2(q)]))
When
Josh Rosenberg added the comment:
If your goal is to get a boolean on/off switch, that's what action='store_true'
is for. You don't need to specify nargs or type at all; using bool as the type
means it wants an argument, and will pass the string form of the argument to
the bool constructor;
Richard Kiss added the comment:
For a reason that I don't understand, this patch to asyncio fixes the problem:
--- a/asyncio/tasks.py Mon Mar 31 11:31:16 2014 -0700
+++ b/asyncio/tasks.py Sat Apr 12 20:37:02 2014 -0700
@@ -49,7 +49,8 @@
def __next__(self):
return next(self.gen)
R. David Murray added the comment:
Testing the documentation examples is a long term goal, which people
occasionally contribute to. I think there is an open issue about using the
Sphinx doctest support, that for a long time was blocked by the documentation
tool chain not using python3. Some
R. David Murray added the comment:
I think this is a specific case of a more general need to improve 'wraps' that
was discussed on python-dev not too long ago.
--
nosy: +r.david.murray
versions: +Python 3.5 -Python 3.4
___
Python tracker
R. David Murray added the comment:
Yeah, this is a bit non-obvious, but it is a specific instance of the general
way that argparse handles types. So as far as I can see there really isn't
anything to do here.
--
nosy: +r.david.murray
resolution: - invalid
stage: -
52 matches
Mail list logo