Roundup Robot added the comment:
New changeset 5063df721985 by Terry Jan Reedy in branch '2.7':
Issue #21686: idlelib/HyperParser.py - Update docstrings and comments and
http://hg.python.org/cpython/rev/5063df721985
New changeset ddf15cf0db72 by Terry Jan Reedy in branch '3.4':
Issue #21686:
Roundup Robot added the comment:
New changeset 95d487abbfd8 by Terry Jan Reedy in branch '2.7':
Issue #19362: Tweek len() doc and docstring to expand the indicated range of
http://hg.python.org/cpython/rev/95d487abbfd8
New changeset 8fcbe41e1242 by Terry Jan Reedy in branch '3.4':
Issue #19362:
Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - fixed
stage: - resolved
status: open - closed
versions: +Python 2.7, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19362
Roundup Robot added the comment:
New changeset 9ba324a20bad by Terry Jan Reedy in branch '3.4':
Issue #21559: Add alternative (historical) reason for OverflowError.
http://hg.python.org/cpython/rev/9ba324a20bad
--
nosy: +python-dev
___
Python tracker
Changes by Terry J. Reedy tjre...@udel.edu:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21559
___
___
Python-bugs-list
Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - fixed
stage: - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21559
___
___
Nick Coghlan added the comment:
I'm with Guido on this one - I don't believe there's a clean sweet spot to hit.
There *might* be a plausible case to be made for tracing functionality in the
logging module, but even there the number of options multiplies fast enough
that writing your own
Sebastian Kreft added the comment:
Any ideas how to debug this further?
In order to overcome this issue I have an awful workaround that tracks the
maximum running time of a successful task, and if any task has been running
more than x times that maximum I consider it defunct, and increase the
New submission from Claudiu Popa:
Hi. Currently, distutils.command.upload has this code:
try:
result = urlopen(request)
status = result.getcode()
reason = result.msg
except OSError as e:
self.announce(str(e), log.ERROR)
return
except HTTPError as e:
status = e.code
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: -haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20319
___
___
Python-bugs-list
Bohuslav Slavek Kabrda added the comment:
So, as pointed out by haypo, blksize_t is actually signed long on Linux. This
means that my patch (as well as the current code) is not right.
Both with and without my patch, io_open function uses int to store blksize_t
and it also passes it to one of
Roundup Robot added the comment:
New changeset 2b8cd2bc2745 by Nick Coghlan in branch '3.4':
Issue #21669: Special case print exec syntax errors
http://hg.python.org/cpython/rev/2b8cd2bc2745
New changeset 36057f357537 by Nick Coghlan in branch 'default':
Merge issue #21669 from 3.4
Nick Coghlan added the comment:
I went ahead and committed the v2 patch, as I think it's already an improvement
over the generic message. Any further significant tweaks to the heuristics or
changes to the error messages can be handled in separate issues.
--
resolution: - fixed
stage:
Giampaolo Rodola' added the comment:
Yeah, I don't think this is worth it anymore. Closing as won't fix.
--
assignee: - giampaolo.rodola
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Claudiu Popa pcmantic...@gmail.com:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19628
___
___
Michael Foord added the comment:
I haven't reviewed the patch in detail, but I've had a scan through and it
looks *great*. A quick and dirty check that it's correct is to compare the
number of tests run before and after the patch - and if the numbers differ
verifying that it's for good
New submission from Nick Coghlan:
There are currently no dedicated docs for the bytes and bytearray methods - the
relevant section just refers back to the str methods. This isn't sufficient,
since the str methods cover of lot of stuff related to Unicode that isn't
relevant to the binary
Glenn Langford added the comment:
Any ideas how to debug this further?
Wherever the cause of the problem might live, and to either work around it or
gain additional information, here is one idea to consider.
Do you need to submit your Futures just two at a time, and tightly loop every
15s?
Roundup Robot added the comment:
New changeset f254ceec0d45 by Jesus Cea in branch '2.7':
Closes #21759: URL Typo in Documentation FAQ
http://hg.python.org/cpython/rev/f254ceec0d45
--
nosy: +python-dev
resolution: - fixed
stage: needs patch - resolved
status: open - closed
Jesús Cea Avión added the comment:
Thanks!
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21759
___
___
Python-bugs-list mailing
Sebastian Kreft added the comment:
I'm running actually millions of tasks, so sending them all at once will
consume much more resources than needed.
The issue happens no only with 2 tasks in parallel but with higher numbers
as well.
Also your proposed solution, has the problem that when you
Glenn Langford added the comment:
Under the hood, the behaviour of as_completed is quite different. So there is
no guarantee it would behave the same.
In any event, with millions of tasks you might consider Celery (I haven't used
it myself):
http://www.celeryproject.org
--
R. David Murray added the comment:
Since there is no guarantee anyone is going to tackle the job of reviewing all
the changes for whatsnew entries, I prefer that we get in the habit of creating
the entries as we go along.
As for the versionchanged...if you can find where include is
R. David Murray added the comment:
Yes, I think that is appropriate. Note that you also get RFC822 parsing for
datetime via email.util.parsedate_to_datetime.
(I'm not sure why the OP thought that using the email utilities to parse
email-standard dates was not [a] very good way.)
--
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: - duplicate
stage: test needed - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21741
___
___
R. David Murray added the comment:
+1 from me (after verification), which should probably go without saying since
I'm the one that started this ball rolling by making regrtest work with
unittest discovery :)
I think the potential disruption to existing patches and any forward porting
issues
Roundup Robot added the comment:
New changeset aa85e8d729ae by Victor Stinner in branch 'default':
Issue #21205: Add a new ``__qualname__`` attribute to generator, the qualified
http://hg.python.org/cpython/rev/aa85e8d729ae
--
nosy: +python-dev
___
New submission from Armin Rigo:
Following the documentation at https://docs.python.org/3/c-api/buffer.html, if
we write a custom object in C with a getbufferproc that simply returns
PyBuffer_FillInfo(...), then it works fine up to Python 3.2 but segfaults in
Python 3.3 depending on what we do
Changes by Armin Rigo ar...@users.sourceforge.net:
Added file: http://bugs.python.org/file35655/xymodule.c
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21778
___
STINNER Victor added the comment:
Ok, this issue is now fixed in Python 3.5.
For Python 2.7 and 3.4, it may be possible to change how the generator name is
set (from the function, not from the code object). It might break the backward
compatibility, even if I don't think that anyone rely on
Roundup Robot added the comment:
New changeset 901a8265511a by Victor Stinner in branch 'default':
Issue #21205: Fix unit tests
http://hg.python.org/cpython/rev/901a8265511a
--
___
Python tracker rep...@bugs.python.org
Antoine Pitrou added the comment:
Le 16/06/2014 10:20, STINNER Victor a écrit :
What do you think for Python 2.7 and 3.4: would you be ok to change
also the generator name? I can write a patch which adds a new gi_name
but the name would not be modifiable to limit the incompatible changes.
I
STINNER Victor added the comment:
Antoine Pitrou wrote:
I don't think it is worthwhile.
Ok, let's keep the issue closed then ;-)
Thanks for the review Antoine.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21205
Stefan Krah added the comment:
The flags from mb_getbuf() have to be passed to PyBuffer_FillInfo():
return PyBuffer_FillInfo(view, (PyObject *)self,
internal, 5,
/*readonly=*/0, flags);
The flags contain the actual request that the
Serhiy Storchaka added the comment:
Some abstract test classes now are included in testing:
Lib/test/test_calendar.py: MonthCalendarTestCase
Lib/test/test_csv.py: TestCsvBase
Lib/test/test_funcattrs.py: FuncAttrsTest
Lib/test/test_sys_setprofile.py: TestCaseBase
Lib/test/test_telnetlib.py:
Roundup Robot added the comment:
New changeset 28b3b8b22654 by Victor Stinner in branch 'default':
Issue #21205: Complete the versionchanged note in inspect documentation
http://hg.python.org/cpython/rev/28b3b8b22654
--
___
Python tracker
Michael Foord added the comment:
Those should be turned into mixins, or someone could implement issue 14534.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21741
___
Armin Rigo added the comment:
Ah! Thanks. I systematically missed the flags arguments passed in the
getbufferproc function.
(I thought I had to tell PyBuffer_FillInfo() what kind of format we actually
provide, but it seems that the interface is the other way around. I don't see
how I would
Changes by Armin Rigo ar...@users.sourceforge.net:
--
resolution: - not a bug
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21778
___
___
Iakov Davydov added the comment:
ISO 8601 is meant as the standard way to provide an unambiguous and
well-defined method of representing dates and times. And the fact that it is
widely used in e-mails doesn't make it e-mail specific.
Incorporating function parsedate_to_datetime to email.util
New submission from Serhiy Storchaka:
$ ./python -Werror -m test.regrtest -v -m test_sys_exit
test_multiprocessing_spawn
== CPython 3.5.0a0 (default:149cc6364180+, Jun 12 2014, 15:45:54) [GCC 4.6.3]
== Linux-3.8.0-36-generic-i686-with-debian-wheezy-sid little-endian
== hash algorithm:
Changes by STINNER Victor victor.stin...@gmail.com:
--
title: est_multiprocessing_spawn fails when ran with -Werror -
test_multiprocessing_spawn fails when ran with -Werror
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21779
STINNER Victor added the comment:
zlibmodule_ssize_t_clean.patch: Patch to make the zlib module ssize_t clean.
The patch just defines PY_SSIZE_T_CLEAN, no # format is used. ./python -m
test -v test_zlib test pass on my 64-bit Linux.
--
keywords: +patch
nosy: +haypo
Added file:
STINNER Victor added the comment:
I just created the issue #21780 to make the unicodedata module 64-bit safe.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8677
___
New submission from STINNER Victor:
Follow-up of issue #8677: patch to make the unicodedata module 64-bit safe.
--
files: unicodedata_64bit.patch
keywords: patch
messages: 220734
nosy: haypo
priority: normal
severity: normal
status: open
title: make unicodedata module 64-bit safe
New submission from STINNER Victor:
Follow-up of issue #8677: patch to make the _ssl module 64-bit clean.
--
files: ssl_64bit.patch
keywords: patch
messages: 220736
nosy: haypo
priority: normal
severity: normal
status: open
title: make _ssl module 64-bit clean
versions: Python 3.5
Added
STINNER Victor added the comment:
I created the issue #21781 to make the _ssl module 64-bit clean.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8677
___
STINNER Victor added the comment:
Here is a different but similar patch for _syscmd_uname():
- use os.fsdecode() to use the locale encoding instead of latin-1
- use subprocess.DEVNULL to redirect errors to /dev/null
- use with proc: to ensure that the subprocesss is cleaned in case of error
R. David Murray added the comment:
Supporting ISO 8601 is quite different from supporting RFC2822 dates, as far as
I can see, and the latter clearly belongs in the email library (especially
considering that RFC2822 parsing must follow Postel's Law and accept dirty
data).
If you want to
Iakov Davydov added the comment:
I took a closer look for #15873. Apperently it solves the issue.
Thanks, David.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
Changes by Iakov Davydov da...@myths.ru:
--
nosy: +davydov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15873
___
___
Python-bugs-list mailing
Stefan Krah added the comment:
Yes, PyBuffer_FillInfo() is a bit confusing: The canonical usage *looks* as
if flags were somehow used in the Py_buffer struct to mark a buffer as having
certain capabilities:
Modules/_io/bufferedio.c:
-
if (PyBuffer_FillInfo(buf,
Stefan Krah added the comment:
I think it's worth adding a note to the docs about passing the flags unmodified
inside a getbufferproc.
--
assignee: - docs@python
components: +Documentation
nosy: +docs@python
resolution: not a bug -
stage: - needs patch
versions: +Python 3.4, Python
Mark Lawrence added the comment:
Can we have an update on this please, I'm assuming that the priority should now
be marked as normal?
--
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3
___
Python tracker
Mark Lawrence added the comment:
Presumably set to languishing by mistake so please close.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20085
___
Ethan Furman added the comment:
Right, I had copied that code from test_pydoc which is where 'print_diffs' is
defined.
A comment there says to use the now-included functionality in unittest, and
some digging in the docs revealed that assertEqual uses diffs by default.
--
assignee: -
New submission from Giacomo Alzetta:
The documentation for hashable in the glossary
(https://docs.python.org/3.4/reference/datamodel.html#object.__hash__) is
incorrect:
they all compare unequal (except with themselves), **and their hash value is
their id().**
It is *not* true that their
Mark Lawrence added the comment:
I'm assuming that this still needs some TLC.
--
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7687
Mark Lawrence added the comment:
There is a simple patch to free memory which at a quick glance appears okay.
I've not tried to apply it as the line numbers tie up with those in the
existing code.
--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.1
R. David Murray added the comment:
The statement is poorly worded. The id() is the *input* to the hash function
used to compute the default __hash__. This is a CPython implementation detail,
though, so perhaps all mention of it should indeed be dropped.
--
nosy: +r.david.murray
Giacomo Alzetta added the comment:
their hash value is their id() seems quite clearly stating that:
class A: pass
...
a = A()
hash(a) == id(a)
should be true, but:
hash(a) == id(a)
False
(both in python2 and in python3)
The python 2 documentation for the __hash__ special method *does*
Changes by Berker Peksag berker.pek...@gmail.com:
--
status: languishing - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20085
___
___
Ned Deily added the comment:
Investigating a user report of IDLE freezing on OS X when mouse clicking on the
code completion menu led me to this issue. The behavior I see varies depending
on the Tk variant in use. The basic test case is:
1. launch IDLE with an IDLE shell window open
2. open
Antoine Pitrou added the comment:
I think it's ok to keep the block size an int for now. It would be surprising
for a block size to be more than 2 GB, IMO.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21679
R. David Murray added the comment:
Yes, I should have been clearer. By poorly worded I meant id is involved,
but the sentence does not correctly describe *how* id is involved. That is,
the sentence is wrong as written.
The implementation is the same in both Python2 and Python3, though the
Changes by Benjamin Kircher benjamin.kirc...@gmail.com:
--
nosy: +bkircher
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10740
___
___
New submission from Milan Oberkirch:
Sending HELO or EHLO more then once causes smtpd.SMTPChannel to respond with
b'503 Duplicate HELO/EHLO\r\n' (see Lib/test/test_smtpd.py:124 for an example).
My interpretation of RFC 821, section 4.1.1.5 is that multiple HELO commands
are fine outside a
Terry J. Reedy added the comment:
Coverage is now '99%'. Unless I see problems that are more than trivial, I am
going to polish the patch and commit.
I believe partial coverage of for context in editwin.num_context_lines: is
because the iterable is never empty. But it never will be in
Mark Lawrence added the comment:
Seems like a good idea but it'll go nowhere without a patch, anybody up for it?
--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.5 -Python 3.4
___
Python tracker rep...@bugs.python.org
Mark Lawrence added the comment:
@Benjamin what do you think of the proposed fix?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11056
___
Eduardo Seabra added the comment:
Berker Peksag, I don't think your patch is okay.
When symlinks is set to true, it should copy the symbolic link of the
directory. Your code is calling copytree instead.
I think the following patch is working, no errors on regression tests.
--
nosy:
Mark Lawrence added the comment:
If this report is (still) true I'd assume that we'd want to eventually action
it. Otherwise can we close this as out of date?
--
nosy: +BreamoreBoy
type: - enhancement
versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2, Python 3.3
Roundup Robot added the comment:
New changeset 1536085d4a94 by Victor Stinner in branch '3.4':
Issue #21773: Fix TestStdLib.test_pydoc() of test_enum. Patch written by
http://hg.python.org/cpython/rev/1536085d4a94
New changeset e82ba67d7472 by Victor Stinner in branch 'default':
(Merge 3.4)
STINNER Victor added the comment:
Fixed. Thanks for the patch.
--
nosy: +haypo
resolution: - fixed
status: open - closed
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21773
STINNER Victor added the comment:
If I understood correctly, supporting the wide mode for wprintf() requires to
modify all calls to functions like printf() in Python and so it requires to
change a lot of code. Since this issue was the first time that I heard about
wprintf(), I don't think
STINNER Victor added the comment:
I don't think that Windows XP is officially no more supported in Python. I
would prefer an explicit mention in the PEP 11. So please don't use this
argument to close an issue.
--
nosy: +haypo
___
Python tracker
Mark Lawrence added the comment:
msg139889 states so I think this report is invalid so I suggest we close this.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11394
___
Mark Lawrence added the comment:
Is the OP interested in taking this forward?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4887
___
Mark Lawrence added the comment:
This won't go anywhere without a patch, is the OP willing to provide one?
--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.5 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5877
Mark Lawrence added the comment:
@Brian this will go nowhere without a patch covering code, tests and
documentation, are you interested in providing one?
--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.5 -Python 3.4
___
Python tracker
Mark Lawrence added the comment:
In recent months people have been doing some great work on the docs, is this
something that one of them could pick up? I'm sorry that I can't remember any
names.
--
nosy: +BreamoreBoy
___
Python tracker
STINNER Victor added the comment:
Calling f.read() on naked os.open() output can produce IOError: [Errno 4]
Interrupted system call. Attached is a suggested fix.
I cannot reproduce your issue. What is your exact Python version and OS?
I tried to run 100 threads calling 100 times
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15955
___
___
Python-bugs-list
Mark Lawrence added the comment:
It looks as if we're talking at cross purposes. PEP11 will not be updated any
more for Windows releases, we will be following the Microsoft support life
cycle. That is clearly of interest to anybody wishing to make code changes
against this issue. I do not
Josh Rosenberg added the comment:
I see a few issues with this:
1. Changing the default behavior is a compatibility issue. I've written code
that depends on exceptions being raised if slice assignment sizes don't match.
2. The performance cost is high; changing from rewriting in place to
Mark Lawrence added the comment:
I've tried to reproduce this on Windows 7 with Python 3.4.1 and failed. Would
somebody else please give it a go.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6270
Changes by Josh Rosenberg shadowranger+pyt...@gmail.com:
--
nosy: +josh.rosenberg
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21679
___
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16136
___
___
Mark Lawrence added the comment:
I like the wording in the patch as it's clearer than the original and so think
it should be applied.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8822
Tor Colvin added the comment:
2.7.6 or 3.4.1 with OS X 10.8. I can only reproduce it an automated test
environment when the load is high on the machine. I've also seen it with
10.6/10.7. It's definitely inconsistently reproducible.
--
___
Python
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +paul.j3
versions: +Python 2.7, Python 3.5 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9341
___
Lars H added the comment:
+1 vote for fixing this problem. Matt Hickford said it very well... the error
message is very cryptic, not giving the user a clue as to what domain the
problem lies in.
--
nosy: +Lars.H
___
Python tracker
Mark Lawrence added the comment:
@Steve could this be included with the work you're doing with the Windows
installers?
--
components: +Windows
nosy: +BreamoreBoy, dstufft, eric.araujo, steve.dower
___
Python tracker rep...@bugs.python.org
Nikolaus Rath added the comment:
On 06/15/2014 06:26 PM, Raymond Hettinger wrote:
Before creating more tracker items, please take time to learn about how
Python's history,
[...]
It'd be nice if you would have at least followed the link to
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
versions: +Python 3.5 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1635217
___
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +paul.j3
versions: +Python 2.7, Python 3.5 -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9350
___
Mark Lawrence added the comment:
The attached patch is simple enough, surely it's a simple decision as to
whether or not to commit it?
--
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3
___
Python tracker
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +paul.j3
versions: +Python 2.7, Python 3.5 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11695
___
Mark Lawrence added the comment:
If we've got some meaningful changes can we please get them committed. However
I'd like to state that with over 4000 issues open we've got better things to do
than change docs because somebody doesn't like the use of foo, bar and baz in
examples.
--
1 - 100 of 124 matches
Mail list logo