Christian Heimes added the comment:
Neal fixed it in r60488
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1963
__
___
Georg Brandl added the comment:
Martin, what do you think?
--
assignee: - loewis
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1652
__
___
Colin Watson added the comment:
To be quite honest I can't think of any incompatibilities that wouldn't
have the basic result of improving matters. I put the migration stuff in
my bug report in case somebody else could, because I don't want the bug
fix to stall on that.
My preference would be
Amaury Forgeot d'Arc added the comment:
I think that we should separate this from #1222, and have two steps:
- first change test_locale, without any modification to localemodule.
- then add features and more tests.
--
nosy: +amaury.forgeotdarc
__
Tracker
Georg Brandl added the comment:
Looks good to me.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1222
__
___
Python-bugs-list mailing list
Unsubscribe:
Georg Brandl added the comment:
Added to Sphinx in r60490.
--
resolution: - accepted
status: open - closed
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue800926
New submission from Georg Brandl:
x = io.StringIO(1)
x.read()
'1'
--
components: Extension Modules
messages: 61957
nosy: georg.brandl
priority: high
severity: normal
status: open
title: io.StringIO allows any parameter
type: behavior
versions: Python 3.0
Antoine Pitrou added the comment:
Well it was how I planned to do it at first (hence this bug entry) :-)
I can still try to split the #1222 patch if it makes things easier (but
does it?).
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1864
Raghuram Devarakonda added the comment:
test_socket.py now seems to use dynamically computed port number so
there should not be any port number conflicts.
--
nosy: +draghuram
resolution: - out of date
status: open - closed
_
Tracker [EMAIL
Guido van Rossum added the comment:
I think it's worth applying this to 2.5.2 even if the patch is dead
after that. More unittests are definitely in order.
--
nosy: +gvanrossum
priority: low - normal
__
Tracker [EMAIL PROTECTED]
Changes by Guido van Rossum:
--
assignee: - barry
nosy: +barry
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1974
__
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Actually I see the same behavior under Linux and OSX: the first ^C
interrupts the select() call, after that ^C is ignored.
--
nosy: +gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1975
Guido van Rossum added the comment:
id(a.__abs__) == id(a.__abs__)
has a completely different explanation -- it so happens that the first
instantiation of a.__abs__ is freed after id() is called on it and the
second instantiation happens to reuse that same memory block.
--
nosy:
Guido van Rossum added the comment:
I think nobody really cares about freeze any more -- it isn't maintained.
--
nosy: +gvanrossum
priority: - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1985
__
Christian Heimes added the comment:
Ryan Stutsman wrote:
Actually the current trunk of as of this morning (60484) is still broken
in a couple of ways. First, converting the pid_t using PyInt is a
problem and second the waitpids aren't corrected. This would cause
waits on invalid pids.
Ryan Stutsman added the comment:
Actually the current trunk of as of this morning (60484) is still broken
in a couple of ways. First, converting the pid_t using PyInt is a
problem and second the waitpids aren't corrected. This would cause
waits on invalid pids.
Raghuram Devarakonda added the comment:
With the latest python, get() itself fails with boolean value default. I
tried with this script:
-
from ConfigParser import ConfigParser
cfg = ConfigParser({'var':True})
cfg.add_section('test_section')
print cfg.getboolean('test_section',
Raghuram Devarakonda added the comment:
The following two statements from ConfigParser document clearly mention
that what is passed in 'vars' are defaults and defaults come into
picture only when values are not explicitly set.
Default values can be specified by passing them into the
Changes by Raghuram Devarakonda:
--
components: +Documentation -Library (Lib)
versions: +Python 2.6 -Python 2.3
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1090076
_
Guido van Rossum added the comment:
I'm against including this in 2.5.2. It reeks of a new feature, and the
code looks like it would risk breaking other apps.
(I'm fine with adding this to 2.6 of course.)
--
nosy: +gvanrossum
_
Tracker [EMAIL
Gregory P. Smith added the comment:
yes i'll take a look at this weekend.
jcea is doing his bsddb development in the pybsddb.sf.net project svn
repository for the time being. I'll be merging his changes back into
the python tree.
We can get him python svn access soon but i wanted to make sure
New submission from Antoine Pitrou:
Some values in the dict returned by localeconv() may be non-ASCII
strings, yet they are not decoded according to the locale's character
set. This can be observed when the currency symbol is the euro sign:
import locale
locale.setlocale(locale.LC_MONETARY,
Antoine Pitrou added the comment:
Here is a patch fixing the problem. Note however that it will make
localeconv() quite slower. Perhaps _locale.localeconv should grow an
encoding parameter instead.
Added file: http://bugs.python.org/file9343/pylocaleconv.patch
Christian Heimes added the comment:
Martin v. Löwis wrote:
If so, Python would now fail to compile under that
patch. Backporting a change that causes Python to fail
to compile on some systems is not a good idea.
I added the size comparison to identify systems with sizeof(pid_t)
Martin v. Löwis added the comment:
The locale module is completely broken; don't try to work around that
breakage. One option would be to remove it entirely.
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1995
Martin v. Löwis added the comment:
Your proposal looks sound and good to me, but it involves some work. The
chance would require a new format operator 'p' for argument parsing and
new functions like PyInt_FromPid_t() and PyInt_AsPid_t().
No, it doesn't require that. You could use conditional
New submission from Raymond Hettinger:
Just before the sign bit is restored, add code with the following effect:
while not top1:
top = 1
e += 1
Tests:
math.pi -- (884279719003555, 281474976710656)
7.5 -- (15, 2)
0.875 -- (7, 8)
--
files: tmp_float_conv.py
Changes by Raymond Hettinger:
--
assignee: - jyasskin
components: +Interpreter Core
nosy: +jyasskin
versions: +Python 2.6
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1996
__
New submission from Aaron Watters:
As I understand it comparisons between two objects should
always work. I get this at the interpreter prompt:
Python 2.6a0 (trunk, Jan 11 2008, 11:40:59)
[GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2
Type help, copyright, credits or license for more
Marc-Andre Lemburg added the comment:
The change we did was for == and != comparisons to always work (they now
raise warnings) - mostly because doing otherwise resulted in strange
exceptions when dealing with dictionary lookups.
However, this was not done for comparisons , =, =, since these
Raymond Hettinger added the comment:
Fixed in revision 60511.
--
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1996
__
___
Python-bugs-list
Malte Helmert added the comment:
I can reproduce the bug on trunk (r60511). At first I thought the
behaviour might be caused by the testcase removing items from the
children list while iterating over it, but this is not the case; the
exception is raised upon the first removal already.
Here is a
Malte Helmert added the comment:
OK, I think I found the root cause. Node.normalize regenerates the list
of children L with their previousSibling/nextSibling references from
scratch; however, it fails to set the nextSibling reference for the very
last element of L to None at the end. This is
Malte Helmert added the comment:
Here is a minimal testcase to more clearly expose the root of the
problem, in case a regression test is needed. Without the patch, the
assertion fails.
==
from xml.dom import minidom
node =
Changes by Malte Helmert:
--
versions: +Python 2.6 -Python 2.4
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1433694
_
___
Python-bugs-list mailing list
Guido van Rossum added the comment:
As I understand it comparisons between two objects should
always work.
Hi Aaron! Glad to see you're back.
It used to be that way when you Jim wrote the first Python book. :-)
Nowadays, comparisons *can* raise exceptions. Marc-Andre has explained
why.
Christian Heimes added the comment:
Should freeze be removed if it's no longer maintained? Freeze is partly
used by py2exe and py2app. Maybe the maintainers of the apps can step in
and maintain the parts of the freeze api they require. The rest could
then be deprecated for Python 2.6 and removed
New submission from Mick Charles Beaver:
On page:
http://docs.python.org/lib/sqlite3-Module-Contents.html
The following:
If you want to use other types, like you have to add support for them
yourself.
Should be:
If you want to use other types, you'll have to add support for them
yourself.
New submission from Mick Charles Beaver:
When I found a small mistake in the documentation, I went to the
following URL, which in turn sent me to SourceForge, which then sent me
to the Roundup bug database.
http://docs.python.org/lib/about.html
--
components: Documentation
messages:
Martin v. Löwis added the comment:
Perhaps it is broken - it does look rather fragile - but are there any
plans to design a replacement?
If people could contribute an ICU wrapper - that would be nice. However,
it's unlikely to happen. So I'll rather rewrite _locale to use wchar_t
functions,
Changes by Christian Heimes:
--
assignee: - georg.brandl
keywords: +easy
nosy: +georg.brandl
priority: - low
type: - rfe
versions: +Python 2.6
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1998
__
Changes by Christian Heimes:
--
assignee: - georg.brandl
nosy: +georg.brandl
priority: - normal
type: - rfe
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1999
__
Martin v. Löwis added the comment:
This is a duplicate of issue 1462.
--
nosy: +loewis
resolution: - duplicate
status: open - closed
superseder: - About this document refers to SourceForge tracker
__
Tracker [EMAIL PROTECTED]
Bill Janssen added the comment:
OK, I'll read it more carefully and compare it to the 2.6 version of the
code.
Bill
On Feb 1, 2008 8:00 AM, Guido van Rossum [EMAIL PROTECTED] wrote:
Guido van Rossum added the comment:
I think it's worth applying this to 2.5.2 even if the patch is dead
Guido van Rossum added the comment:
Why don't you ask that question on python-dev? Maybe someone volunteers!
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1985
__
___
Mark Dickinson added the comment:
See issue #1979 for a possible fix.
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1514428
_
___
Python-bugs-list mailing list
Jeffrey Yasskin added the comment:
Go ahead and fix the docstring. I don't really understand what was
incorrect about the original returns the integral closest to x between
0 and x, so I'm not confident that I'll come up with something you'll like.
--
assignee: jyasskin - rhettinger
Raymond Hettinger added the comment:
The latest version in Py2.6 has wording about truncating toward zero.
This is fine. Leaving the report closed.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1965
__
Jeffrey Yasskin added the comment:
*sigh* That's the version I put there. Did you read the patch before
complaining about it?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1965
__
Jeffrey Yasskin added the comment:
Whoops, sorry for taking a while to answer. +0 on adding support for
'2.' and '.3', given that they're allowed for float and Decimal. Not +1
because they'll make the regular expression more complicated, and
they're not exactly necessary, but if you want to add
Georg Brandl added the comment:
This seems already fixed in SVN.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1998
__
51 matches
Mail list logo