Georg Brandl added the comment:
I agree with Raymond. Having three names for a function is even more
un-Zen than two.
Also, I can't see wha'ts clearer in assertTrue in comparison with assert_.
--
resolution: - wont fix
status: open - pending
__
Tracker
Georg Brandl added the comment:
Sorry, but I don't see a mismatch between code and output.
--
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2257
__
Nicolas Lécureuil added the comment:
is there a fix applied on mandriva python :
--- (empty file)
+++ cooker/python/current/SOURCES/python-2.5.1-detect-mandriva.patch
Sat Mar 8 03:22:50 2008
@@ -0,0 +1,10 @@
+--- Lib/platform.py.old2007-10-05 20:17:15.0 +0800
Georg Brandl added the comment:
Closing this as won't fix as per discussion in #1725737.
(Quote: It's the job of the packager to clean the directory before
packaging.)
--
nosy: +georg.brandl
resolution: - wont fix
status: open - closed
_
Tracker
Georg Brandl added the comment:
Could you please put all changes in one complete patch? It's much easier
to review that way.
--
assignee: - loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2240
__
Steve Purcell added the comment:
I could be convinced either way here, and Georg Raymond always have
excellent judgement.
My personal inclination would probably be to add the documentation for
assertTrue() and also assertFalse(), since their naming is symmetrical
with that of assertEqual()
Georg Brandl added the comment:
You're right, the footnote has to be removed. Fixed in r61303.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2253
__
Marc-Andre Lemburg added the comment:
Fixed in r61304.
Backport candidate.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2255
__
___
Python-bugs-list mailing list
Changes by Marc-Andre Lemburg:
--
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2255
__
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis added the comment:
I found now a way to fix this, by relying on wchar_t functions. It's
fixed in r61306
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1995
Martin v. Löwis added the comment:
I found a way to fix this, using wchar_t functions. Fixed in r61307.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1618
__
Guilherme Polo added the comment:
Complete patch attached
Added file: http://bugs.python.org/file9636/setitimer_getitimer.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2240
__
Ralf Schmitt added the comment:
I'd like to also see this in 2.6. Should I update the patch (if it
doesn't apply) and test? (I guess the signal module hasn't changed that
much).
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2240
Guilherme Polo added the comment:
If you are going to backport it to 2.6, then the C wrapper should be
adapted to match Python 2.x C coding style. If the other parts don't
apply correctly, then you should update it aswell.
__
Tracker [EMAIL PROTECTED]
Jean-Paul Calderone added the comment:
I don't see the ability to use a slice as a dict key as particularly
more surprising than the ability to use ints as dict keys. Someone who
doesn't understand how dicts work can use either of these features to
write broken programs.
I have thought about
Alexander Belopolsky added the comment:
Note that L[:] and L[:] = [] are well-known idioms for making a copy of
a list and emptying the list respectively. (For dictionaries we have
D.copy() and D.clear().) Someone looking at x[:] or x[:] = [] should
immediately recognize a list copy or clear
Alexander Belopolsky added the comment:
Georg, did you miss the s/assuming/because/ part of my proposal? Python
guarantees that sizeof(Py_ssize_t) == sizeof(size_t) == sizeof(void*). (See PEP
353.)
Assuming is therefore misleading because it suggests that it may not
be always true.
Brian White added the comment:
I am somewhat new to mock objects. I'm coding up my first one now (in
D) to simulate a stream for other objects I want to write.
Even within a single module, I typically have many tests for the methods
within that module. And since a module's methods make use of
Facundo Batista added the comment:
Added this functionality in r61312.
--
resolution: - accepted
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1106316
_
Mark Dickinson added the comment:
Coming back to this, I think that it actually *is* clear what
struct(f, large_float) should do: it should raise OverflowError.
This fits in well with the general philosophy that Python (at least
tries to) follow for floating-point exceptions.
The attached
Changes by Raymond Hettinger:
--
resolution: - rejected
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1733184
_
___
Python-bugs-list
Jim Kleckner added the comment:
I uninstalled and re-ran the install without the compile all selected.
The install didn't report errors.
running:
python -c import test.testall
results in a traceback with the message:
import _socket
ImportError: DLL load failed: The system could not
Jean Brouwers added the comment:
There are 7 other, potentially serious issues in the original _hotshot.c
file. All those are being fixed for the next version of the enhanced
hotshot files.
The 7 issues are:
1) functions flush_data and do_stop may create an infinite recursion on
line 567.
Mark Dickinson added the comment:
The docs say that development for the MacPython OSA modules has stopped,
and that a replacement is expected for Python 2.5.
Can this issue now be closed, or at least have its priority downgraded?
--
nosy: +marketdickinson
Paul Molodowitch added the comment:
Patch for sgmllib.py (and test_sgmllib.py)
Correctly parses quoted attribute - allowing for brackets, newlines, etc
within attributes - implemented by altering the loop which finds
attributes within parse_starttag so it checks for open-ended quotes, and
makes
25 matches
Mail list logo
