Antoine Pitrou added the comment:
This is indeed the case. And the solution is obvious: call dumps() and then
write() the result yourself. If dump() used _one_shot=True, it would defeat the
purpose of minimizing memory consumption by not buffering the whole result.
--
assignee
New submission from Antoine Pitrou :
Also, *please* provide stderr in the error message when an external command
fails. Otherwise, it's impossible to properly debug failure of external
commands.
==
ERROR: test_buil
Antoine Pitrou added the comment:
Many other failures in
http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/4630/steps/test/logs/stdio
, by the way
--
___
Python tracker
<http://bugs.python.org/issue12
Antoine Pitrou added the comment:
Victor, you broke the Solaris gcc buildbot on 2.7.
http://www.python.org/dev/buildbot/all/builders/sparc%20solaris10%20gcc%202.7/builds/837
--
assignee: -> haypo
stage: patch review -> committed/rejected
status: closed -
Antoine Pitrou added the comment:
The request is reasonable, but the best bet is for someone interested to
provide a patch. See http://docs.python.org/devguide/ if you aren't acquainted
with the development process.
--
components: +Library (Lib)
nosy: +pitrou
stage: -> nee
Changes by Antoine Pitrou :
Removed file: http://bugs.python.org/file22050/unnamed
___
Python tracker
<http://bugs.python.org/issue12107>
___
___
Python-bugs-list mailin
Antoine Pitrou added the comment:
> It makes sense to bring this up for discussion on pydev, then.
Ok, done.
> In the meantime, is there an objection to removing the incorrect
> statement Jean-Paul mentioned from the doc?
Well, no.
--
_
Antoine Pitrou added the comment:
Patch looks ok. Is 3.x also affected? The I/O stack changed quite a bit in 3.x.
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue1441
New submission from Antoine Pitrou :
==
ERROR: test_output (test.test_logging.HTTPHandlerTest)
--
Traceback (most recent call last):
File "/home2/bui
New submission from Antoine Pitrou :
This is probably a transient failure due to the remote host being unavailable,
but the "bad file descriptor" error is not ok:
test test_urllibnet failed -- Traceback (most recent call last):
File
"/Users/pythonbuildbot/buildarea/3.x.hanse
New submission from Antoine Pitrou :
The code I added in b65f417dd266 is buggy, because it calls __exit__ with
(None, None, None) rather than the exception to be tested.
--
assignee: pitrou
components: Tests
messages: 136456
nosy: pitrou
priority: normal
severity: normal
stage: needs
Antoine Pitrou added the comment:
Specifically, the "spawn" function *must* be fixed to include stderr in the
exception message.
--
___
Python tracker
<http://bugs.python.o
Antoine Pitrou added the comment:
> This can be useful to take advantage of firewalls that know how to
> handle NAT with non-secure FTP without opening fixed ports.
Can you explain this a little more?
+resp = self.voidcmd('CCC')
+self.sock =
Antoine Pitrou added the comment:
Same request for distutils in issue11599, by the way.
--
___
Python tracker
<http://bugs.python.org/issue12135>
___
___
Pytho
Antoine Pitrou added the comment:
What's the difference with issue12132?
--
___
Python tracker
<http://bugs.python.org/issue12141>
___
___
Python-bugs-list m
Antoine Pitrou added the comment:
> Oops. It's a duplicate. Keeping this one since the problem was
> narrowed to multiprocessing/sys,executable and sysconfig
I don't think it has anything to do with sys.executable. As the other
issue says, it seems the test (or packaging/sysc
Antoine Pitrou added the comment:
> Because sys.executable (argv[0] in fact) is not filled when you call
> multiprocess vvia the -j option.
sys.executable is set perfectly well when running regrtest in
multiprocess mode, otherwise many other tests would fail.
Try:
$ grep "sys.exec
Changes by Antoine Pitrou :
--
nosy: +charles-francois.natali, rosslagerwall
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue6
Antoine Pitrou added the comment:
Committed in r86498.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Antoine Pitrou added the comment:
This looks ok to me.
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue9518>
___
___
Python-bugs-list mailin
Antoine Pitrou added the comment:
> Did you convert the project using make_perf3.sh?
Yes. But given the error (SystemError) I guess this is a regression in
py3k. I'll apply your patch and open a separate issue to try and make
sense of the re
Changes by Antoine Pitrou :
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue10384>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
Y:\>py3k\__svn__\PCbuild\amd64\python_d.exe -m test.regrtest -v
test_concurrent_futures
== CPython 3.2a4+ (py3k, Nov 18 2010, 11:12:09) [MSC v.1500 64 bit (AMD64)]
== Windows-7-6.1.7600 little-endian
== Y:\py3k\__svn__\build\test_python_2016
[
Changes by Antoine Pitrou :
--
nosy: +facundobatista, georg.brandl
___
Python tracker
<http://bugs.python.org/issue10351>
___
___
Python-bugs-list mailin
Antoine Pitrou added the comment:
> The best that could be done is to provide a configuration option (e.g.
> global variable) that should be treated as a default value, and then
> leave it to people distributing Python to fill out this variable in a
> sensible way.
Actually, Ope
Antoine Pitrou added the comment:
> > This may not be satisfying to users. For example, our Windows
> > distribution doesn't ship with any certicates (AFAIK); I have no
> > clue where exactly OpenSSL would be looking for them, either.
> > People worried about this
Antoine Pitrou added the comment:
Then I get more failures:
==
FAIL: test_map_timeout (test.test_concurrent_futures.ProcessPoolExecutorTest)
--
Traceback
Antoine Pitrou added the comment:
> Could you try with the patch that I just attached? And thanks for you
> help, I really appreciated it!
It works ok indeed.
--
___
Python tracker
<http://bugs.python.org/i
Antoine Pitrou added the comment:
> Sorry again for another epic-length comment...
>
> I'm attaching the latest work-in-progress on this.
If this a work in progress, you could create an SVN branch in the
sandbox (you can then use svnmerge to avoid diverging too much from
main
Changes by Antoine Pitrou :
--
nosy: +brian.curtin, loewis, tim.golden
___
Python tracker
<http://bugs.python.org/issue10469>
___
___
Python-bugs-list mailin
Antoine Pitrou added the comment:
The core problem seems to be that the errno module has mismatching values on
your Python build (for ECONNREFUSED and EWOULDBLOCK, at least, which explains
all 4 failures). On a Windows 7 VM here:
>>> errno.ECONNREFUSED
10061
>>> errno
Changes by Antoine Pitrou :
--
nosy: +amaury.forgeotdarc
___
Python tracker
<http://bugs.python.org/issue10469>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Antoine Pitrou :
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue9435>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
Done in r86602.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
Antoine Pitrou added the comment:
Fixed in r86607, thanks.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 3.2
___
Python tracker
<http://bugs.python.or
Antoine Pitrou added the comment:
Patch committed in r86610, thank you!
--
nosy: +pitrou
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
Antoine Pitrou added the comment:
I can't reproduce anymore (Debian 5.0.6). Barry?
--
status: open -> pending
___
Python tracker
<http://bugs.python.or
Antoine Pitrou added the comment:
Pushed in 40e80cede832, thank you.
(2to3'ed Mako appears 3x slower than on 2x, but it's not obvious whether it's
Python 3 itself or the constructs added by 2to3; I think running 2to3ed
benchmarks is a bit pointless in itself, because it'
Antoine Pitrou added the comment:
Martin,
> You misunderstood. I was not proposing that scripts provide a CA
> list, but that users might deploy a CA list into their Python
> installation, which is then picked up in the same way as you are asking
> for on Ubuntu.
Could you elabo
Antoine Pitrou added the comment:
> > Having applications/scripts explicitly opt-in to a default CA
> > certificate list would be an option (then making those applications
> > break in installations where the default CA list is empty).
>
> "Errors should never pa
Changes by Antoine Pitrou :
--
nosy: +exarkun
___
Python tracker
<http://bugs.python.org/issue7995>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
Oh, and a test should be added of course.
--
___
Python tracker
<http://bugs.python.org/issue7995>
___
___
Python-bugs-list m
Antoine Pitrou added the comment:
It seems to me that it's a reasonable request. There is indeed a bug, since
Python uses non-blocking sockets to implement its "timeout" feature, and flags
inheritance means Python's view of whether the socket is non-blocking is not in
Antoine Pitrou added the comment:
nh2, your issue looks slightly different. In any case, can you tell us what
your system is, and post a simple script to reproduce the issue?
--
___
Python tracker
<http://bugs.python.org/issue1
Antoine Pitrou added the comment:
> Fine.
> So if not in the ssl module what about for urllib etc.?
The same answer really... We can't change default settings without
breaking compatibility.
--
___
Python tracker
<http://bugs.python.
Changes by Antoine Pitrou :
--
nosy: -db
___
Python tracker
<http://bugs.python.org/issue10441>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Antoine Pitrou :
--
resolution: rejected ->
stage: needs patch ->
status: closed -> open
___
Python tracker
<http://bugs.python.or
Antoine Pitrou added the comment:
Wow. The lock is precisely there so that the buffered object doesn't have to be
MT-safe or reentrant. It doesn't seem reasonable to attempt to restore the file
to a "stable" state in the middle of an inner routine.
Also, the outer
Changes by Antoine Pitrou :
--
nosy: +facundobatista, fdrake, orsenthil
versions: +Python 3.1
___
Python tracker
<http://bugs.python.org/issue10479>
___
___
Pytho
Changes by Antoine Pitrou :
--
nosy: +facundobatista, fdrake, orsenthil
___
Python tracker
<http://bugs.python.org/issue10486>
___
___
Python-bugs-list mailin
Changes by Antoine Pitrou :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue10491>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Antoine Pitrou :
--
nosy: +facundobatista, fdrake, orsenthil
___
Python tracker
<http://bugs.python.org/issue10485>
___
___
Python-bugs-list mailin
Changes by Antoine Pitrou :
--
nosy: +facundobatista, fdrake, orsenthil
versions: +Python 3.1
___
Python tracker
<http://bugs.python.org/issue10484>
___
___
Pytho
Changes by Antoine Pitrou :
--
nosy: +facundobatista, fdrake, orsenthil
type: behavior -> feature request
versions: -Python 2.6, Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/issu
Changes by Antoine Pitrou :
--
nosy: +gregory.p.smith
___
Python tracker
<http://bugs.python.org/issue10478>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Antoine Pitrou :
$ LANG=ISO-8859-15 ./python -m test.regrtest test_doctest
[1/1] test_doctest
**
File "/home/antoine/py3k/__svn__/Lib/test/test_doctest.py", line 1676, in
test.test_doctest.test_de
Antoine Pitrou added the comment:
> > Anyway, my personal opinion is that we should consider the current
> > behavior a bug and fix it. I like the idea of setting all accepted
> > sockets to blocking mode (and documenting it clearly).
>
> -1.
>
> > I think it
Antoine Pitrou added the comment:
Le dimanche 21 novembre 2010 à 20:16 +, Martin v. Löwis a écrit :
>
> > We are talking about the timeout feature, which is a Python feature, not
> > a BSD (or Linux) sockets feature. It should work properly, even if that
> > means ad
Changes by Antoine Pitrou :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue10493>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
Well if WeakKeyDictionary silences the TypeError from ref(), it sounds
consistent for WeakSet to silence it too.
--
___
Python tracker
<http://bugs.python.org/issue10
Antoine Pitrou added the comment:
> The notes in the documentation under socket.gettimeout() do go into
> more detail than elsewhere. But at least one thing there is at best
> misleading: "Sockets are always created in blocking mode" is, as we've
> seen, not corr
Antoine Pitrou added the comment:
> > Well, unless someone explains convincingly how the current behaviour is
> > desireable (rather than misleading and useless), I really think this is
> > a bug that should be fix (then we can also discuss what the fix should
> > exa
Antoine Pitrou added the comment:
> Worthwhile trade?
+1 obviously.
Why don't you contribute a list sorting benchmark to the suite in
http://hg.python.org/benchmarks/?
--
___
Python tracker
<http://bugs.python.or
Antoine Pitrou added the comment:
Le mardi 23 novembre 2010 à 00:10 +, Daniel Stutzbach a écrit :
> Daniel Stutzbach added the comment:
>
> Antoine Pitrou wrote:
> > Why don't you contribute a list sorting benchmark to the suite in
> > http://hg.python.org/benc
Antoine Pitrou added the comment:
> The Rietveld issue is here:
> http://codereview.appspot.com/3269041
>
> I ended up loading my incremental patches in, but it's easy enough to
> diff the base with the last patch. If for some reasons it doesn't
> work as convenien
Antoine Pitrou added the comment:
> > I ended up loading my incremental patches in, but it's easy enough to
> > diff the base with the last patch. If for some reasons it doesn't
> > work as conveniently as I expect, let me know and I will upload it to
> &g
Antoine Pitrou added the comment:
> My original patch was much more focused, but had a slightly larger
> performance penalty for sorting random keys (see
> http://bugs.python.org/msg122178). Do you think the performance
> tradeoff there was still worthwhile?
I am not objecting
New submission from Antoine Pitrou :
It was just resting. Here is a patch to wake it up for 3.2 (or 3.3 pending
moratorium interpretation).
As for the py3k warning in 2.x (and the 2to3 fixer), it's not obvious what we
should do: callable() clearly doesn't exist in 3
Changes by Antoine Pitrou :
--
nosy: +rhettinger, stutzbach
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue10519>
___
___
Pytho
Changes by Antoine Pitrou :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue10520>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Antoine Pitrou :
This has just occurred on the Solaris buildbot:
test_telnetlib
Exception in thread Thread-452:
Traceback (most recent call last):
File "/home2/buildbot/slave/2.7.loewis-sun/build/Lib/threading.py", line 530,
in __bootstrap_inner
self.ru
Antoine Pitrou added the comment:
The question is, what should it do with such an input? Pretend it's a single
char (but other chars in the source string won't get the same treatment)? Treat
it as a two-char string (but then center() and friends should logically be
extended to acce
Antoine Pitrou added the comment:
> I'm with Ezio here. I'm -1 for callable(), +0 for iscallable() (there
> should be preferably one obvious way to do it and using isinstance()
> seems to be that way at this point).
The thing is, "isisinstance(x, collections.Callabl
Antoine Pitrou added the comment:
Mandriva and Debian also work fine with both "UTF8" and "UTF-8". For the
record, the canonical spelling inside /usr/share/locale is "UTF-8". I suppose
glibc does its own normalization.
--
nosy: +pitrou
Changes by Antoine Pitrou :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue10538>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
`make coverage` is fine, you just have to use the "-m test.regrtest" form when
running the tests.
--
nosy: +pitrou
resolution: -> invalid
status: open -> pending
___
Python tracker
<htt
Antoine Pitrou added the comment:
Here is a patch raising RuntimeError on reentrant calls to a buffered object. I
haven't touched _pyio; I wonder how to do it without making it even slower.
--
keywords: +patch
Added file: http://bugs.python.org/file19841/reentrantio.
Changes by Antoine Pitrou :
--
stage: -> patch review
versions: +Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/issue10478>
___
___
Python-
Antoine Pitrou added the comment:
> It might be not "obvious", but it's consistent with the check for other
> attributes.
I don't know what attributes you're talking about, and there doesn't seem to be
a lot of consistency there.
Besides, being consiste
Antoine Pitrou added the comment:
Committed in r86842.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Antoine Pitrou :
--
nosy: +barry, skrah
___
Python tracker
<http://bugs.python.org/issue10555>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
Le samedi 27 novembre 2010 à 22:23 +, SilentGhost a écrit :
> SilentGhost added the comment:
>
> I thought PEP 3003 was quite unambiguous:
The stated goal of the moratorium is to make it easier for alternate
implementations to catch up with th
Antoine Pitrou added the comment:
> I thought that moratorium meant Guido dis/approval is not applicable to the
> 3.2
Guido can decide of everything: PEPs, etc. That's what "BDFL" means.
So he can also decide of exceptions to the rules he decided on.
(rules can
Antoine Pitrou added the comment:
> yes, my problem is that callable was removed and a way was shown how
> to do this check. The way which is consistent with the check for any
> other type (ABC).
ABCs are still the exception in Python, and duck typing is still the
rule.
> I don
Antoine Pitrou added the comment:
> > ABCs are still the exception in Python, and duck typing is still the
> rule.
>
> Then why do we callable again?
Because the way __call__ is looked up means hasattr(x, "__call__") is
not the right answer. Otherwise there would b
New submission from Antoine Pitrou :
This test failure is due to test_zipimport_support loading and unloading
modules, which leads to them being reloaded. Then the ssl.CertificateError
which is checked for by assertRaises isn't the same as the one raised by the
module under test (I
Antoine Pitrou added the comment:
> I suggest Py_UNICODE_ADVANCE() to avoid false suggestion that the
> iterator protocol is being used.
You can't use the iterator protocol on a non-PyObject, and Py_UNICODE_*
(as opposed to PyUnicode_*) suggests the macro operates on a raw array
of
Changes by Antoine Pitrou :
--
assignee: -> mark.dickinson
nosy: +mark.dickinson
___
Python tracker
<http://bugs.python.org/issue10562>
___
___
Python-bugs-lis
Antoine Pitrou added the comment:
> Antoine, there are some remaining {LDFLAGS}, two in the Darwin sections,
> one in the OpenBSD section.
>
> I think all of those should be removed as well. Do you agree?
I didn't want to mess with these things too much. I guess you can
Antoine Pitrou added the comment:
There should be an environment variable to make the symbol settable.
$ PYTHONIMAGINARYSYMBOL=i python -c "import cmath; print(cmath.sqrt(-1))"
1i
--
nosy: +pitrou
___
Python tracker
<http://bu
Antoine Pitrou added the comment:
(and perhaps a ResourceWarning if you choose something different from i and j)
--
___
Python tracker
<http://bugs.python.org/issue10
Antoine Pitrou added the comment:
Thanks for the patch.
First, you don't need to support str, since sockets only accept binary strings
(not unicode).
Second, I think it's simpler and more generic to do something like:
try:
self.sock.sendall(data)
except TypeError:
Antoine Pitrou added the comment:
I can reproduce the issue with 3.2 here. Using Wireshark, I see that the
request to http://www.ihnez.cz is satisfied, but the second request (to
http://ihnez.cz) is never issued. Here is the Wireshark dump for the TCP
session (request, then response
Antoine Pitrou added the comment:
That line of code (`void = fp.read()`) dates back to a commit by Guido in 1995,
and isn't motivated by any comment or message. HTTP servers probably have
evolved till then :)
--
___
Python tracker
Changes by Antoine Pitrou :
--
assignee: haypo ->
resolution: invalid ->
___
Python tracker
<http://bugs.python.org/issue10541>
___
___
Python-bugs-list
Antoine Pitrou added the comment:
Well, as you point out, it would make more sense to have two separate
callbacks. Also, PyErr_WriteUnraisable() is better than PyErr_Clear().
Finally, you accidentally recoded the file; it should be kept utf-8, not
latin-whatever.
--
nosy: +pitrou
Changes by Antoine Pitrou :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue10580>
___
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou added the comment:
For the record, this will need a comprehensive rewrite of bz2module, since it
uses FILE pointers right now.
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue5
Antoine Pitrou added the comment:
> Would avoiding PyErr_CheckSignals() while the file object is in
> inconsistent state be a reasonable alternative?
No, because we'd like IO operations to be interruptible by the user
(e.g. pressing Ctrl-C) when they would otherwise block indefinite
Antoine Pitrou added the comment:
> Let's start bikeshedding the calling signature. I like having a
> single callback, since multiple callables are a nuisance to manage.
IMO the callback should have a second argument as a dict containing
various statistics that we can expand ove
3001 - 3100 of 16792 matches
Mail list logo
