New submission from Georg Brandl:
I'm a bit puzzled by this exception in a long-running process
(running on Python 2.7.3):
...
File /usr/lib/python2.7/Queue.py, line 138, in put
self.not_empty.notify()
item = ('message',
Roger Serwy added the comment:
Welcome Phil! Your patch looks good and applied cleanly to the default branch
and behaves as you specified. Your submission mechanics are good!
You might want to look into signing a contributor's agreement:
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 2.7, Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6699
___
Jan Safranek added the comment:
On 05/07/2013 06:06 PM, Antoine Pitrou wrote:
a significant amount of static data inside CPython actually survives
Py_Finalize :-/
As a solution, would it be possible to wipe all registered types in
Py_Finalize?
Jan
--
Jan Safranek added the comment:
On 05/07/2013 05:32 PM, Antoine Pitrou wrote:
Jan, one possibility would be for Pegasus to stop unloading Python,
it seems.
It is always possibility. Actually, Pegasus plugin is just a shared
object (.so) and the .so is linked with Python. Pegasus calls
paul j3 added the comment:
I think this patch should build on http://bugs.python.org/issue9849, which
seeks to improve the error checking for nargs. There, add_argument returns an
ArgumentError if the nargs value is not a valid string, interger, or it there
is mismatch between a tuple
Till Maas added the comment:
I just tried on a Windows 8 system with python from GIMP. The error occurs
there as well if I compare two empty files after I removed permissions for one
of the files. I do not know how to manage Windows' file ACLs in python,
therefore I created the test case
Amit Saha added the comment:
Hello, I just wanted to check if I should attach the image files separately and
submit the text as a diff?
Thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17583
New submission from Serhiy Storchaka:
Here is a patch which refactors test_zipfile, decreases it's size by 269 lines,
makes adding tests for new compression types and new tests for all compression
types simpler, and makes test_zipfile discoverable.
--
components: Tests
files:
Nick Coghlan added the comment:
Ah, I misread the second patch, I think due to the copy the cell into in
the comment. I believe I would have grasped it immediately if it said
something like reference the cell from.
--
___
Python tracker
Richard Oudkerk added the comment:
If the name is a qualified dotted name, it will be split and the first
part becomes the __module__.
That will not work correctly if the module name has a dot in it.
--
nosy: +sbt
___
Python tracker
Roundup Robot added the comment:
New changeset 9b86fb6f5bc9 by Serhiy Storchaka in branch '2.7':
Issue #16601: Restarting iteration over tarfile no more continues from where
http://hg.python.org/cpython/rev/9b86fb6f5bc9
New changeset 9ed127d8ad61 by Serhiy Storchaka in branch '3.3':
Issue
Serhiy Storchaka added the comment:
Thank you for contribution.
I have committed simpler test.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
Michael Birtwell added the comment:
Sorry about the delay in the contributor form. Things got in the way then I
completely forgot about it. It's done now.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16601
Serhiy Storchaka added the comment:
Patch for issue16601 has fixed this issue too.
--
resolution: - duplicate
stage: patch review - committed/rejected
status: open - closed
superseder: - Restarting iteration over tarfile continues from where it left
off.
Serhiy Storchaka added the comment:
Shouldn't it left opened until regression fix release has released.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17656
___
Antoine Pitrou added the comment:
I don't think so. The bug is fixed, and the fix will be in the release.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17656
___
Roundup Robot added the comment:
New changeset dee0a2dea11e by Ezio Melotti in branch '3.3':
#17809: fix a test failure in test_expanduser when $HOME has a trailing /.
Patch by Kubilay Kocak.
http://hg.python.org/cpython/rev/dee0a2dea11e
New changeset 489f075430de by Ezio Melotti in branch
Antoine Pitrou added the comment:
Waiters are created through _allocate_lock(), so you should look there.
But, unless you have further info, I don't think keeping this open as a bug is
useful.
--
___
Python tracker rep...@bugs.python.org
Ezio Melotti added the comment:
Fixed, thanks for the patch!
--
resolution: - fixed
stage: commit review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17809
Roundup Robot added the comment:
New changeset 844c6442a39e by Ezio Melotti in branch '3.3':
#17938: remove duplicate paragraphs.
http://hg.python.org/cpython/rev/844c6442a39e
New changeset ebc296bf23d1 by Ezio Melotti in branch 'default':
#17938: merge with 3.3.
Ezio Melotti added the comment:
Fixed, thanks for the report!
--
assignee: docs@python - ezio.melotti
resolution: - fixed
stage: - committed/rejected
status: open - closed
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
A.M. Kuchling added the comment:
I've just verified that I still have commit access to the repo, so unless
someone has any further suggested changes to the patch, I'll go ahead and
commit it to trunk. Should I also commit it to the 3.3 branch?
Victor: I'm willing to improve the HOWTO's
Eric V. Smith added the comment:
I agree it should work the same as Enum, and I agree it should be possible to
supply the module name. But wouldn't it be cleaner as:
Point = namedtuple('Point', 'x y z', module=__name__)
rather than:
Point = namedtuple(__name__ + '.Point', 'x y z')
?
Ezio Melotti added the comment:
Patch LGTM.
You should commit it to 3.3 and then merge it with default (unless the patch
contains parts that are specific to 3.4).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17700
Serhiy Storchaka added the comment:
Thanks, for 3.4 I will use new formatting feature.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16741
___
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17941
___
___
Python-bugs-list mailing
New submission from Gregory HOULDSWORTH:
Python version: 3.3.0 32bit
OS: Windows 7 Service Pack 1 64bit
The peer_create method of the Text class, introduced in changeset
71041c0dedd5 in response to issue 2843 creates a tk text widget
but does not instantiate Text. Because they don't exist as
Arfrever Frehtes Taifersar Arahesis added the comment:
http://mail.python.org/pipermail/python-dev/2013-April/125761.html asked to
leave bugs open.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17656
Antoine Pitrou added the comment:
Ah, fair enough.
--
status: closed - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17656
___
___
Andriy Mysyk added the comment:
Incorporated R. David Murray's feedback...
.. method:: acquire(blocking=True, timeout=-1)
Without any optional argument, this method acquires the lock
unconditionally, if necessary waiting until it is released by another
thread (only one
Guilherme Polo added the comment:
Uh.. well observed.
It sounds like you are the first actual user of peer_create. Now I wish Tk
had done this in a different way: when creating a text widget, specificy
that it is a peer of some other text widget via an option (-peer w for
example).
If possible
Guido van Rossum added the comment:
Ok, here's a version with a unittest. I've also improved the comment that set
Nick off the track.
--
keywords: +patch
Added file: http://bugs.python.org/file30185/cellfree3.diff
___
Python tracker
Guilherme Polo added the comment:
Here is a quick patch for it: http://pastebin.com/m1XQBGqU (I forgot my
password for the tracker, and leaving home right now).
Does it work for you ?
--
___
Python tracker rep...@bugs.python.org
Guido van Rossum added the comment:
Agreed with Eric. We're already modifying PEP 435 to do it that way.
--
nosy: +gvanrossum
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17941
___
New submission from Lucas Clemente Vella:
As stated in RFC 3548:
Base encoding of data is used in many situations to store or transfer
data in environments that, perhaps for legacy reasons, are restricted
to only US-ASCII [9] data.
thus, I was surprised to see, when I used base64 for
Gregory HOULDSWORTH added the comment:
Splendid, it works and is indeed far more elegant.
Well done there, thanks.
--
resolution: - works for me
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17945
R. David Murray added the comment:
This has been discussed numerous times. There are just as many times when you
want the output to be binary (because you are about to send it on the wire).
However, the deciding factor is that the API is now what it is, and changing it
at this point would
Xavier de Gaye added the comment:
The attached script, test_initiate_send.py, tests initiate_send with
threads, causing duplicate writes and an IndexError. This is the
script output using python on the default branch:
$ python test_initiate_send.py
--- Test: duplicate data sent ---
Zachary Ware added the comment:
I'm not sure where to go with this from here, without knowing more about what's
going wrong. Just to make sure there wasn't anything wrong with the Tcl/Tk
build or some manner of issue with things not being properly cleaned up or
something, I set the 'custom'
STINNER Victor added the comment:
Alex In my opinion that should use PyLong_CheckExact
+1
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17576
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17936
___
___
Python-bugs-list
Terry J. Reedy added the comment:
Amaury and Martin: there is a problem on one machine with
test.test_tcl.TclTest.testLoadWithUNC that you two jointly wrote, reviewed, and
applied in #6470.
This issue (17883) is above getting the tcl/tk/tkinter tests to actually be run
on 2.7, which they
Michael Foord added the comment:
The default test runner is quite horrible.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17908
___
___
Benjamin Peterson added the comment:
Consider the following testcase
class X:
def meth(self):
print(self)
super()
def f():
k = X()
def g():
return k
return g
c = f().__closure__[0]
X.meth(c)
With patch
$ ./python unboxing.py
cell at 0x7fddacab1eb8: X
paul j3 added the comment:
This patch adds this `nargs='{m,n}'` or `nargs=(m,n)` feature.
It builds on the `better nargs error message` patch in
http://bugs.python.org/msg187754
It includes an argparse.rst paragraph, changes to argparse.py, and additions to
test_argparse.py.
The tests
Guido van Rossum added the comment:
I see. I really don't care, it's extremely rare to see a closure object.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17927
___
A.M. Kuchling added the comment:
Applied to 3.3 and 3.4. I'll leave this issue open for a week so that Victor
can comment on Unicode/wide-characters.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17700
Roundup Robot added the comment:
New changeset 1fa70b797973 by Andrew Kuchling in branch '3.3':
#17700: update the curses HOWTO for 3.x
http://hg.python.org/cpython/rev/1fa70b797973
New changeset 70f530161b9b by Andrew Kuchling in branch 'default':
#17700: merge with 3.3
Guido van Rossum added the comment:
cellfree4.diff. Addressed review:
- Moved test to test_scope.py
- Added @cpython_only
- Fixed comment indent (and removed tabs :-)
- Fixed missing NULL test
I decided to keep the super() call; it's likely that it's tested elsewhere but
I don't want to
A.M. Kuchling added the comment:
Thanks for the patch!
--
nosy: +akuchling
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14878
___
Roundup Robot added the comment:
New changeset 7b8c0bf8fcb8 by Andrew Kuchling in branch '2.7':
#14878: add cross-reference to the yield statement.
http://hg.python.org/cpython/rev/7b8c0bf8fcb8
--
nosy: +python-dev
___
Python tracker
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: needs patch - committed/rejected
type: - enhancement
versions: -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14878
Roundup Robot added the comment:
New changeset ead47bc3a763 by Ezio Melotti in branch '3.3':
#17841: remove missing codecs aliases from the documentation. Patch by Thomas
Fenzl.
http://hg.python.org/cpython/rev/ead47bc3a763
New changeset eafff38a56cc by Ezio Melotti in branch 'default':
Ezio Melotti added the comment:
Fixed, thanks for the patch!
@Nick
While this works as a short-term solution, I think it would be good to
1) reintroduce the aliases in 3.4 (so that codecs.encode(b'foo', 'base64')
works without spelling out the full codec name);
2) either separate these
Nick Coghlan added the comment:
Ezio pointed out on IRC that the extra type checks in str.encode, bytes.decode
and bytearray.decode should reference the appopriate codecs module function in
addition to the codec in use.
So if str.encode produces something other than bytes, it should reference
Benjamin Peterson added the comment:
I think it looks good now. I'll probably just rewrite the test once you commit
it.
--
keywords: -needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17927
Nick Coghlan added the comment:
Looks good to me, too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17927
___
___
Python-bugs-list mailing
Ezio Melotti added the comment:
The attached patch changes the error message of str.encode/bytes.decode when
the codec returns the wrong type:
import codecs
'example'.encode('rot_13')
TypeError: encoder returned 'str' instead of 'bytes', use codecs.decode for
str-str conversions
Ezio Melotti added the comment:
To summarize:
* str.encode does only str-bytes;
* bytes.decode does only bytes- str;
* codecs.encode/decode do obj-obj;
The things that could go wrong are:
1) the input type is wrong (i.e. the codec doesn't accept the type of the
input);
2) the input value
Ezio Melotti added the comment:
The attached proof of concept catches Type/ValueError in str.encode and raises
another exception with a better message:
'example'.encode('hex_codec')
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: invalid input type for hex_codec
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: needs patch - patch review
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17282
___
62 matches
Mail list logo
