Guido van Rossum added the comment:
If it works for you, can you submit it?
--
assignee: -> theller
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Guido van Rossum added the comment:
I'm guessing this is fixed now that that patch is submitted.
--
nosy: +gvanrossum
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Guido van Rossum added the comment:
Should be fixed by r57665. I'm guessing we went a little too fast with
this change.
--
nosy: +gvanrossum
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Changes by Guido van Rossum:
--
resolution: -> duplicate
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1023>
__
___
Python
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1678077>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1683368>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
title: Efficient reverse line iterator -> Efficient reverse line iterator
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1720390>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1752184>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1762972>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1774369>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1771260>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1753395>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 3.0
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1766304>
_
___
Python-bugs-list mailing list
Changes by Guido van Rossum:
--
versions: +Python 2.4, Python 2.5, Python 2.6, Python 3.0
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue504152>
__
New submission from Guido van Rossum:
The various caches in abc.py should be turned into weak sets so that the
caches don't keep the subclass objects alive forever.
--
messages: 55480
nosy: gvanrossum
severity: normal
status: open
title: ABC caches should use weak refs
versions: P
Guido van Rossum added the comment:
On 8/30/07, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
> Thomas Wouters added the comment:
>
> Here's a working version of that idea, with a WeakSet implementation I
> had lying around (but never really used.) It seems to work, and f
Changes by Guido van Rossum:
--
priority: immediate -> normal
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1467929>
_
___
Python-bugs-li
Guido van Rossum added the comment:
Georg, would you have time to submit an improved patch?
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1061>
__
___
Pyth
Guido van Rossum added the comment:
Please check it in yourself.
--
assignee: gvanrossum -> collinwinter
resolution: -> accepted
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Guido van Rossum:
--
versions: +Python 3.0
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1067>
__
___
Python-bugs-list mailing list
Unsubs
Guido van Rossum added the comment:
Great, please check it in. This is close to what I had sitting
somewhere, but I hadn't finished it.
--
assignee: gvanrossum -> twouters
resolution: -> accepted
__
Tracker <[EMAIL PROTECTED]>
<ht
Guido van Rossum added the comment:
Barry, what do you think of this patch? How does the email package
handle this case?
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/is
Guido van Rossum added the comment:
(Reopening given recent discussion.)
--
resolution: fixed ->
status: closed -> open
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum added the comment:
Thanks, but no thanks; I was quickly dissuaded from the need for this.
--
nosy: +gvanrossum
resolution: -> rejected
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum added the comment:
We should make sure this is *not* merged into Py3k; there, things remain
unicode until they're printed, at which point the only encoding that
matters is the output file's encoding.
_
Tracker <[EMAIL PROT
Guido van Rossum added the comment:
OK, I've added a big section about print to the front of the "common
stumbling blocks section, with all the info about print together, and a
few examples to clarify the most common changes. You can see the
changes in subversion; they
Guido van Rossum added the comment:
I tend to agree with the author; I've run into this myself. For
whitespace, I propose to use only the following: tab LF FF VT CR space.
These are the whitespace ASCII characters according to isspace() in libc.
(Unicode also treats hex 1C, 1D, 1E and
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1123>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1123>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Guido van Rossum added the comment:
This is essentially unsupported and unmaintaned example code. Feel free
to submit a patch though!
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
Here's a patch that fixes bytes.split and .rsplit. I'll hold off for a
while in case there's strong disagreement. I might add a patch for
bytes.strip later (it's simpler).
--
keywords: +patch
__
Changes by Guido van Rossum:
--
components: +Interpreter Core -Library (Lib)
type: rfe -> behavior
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__
___
Guido van Rossum added the comment:
Updated patch that also modifies bytes.*strip().
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__Index: Objects/b
Guido van Rossum added the comment:
New version with corrected docstrings and buffer support for *split() as
well. Added unittests.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__Index: Objects/b
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1125>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Changes by Guido van Rossum:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1094>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mai
Guido van Rossum added the comment:
Oops, I accidentally deleted the patch. Here is is again.
Thanks for the patch! I've applied it.
Committed revision 58072.
--
assignee: -> gvanrossum
nosy: +gvanrossum
resolution: -> fixed
status: ope
Guido van Rossum added the comment:
Committed revision 58093.
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Guido van Rossum:
--
assignee: -> georg.brandl
nosy: +georg.brandl
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1139>
__
___
Python-bu
Guido van Rossum added the comment:
I agree. I wonder if it should return Unicode as soon as *any* of the
arguments are unicode???
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
Actually, it already implements the best possible rules, *except* for
the special case of an empty 3rd argument. (When there are no
substitutions, it normally returns the input unchanged; but somehow an
empty input is handled with a shortcut even before that
Guido van Rossum added the comment:
Here's a patch.
--
assignee: -> gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1140>
__Index:
Guido van Rossum added the comment:
Here's a better patch that also fixes a few related issues.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1140>
__Index: Li
Guido van Rossum added the comment:
Fredrik, thoughts?
--
assignee: gvanrossum -> effbot
nosy: +effbot
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Guido van Rossum added the comment:
PythonMeister, what do you mean, "confirmed"? Your read loop ends printing
('total lines read ', 85014960)
which is the expected output. (It's one less than the number of lines
written due to a bug in the program -- it prints t
Guido van Rossum added the comment:
Thanks, Fredrik.
Fixed in 2.6.
Committed revision 58098.
Someone else could backport to 2.5.
Shouldn't be merged into 3.0.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Guido van Rossum added the comment:
Committed revision 58099.
(I had to backport test_typechecks.py myself, and fix one issue in abc.py.)
Are you going to backport _abcoll.py and its tests?
--
assignee: -> gvanrossum
nosy: +gvanrossum
resolution: -> accepted
status: open -&g
Guido van Rossum added the comment:
Folks, please focus on one issue at a time, and don't post such long
transcripts.
I know Py3k text I/O is very slow; it's written in Python and uses UTF-8
as the default encoding. We've got a summer of code student working on
an accelerating
New submission from Guido van Rossum:
Because writeable is not an English word; writable is.
Other names should be fixed as well.
--
messages: 55830
nosy: gvanrossum
severity: normal
status: open
title: Rename PyBUF_WRITEABLE to PyBUF_WRITABLE
versions: Python 3.0
Guido van Rossum added the comment:
Cool. This helps track down the bug a bit more; it's either in (our
routine) getline_via_fgets or it's in Microsoft's text mode line end
translation (which universal newlines bypasses).
I'm assigning this to Tim Peters, who probably sti
Guido van Rossum added the comment:
PJE's patch looks good to me too.
Stylistic nits:
- The proper name of the now-public null importer type ought to be
PyNullImporter_Type, to rhyme with e.g. PyString_Type
- There's a multi-line if that has the closing parenthesis in an odd
pl
Guido van Rossum added the comment:
I like this, but the patch has problems: you don't error-check the
return value from PyObject_Unicode() or PyUnicode_FromObject() (and why
do you need the latter call anyway?)
Also in the docstring I would reference str() instead of __str__().
There are
Guido van Rossum added the comment:
Confirmed. I'll fix it ASAP.
--
assignee: -> gvanrossum
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pyt
Guido van Rossum added the comment:
Confirmed. Weird.
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1151>
__
___
Python-bugs-list
Guido van Rossum added the comment:
Committed revision 58126.
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum added the comment:
There's one additional issue. If any of the items is a bytes, the call
should fail.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
New submission from Guido van Rossum:
==
ERROR: test_ftp (__main__.OtherNetworkTests)
--
Traceback (most recent call last):
File "Lib/test/test_urllib2n
Guido van Rossum added the comment:
> Should it really, even if the bytes is ascii-encodable?
Yes, really. We don't want to open up the same can of worms that made
working with Unicode such a pain in 2.x.
__
Tracker <[EMAIL PROTECTED]>
<http:
Guido van Rossum added the comment:
This is a good start, but I think that instead of using global variables
and functions, you should try to turn all those into instance variables
(of the ThreadTest class). That way the tests are truly independent.
Initialization should be taken care of in
Guido van Rossum added the comment:
/F?
--
assignee: -> effbot
nosy: +effbot, gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1160>
__
Guido van Rossum added the comment:
> Should "child" be replaced with "parent"?
No. I'm pretty much I wrote that. The use case I was thinking of is
the error handling in the child process after the exec fails. if you
were to use sys.exit() there, which raises Syst
Guido van Rossum added the comment:
I can't quite reproduce this, but I do see there's a problem with the
syntax error reporting:
Python 3.0a1 (py3k, Sep 12 2007, 12:23:06)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
Type "help", "copyright", "credits
Guido van Rossum added the comment:
Plese do submit a patch.
FWIW I think it's solved in Py3k, the tp_print slot is dead (as is any
use of the C stdio library).
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Guido van Rossum added the comment:
Looks Good, except I think it's a bad idea to release/acquire the GIL
for each character when writing the repr() of a string. Given that the
string is immutable and its refcount kept alive by the caller I don't
see a reason why you can't jus
Guido van Rossum added the comment:
looks good to me :)
--
assignee: -> brett.cannon
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1164>
__
___
P
Guido van Rossum added the comment:
Looks good. Check it in, with one small addition: add
#define PyBUF_WRITEABLE PyBUF_WRITABLE
for those NumPy folks who can't help writing the alternate spelling
('writeable' *is* in some dictionaries, though it is consistently
flagged as i
Guido van Rossum added the comment:
I don't see what the problem is. You requested strict_parsing=True, and
this is what strict parsing does.
--
resolution: -> wont fix
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<ht
Guido van Rossum added the comment:
Cartman, please refrain from using vulgarities in your sample code. It's
hard to take a bug report seriously with such variable names.
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://b
Guido van Rossum added the comment:
readline() goes through C stdio which makes it impossible to get
non-blocking I/O right. You should be using raw os.read() calls (until
python 3000 which will remove Python's reliance on C stdio).
--
nosy: +gvanrossum
resolution: -> wont fi
Guido van Rossum added the comment:
Hm. First of all, it seems the imageop module has completely missed the
Py_ssize_t changes.
Second, I don't think that "if ( x != len / y )" is a valid replacement
for "if ( x*y != len )" -- consider x==5, y==2, len==11.
Guido van Rossum added the comment:
Sounds like a good idea. Anyone care to check it in?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
On 9/20/07, Raghuram Devarakonda <[EMAIL PROTECTED]> wrote:
> Shouldn't the first clear() in the patch say "del
> self.data[key.upper()]" instead of "del self.data[key]"? I also think
> the patch should include doc c
Guido van Rossum added the comment:
This is only a problem with the 2.5 latex docs.
--
assignee: -> fdrake
nosy: +fdrake, gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Guido van Rossum added the comment:
Can you redo the patch while keeping the slot *position* (though not the
name or type)? The wasted space is minimal (4-8 bytes per type or class
object) and it means a lot for third party code if the positional struct
initialization never breaks due to
Guido van Rossum added the comment:
Thanks Neil!
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum added the comment:
Thanks!
Committed revision 58232.
--
assignee: -> gvanrossum
nosy: +gvanrossum
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Guido van Rossum added the comment:
Hm, doesn't this make t and t# identical to s and s#? Or if there are
still differences, are they still relevant? I vaguely recall that t and
t# were introduced as variants of s and s# that requested char buffers.
Since we're phasing out the who
Changes by Guido van Rossum:
--
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1201>
__
___
Python
Guido van Rossum added the comment:
Never mind. s/s# has explicit support for unicode. There is no t; t#
requires a buffer that's not unicode (that's what PyBUF_CHARACTER
amounts to).
If there's one area I'd love to refactor it's getargs.c.
What a sprawling me
Guido van Rossum added the comment:
Since it's basically a magic cookie, not a meaningful numeric value, I'd
propose sticking with backwards compatibility and fixing the 64-bit
version to return a signed version.
return x - ((x & 0x8000) <<1)
anyone?
Guido van Rossum added the comment:
Maybe the French internet is incompatible with the rest of the world? :-)
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
> In my opinion, Python urllib "should" be more practical and
> provide a way to read this kind of page. [quotes mine]
Totally agreed. Someone "should" submit a patch.
__
Tracker <[EMAIL PROTEC
Guido van Rossum added the comment:
Patience? :-)
Seriously, I'd lost track of this. It's now submitted:
Committed revision 58276.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.p
Changes by Guido van Rossum:
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1145>
__
___
Python
Guido van Rossum added the comment:
Why is this a Python bug?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1215>
__
___
Pyth
Guido van Rossum added the comment:
Please submit a patch -- this was mostly intended as demo code, I didn't
expect anyone to use it, let alone on Windows. :-)
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Guido van Rossum added the comment:
I think it would be better to get rid of the typedefs and use the public
Py* names everywhere?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
Can you be more specific as to on which line number the questionable
allocation happens, and which functions are depending on there being one
extra slot?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
Guido van Rossum added the comment:
Are you sure you're not missing the +1 on line 440 in PyType_GenericAlloc()?
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Guido van Rossum added the comment:
See http://bugs.python.org/issue1236 for a good repeatable testcase.
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/iss
Guido van Rossum added the comment:
This is a duplicate of bug# 1731717.
I asked Donovan Baarda, who told me:
"""
Last time I looked this had been fixed, admittedly in a bit of an ugly
way, on the svn head. I offered to do a patch to make it a bit cleaner,
but as it isn't r
Changes by Guido van Rossum:
--
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1237>
__
___
Python
Guido van Rossum added the comment:
It was deemed a documentation bug.
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1240>
__
___
Guido van Rossum added the comment:
This is how C stdio works in the subprocess. Python's subprocess.py has
nothing to do with it and can't do anything about it.
--
nosy: +gvanrossum
resolution: -> invalid
status: open -> closed
__
Guido van Rossum added the comment:
Since you've done so much work debugging this, would you mind submitting
a patch, including a unit test that confirms the desired behavior?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://b
Changes by Guido van Rossum:
--
assignee: -> gvanrossum
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1249>
__
___
Python-bugs-li
Guido van Rossum added the comment:
Thanks!
This patch looks fine, except the PyClear() call is unnecessary. I
suppose you copied it from the similar return clauses further down, but
there they clear an exception set by the _getbuffer() call. But just
calling PyObject_IsInstance() cannot set
301 - 400 of 5563 matches
Mail list logo
