Tarek Ziadé [EMAIL PROTECTED] added the comment:
This is because the code uses a print statement when opening the .pypirc
file. This was already the case before this patch, but the code was not
covered by tests. (see in previous revision)
The test is not broken, it just ouputs to stdin.
I
Armin Rigo [EMAIL PROTECTED] added the comment:
However, even the TLS copy of errno may change because of this,
if the finalizer of some object invokes ctypes, right?
Yes, it's annoying, but at least the Python programmer has a way to fix
this problem: he can save and restore the TLS copy of
Martin v. Löwis [EMAIL PROTECTED] added the comment:
This is because the code uses a print statement when opening the .pypirc
file. This was already the case before this patch, but the code was not
covered by tests. (see in previous revision)
The test is not broken, it just ouputs to
Tarek Ziadé [EMAIL PROTECTED] added the comment:
Right, Thanks!
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1858
__
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
The patch, in its current form, is incomplete. Can you please provide:
a) a VS 2008 project file, which builds both the curses module and the
pdcurses library, fetching the sources for that from ../../pdcurses (or
some such); the
New submission from Haoyu Bai [EMAIL PROTECTED]:
Sometime we need to enable all fixers but one or two, eg. the 'import'
fixer. So it would be fine if there's a way to do that.
--
assignee: collinwinter
components: 2to3 (2.x to 3.0 conversion tool)
messages: 67289
nosy: bhy, collinwinter
New submission from Haoyu Bai [EMAIL PROTECTED]:
To reproduce the bug, save the uploaded huge.py, then import the module
twice:
$ python3 -c 'import huge'
$ python3 -c 'import huge'
Traceback (most recent call last):
File string, line 1, in module
ValueError: recursion limit exceeded
But
Antoine Pitrou [EMAIL PROTECTED] added the comment:
This is a complementary patch that should fix the remaining cases
(funnily doctest was relying on the old behaviour).
Unfortunately #2833 still remains, and would probably need some
discussion on the ML for proper resolution.
Added file:
Guilherme Polo [EMAIL PROTECTED] added the comment:
Once I wanted this too. I'm attaching two patches but I prefer the
former which allows the skipped fixer(s) to be logged.
--
keywords: +patch
nosy: +gpolo
Added file: http://bugs.python.org/file10425/fixer_skip.diff
Changes by Guilherme Polo [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file10426/fixer_skip2.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2956
__
___
Benjamin Peterson [EMAIL PROTECTED] added the comment:
For time being, should r62847 be reverted?
--
nosy: +benjamin.peterson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
What makes you think that the code does not match the description?
--
nosy: +amaury.forgeotdarc
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2955
__
Antoine Pitrou [EMAIL PROTECTED] added the comment:
I don't think so. As Amaury pointed in #2833, the original re-raising
behaviour which got changed by fixing the present bug was rather broken
in its own way.
Anyway, I think the question better be asked on the ML because any
solution for the
Guilherme Polo [EMAIL PROTECTED] added the comment:
I just got an information here.. The new way is the recommended way
since Tk 8.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2806
__
Georg Brandl [EMAIL PROTECTED] added the comment:
Closing as works for me.
--
resolution: - works for me
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2955
__
Guilherme Polo [EMAIL PROTECTED] added the comment:
You need to install the development package of readline in order to have
the readline module compiled. And this is not a bug.
--
nosy: +gpolo
resolution: - invalid
status: open - closed
__
Tracker
Guilherme Polo [EMAIL PROTECTED] added the comment:
Using a frame and menubutton for creating a menubar has been deprecated
for a long time. I tried finding when exactly it got marked as
deprecated, but I found just this page http://wiki.tcl.tk/4055 which
says about a decade ago.
--
New submission from Benjamin Peterson [EMAIL PROTECTED]:
A good bug day task:
Lib/test/README is a bit dated. It still talks about old-style Python
tests which have been almost completely removed in 2.6 (and none more
should be written.) The assert* methods of unittest should also be
stressed
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10424/better_exc_cleanup.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Patch removed, there are still some unsolved cases :-)
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Changes by Giampaolo Rodola' [EMAIL PROTECTED]:
--
nosy: +giampaolo.rodola, josiah.carlson, josiahcarlson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2944
__
___
Facundo Batista [EMAIL PROTECTED] added the comment:
It's not a 2.6 bug, as it behaves exactly as the documentation states.
In Py3 it *is* different the result than the documentation. However,
it's not clear to me if this behaviour is changed deliberately or by
mistake (personally, I prefer
Georg Brandl [EMAIL PROTECTED] added the comment:
This should now be fixed in r63580.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2904
__
Georg Brandl [EMAIL PROTECTED] added the comment:
This should now be fixed in SVN.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2852
__
Giampaolo Rodola' [EMAIL PROTECTED] added the comment:
By trying your script on Linux and Windows I notice different behaviors.
On Windows handle_expt is always called.
On Linux, no matter if using select or poll, handle_accept is called,
then an exception is thrown at the time the data is going
Georg Brandl [EMAIL PROTECTED] added the comment:
Okay, moved the module and applied the patch in r63586, r63587 and r63589.
--
nosy: +georg.brandl
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
Alexander Shigin [EMAIL PROTECTED] added the comment:
Oh, fine. May be handle_error should have been called, but anyway not
handle_connect.
But in my mind, handle_expt is better.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2944
Changes by Jeffrey C. Jacobs [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file10428/issue2636-05-only.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2636
__
___
Jeffrey C. Jacobs [EMAIL PROTECTED] added the comment:
I am finally making progress again, after a month of changing my
patches from my local svn repository to bazaar hosted on launchpad.net,
as stated in my last update. I also have more or less finished the
probably easiest item, #5, so I
Changes by Jeffrey C. Jacobs [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file10429/issue2636-05.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2636
__
___
Changes by Jeffrey C. Jacobs [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10056/issue2636-05.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2636
__
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Well, it's true that get_ident() will always give you a reliable number
while currentThread() can play dirty games on you at shutdown. The thing
is the Thread object is dereferenced before the OS thread actually
terminates, so it may be that a
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Here is a hopefully complete patch using the same approach as before.
However I'm now convinced that another approach would be better in order
to solve both this bug and the various re-raising issues. It would
involve replacing most of the
Gregory P. Smith [EMAIL PROTECTED] added the comment:
This seems like a useful addition and is easy enough.
Patch with tests and documentation attached. Unless I hear objections I
will commit it to trunk later this week.
Patch available for review here: http://codereview.appspot.com/1301
Changes by Brett Cannon [EMAIL PROTECTED]:
--
dependencies: -Revert SocketServer rename in 2.6
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2775
__
___
Changes by Brett Cannon [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10267/socketserver_rename.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2775
__
___
New submission from Michael Magin [EMAIL PROTECTED]:
Built-in file objects allow repeated calls to .close(), even the
documentation states, Calling close() more than once is allowed.
(http://docs.python.org/lib/bltin-file-objects.html)
GzipFile does not obey this aspect of the file interface:
Irmen de Jong [EMAIL PROTECTED] added the comment:
Thanks Gregory, for taking the time to make a patch.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2871
__
___
Changes by Brett Cannon [EMAIL PROTECTED]:
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2925
__
___
Python-bugs-list mailing list
Unsubscribe:
Brett Cannon [EMAIL PROTECTED] added the comment:
r63104 moved the stud module from Lib to Lib/lib-old.
r63080 changed some docs and added a test for the rename.
r63077 changed imports.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2925
Brett Cannon [EMAIL PROTECTED] added the comment:
After performing a ``svn rename`` on Lib/queue.py to Lib/Queue.py the
attached patch should revert all other changes related to the rename.
As per usual, I am on OS X so I can't do the case-sensitive rename. If
someone could do the svn rename,
Brett Cannon [EMAIL PROTECTED] added the comment:
I have uploaded a patch that when applied after a ``svn rename`` for
Lib/configparser.py to Lib/ConfigParser.py, should revert the rename.
Since I am on OS X I can't do the rename myself.
--
keywords: +patch
Added file:
New submission from Gregory P. Smith [EMAIL PROTECTED]:
Using Linux with BerkeleyDB 4.7.25 the bsddb/test/test_replication.py
test is very flaky. It alternately passes, raises an AssertionError
because of the timeout or gets a segmentation fault or bus error.
(side note: i updated
New submission from Chester [EMAIL PROTECTED]:
Hello,
I would like to report that two error messages of the Python parser are
not consistent. Please take a look at this:
a = hello
a + 1
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: cannot concatenate 'str'
44 matches
Mail list logo
