Changes by Guido van Rossum <[EMAIL PROTECTED]>:
--
nosy: +gvanrossum
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3555>
___
__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I worry that many things were not recoded in Misc/NEWS at all,
especially in the early days of 3.0 development (e.g. in the p3yk branch
:-).
I'm not sure if it's possible to fix this retroactively, however. As
long as we
Changes by Guido van Rossum <[EMAIL PROTECTED]>:
--
nosy: +gvanrossum
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3572>
___
__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Looking into this now. Will make sure it's included in beta3.
--
assignee: -> gvanrossum
priority: -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http:/
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Checked in patch 10 with minor style changes as r65838.
Thanks Matt for persevering! Thanks everyone else for contributing;
this has been quite educational.
--
resolution: -> accepted
status: open
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Reviewers: GvR,
Message:
Looks good. Go ahead and submit, assuming you've run full tests.
Description:
http://bugs.python.org/issue3560
Please review this at http://codereview.appspot.com/3003
Affected files:
Include/mem
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
PS. The PEP probably needs an update. And the docs.
http://codereview.appspot.com/3003
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
On 2008/08/19 17:18:45, GvR wrote:
> PS. The PEP probably needs an update. And the docs.
And Misc/NEWS
http://codereview.appspot.com/3003
___
Python tracker <[EMAIL PROTECTED]>
<http
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I like Armin's latest proposal: have Py_TPFLAGS_DEFAULT include
Py_TPFLAGS_HAVE_VERSION_TAG when compiling the core only. ISTR there's
a way to do this, but I can't find it right now.
_
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Please review the patch here: http://codereview.appspot.com/3005
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Submitted as r65874.
I will block this for 3.0; 3.0 extensions that want to mess with tp_dict
must explicitly disable this flag.
--
resolution: -> fixed
status: open -> closed
__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Looking into this now.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1179>
___
__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Latest patches applied to 2.5 branch: r65878.
And to 2.6 trunk: r65880.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Sure, go right ahead.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1878>
___
__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Did someone fix xmlrpc.client:1168 yet?
IMO it's okay to add encodebytes(), but let's leave encodestring()
around with a deprecation warning, since it's so late in the release cycle.
---
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Duly accepted. (Though if someone has a quick fix I'd be open to it. :-)
--
assignee: -> gvanrossum
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I think it's fine as it is. Incrementing the stack level more frequently
is a good thing since there used to be paths that didn't increment it at
all and hence could cause segfaults. The default is conservative since
inc
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
This will definitely not be in 2.6.
--
keywords: -26backport
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
The proper work-around is for the app to pass bytes into os.listdir();
then it will return bytes. It would be nice if open() etc. accepted
bytes (as well as strings of course), at least on Unix, but not
absolutely necessary -- t
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
So shutil should be fixed to pass a bytes value to os.listdir(). But
then os.remove() should be fixed to accept bytes as well. This is the
crux I believe: on Unix at least, syscall wrappers should accept bytes
for filenames. An
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
>> I do not accept an os.listdir() that raises an error because one
>> filename cannot be decoded. It sounds like using errors='replace' is
>> also wrong -- so the only solution is for os.listdir() to skip
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I'm not interested in the InvalidFilename class; it's an API
complification that might seem right for your situation but will hinder
most other people. However I *am* interested in a patch that makes
os.unlink() (a
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
See http://codereview.appspot.com/3055 for a code review of Victor's
latest patches.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Looks okay, although my taste would be to let the calls to
source_as_string() be slightly more verbose and include the "string,
bytes" part. While that has a little more redundancy, it is easier to
read, and possibly ea
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I wonder if we shouldn't hold off on this. It's a substantial amount of
new code. I'd be fine with it going into 3.0.1 since it's pure
optimization (IIUC!). But right now we want
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
To be honest, I don't see any harm in adding this now, especially since
rc1 hasn't been released yet.
--
nosy: +gvanrossum
___
Python tracker <[EMAIL PROTECTED]>
&
Changes by Guido van Rossum <[EMAIL PROTECTED]>:
--
priority: -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3780>
___
_
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Yes, please move this to 3.0.1 / 2.6.1. The hard part appears to be
making sure that it compiles *and* is correct on all conceivable
platforms...
___
Python tracker <[EMAIL PROTECTE
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Making this into a release blocker just so someone will look at it.
Needs to be decided & fixed by rc2 at the very latest.
--
nosy: +gvanrossum
priority: high -> release blocker
_
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
How hard would it be to fix dbm.dumb to accept strings as well?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Agreed. But we need to tread carefully -- fixing this might break other
stuff that has silently relied on it. Better try it ASAP.
--
nosy: +gvanrossum
___
Python tracker <[EMAIL
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Figured it out. Does anyone want to review?
--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11452/fix3629.diff
___
Python tracker <[EMAIL PROTECTE
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I think this isn't quite right.
Ideally a fix should maintain several important properties:
(1) Be able to read databases written by Python 2.x.
(1a) Write databases readable by Python 2.x.
(2) Use the same mapping between st
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Submitted as r66364.
I'll merge into 3.0 as well (it's clean merge).
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Changes by Guido van Rossum <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11458/unnamed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
2008/9/10 Martin v. Löwis <[EMAIL PROTECTED]>:
> I have now committed the change as r66362 (including the missing
> documentation updates), and ported it to 3.0 as r66363 (where I had to
> change the flag value and re
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Looks fine, except I used frozenset for the _alphanum* variables and
reverted to double quotes like the rest of the file. Submitted as r66366.
--
assignee: -> gvanrossum
resolution: -> accepted
status: op
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
2008/9/10 Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:
> Code point 0x0370 is now a printable character.
> r66381 corrected the failures by simply changing it to 0x0378, until the
> next unicodedata upgrade...
>
Changes by Guido van Rossum <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11461/unnamed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Given MvL's review, assuming it fixes the Czech problem, I'm all for
applying it.
___
Python tracker <[EMAIL PROTECTED]>
<http://
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Agreed. It's toplevel in 2.6. Let's keep it toplevel in 3.x.
--
assignee: gvanrossum -> loewis
___
Python tracker <[EMAIL PROTECTED]>
<http
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
The problem with doing this per 3.0 is that it's impossible to write a
conversion script.
I'm okay with adding a flag to enable this behavior though. Please open
a new bug with a new patch, preferably one that applies clea
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Hmm... much of the os.path machinery (and os.walk) probably doesn't work
with bytes, and neither do fnmatch.py and glob.py, I expect. Plus
io.open() refuses bytes for the filename, even though _fileio accepts
them. The latte
New submission from Guido van Rossum <[EMAIL PROTECTED]>:
Google just released ipaddr.py, a module that knows how to manipulate IP
addresses (both IPv4 and IPv6).
I have nothing to do with this module, but I suggest considering it for
inclusion in the standard library.
It fills a g
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
It would help if I added a link to the Google release:
http://code.google.com/p/ipaddr-py/
Description:
"
An IPv4/IPv6 manipulation library in Python.
This library is used to create/poke/manipulate IPv4 and IPv6 addresses
a
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
On Wed, Sep 24, 2008 at 9:07 PM, Martin v. Löwis <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis <[EMAIL PROTECTED]> added the comment:
> I see a list of owners in the code (although it's difficult to infer
> re
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
On Thu, Sep 25, 2008 at 10:57 PM, Gregory P. Smith
<[EMAIL PROTECTED]> wrote:
> The whole socket._io_refs thing looks like a real design flaw. What is
> its actual intended purpose?
The original purpose was to su
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
On Fri, Sep 26, 2008 at 5:47 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> Ok. Here's another possibility. It adds another optional parameter to
> listdir. If False, bytes strings can be returned. Otherwise, the
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
You can call it a leaky abstraction all you want, but most people think
of filenames as text strings most of the time, and we need to somehow
support this, at least for users who agree . I agree we also need to
support bytes strin
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
On Tue, Sep 30, 2008 at 8:21 AM, Martin v. Löwis <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis <[EMAIL PROTECTED]> added the comment:
> Here is a patch that solves the issue in a different way: it introduces
> sy
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Martin, can you check in your changes to add sys.setfilesystemencoding()?
I will check in Victor's changes (with some edits).
Together this means that the various suggested higher-level solutions
(like returning path-like objec
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
I have committed a somewhat modified version of Victor's latest patch as
r66743.
Assigning to MvL now for the sys.setfilesystemencoding() commit. Then
you can hand it over to the doc folks; something derived from
http://wiki
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Yeah, but I have no idea where I got the info, alas.
I would recommend to just delete the Alpha line, but who knows what it
means. And should we update this for each alpha or beta release???
--
assignee: gvanrossum -&g
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Reducing priority to critical, it's just docs and tweaks from here.
You should also support bytearray() in ntpath:
>isinstance(path, (bytes, bytearray))
No, you shouldn't. I changed my mind on this several t
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Assigning to Amaury for Windows fix first.
--
assignee: georg.brandl -> amaury.forgeotdarc
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
FWIW, I don't see a need to change macpath.py -- it's only used for
MacOS 9 and the occasional legacy app. OSX uses posixpath.py.
--
resolution: -> accepted
___
Pyt
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Sorry Amaury, but there's another issue.
test_ntpath now fails when run with -bb:
==
ERROR: test_expandvars (__main__
Guido van Rossum <[EMAIL PROTECTED]> added the comment:
Thanks Amaury!
On to Georg for doc tweaks. Summary:
- all the os.path functions now work on bytes as well, on all platforms
- only on Unix (but not OSX) do we recommend using bytes
- os.getcwdu() no longer exists
- os.getcwdb() r
Guido van Rossum added the comment:
Phillip, can you fix this in 2.6, 2.7, 3.1 and trunk? (There are certain rules
for merging fixes between branches but I don't recall the details. Contact
Benjamin or another active core developer via IRC if you need help.)
--
nosy: +gvanr
Guido van Rossum added the comment:
Marking this as release blocker to ensure the (one-line) fix makes it into 2.7
and 3.2.
--
priority: high -> release blocker
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/
Guido van Rossum added the comment:
All examples so far (*) have to do with our inability to have properly nested
blocks. If we did, I'd make the except clause a block, and I'd issue a syntax
warning or error if a nested block shadowed a variable referenced outside it.
Ditto for
Guido van Rossum added the comment:
On Mon, Feb 22, 2010 at 6:51 PM, Jeremy Hylton wrote:
> There's no reason we couldn't revise the language spec to explain that
> except clauses and comprehensions are block statements, i.e.
> statements that introduce a new block.
Howev
Guido van Rossum added the comment:
I don't think so. It's very marginal.
--Guido (on Android)
On Feb 23, 2010 8:52 AM, "Amaury Forgeot d'Arc"
wrote:
Amaury Forgeot d'Arc added the comment:
The above patch adds a new opcode (DELETE_DEREF),
Guido van Rossum added the comment:
Hey, can we all try to get along?
For anyone who didn't follow the link to r56841, that was mine (though
Christian Heimes provided the basis for much of the patch apart from
elementtree), and I wrote at the time:
"""I had to fix a f
Guido van Rossum added the comment:
I propose that we continue to see Fredrik as elementtree's "BDFL". If Fredrik
wants the API in 3.2 to be changed to be backwards compatible with 2.x, we
should do that, and damn the torpedoes (um, 3.1 compatibility).
I would do this ASAP;
Guido van Rossum added the comment:
You can't use (...) syntax in substitution strings, only \N references.
--
nosy: +gvanrossum
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python
Changes by Guido van Rossum :
--
nosy: -gvanrossum
___
Python tracker
<http://bugs.python.org/issue1771>
___
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
Exactly. I'm proposing that we don't bother with people who call
types.MethodType(), but we *do* bother converting code that calls
new.method().
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.p
Guido van Rossum added the comment:
Can you open a separate item for the Tkinter leak so you can close this one?
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
Just check these into the trunk, guys! Great!
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1528>
__
___
Python-bugs-list
Guido van Rossum added the comment:
Aren't there equivalent ways to spell those with the "new" module? How
about a fixer for that code (which may be easier to write)?
__
Tracker <[EMAIL PROTECTED]>
<http://b
Guido van Rossum added the comment:
I think the implementation is fine too (others will have to check it
more carefully) but I noticed that the promised functionality of -m
doesn't work yet: I created a file Lib/test/foo.py whose sole contents
was "from . import test_support".
Guido van Rossum added the comment:
Reducing priority and changing assignee since this is now just waiting
for a doc update.
--
assignee: gvanrossum -> tiran
priority: high -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Guido van Rossum:
--
assignee: -> gvanrossum
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1487>
__
___
Python-bugs-li
Guido van Rossum added the comment:
Does this still need to remain open?
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1504>
__
___
Guido van Rossum added the comment:
> You are right about the rest. Can you start a discussion on the list?
Well the only question is where to put these symbols, right? I guess I
still like putting them in sys best, for the ones that don't fit in
collections.
> The last time I tr
Guido van Rossum added the comment:
Please roll this back. The error message you added is inappropriate
when the parameter to a legitimate register() call is omitted, e.g.
collections.Sequence.register()
Since we got rid of unbound methods, the infinite recursion is gone;
that's a good e
Guido van Rossum added the comment:
I'd suggest giving it a different name, maybe float_info. sys.maxfloat
suggests the value is a float, like sys.maxint and sys.maxunicode.
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://b
Changes by Guido van Rossum:
--
assignee: -> georg.brandl
nosy: +georg.brandl
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1520>
__
Guido van Rossum added the comment:
Hmm... Seems there's a 16-bit-wide field somewhere. How do other ZIP
implementation deal with this?
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
Guido van Rossum added the comment:
> Whatever you say. But shouldn't we make people to use types.MethodType()
> or whatever we use as the new module for PyMethod_Type()? People are
> going to use types.MethodType() when they see the deprecation warning.
Well, if new.method is de
Guido van Rossum added the comment:
OK Georg, take 'er away!
--
assignee: gvanrossum -> georg.brandl
resolution: -> accepted
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Guido van Rossum added the comment:
PS. A note on backporting this to 2.6: I think it's sufficient if
"builtins" exists in sys.modules as an alias of "__builtin__" in 2.6.
Crys: go ahead and check in the fixer as well.
__
Tracker
Guido van Rossum added the comment:
Great, now check it in!
On Dec 2, 2007 6:01 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>
> Nick Coghlan added the comment:
>
> Posted v2 of the patch, which fixes the problem Guido noted, and
> improved the tests to make sure __p
Guido van Rossum added the comment:
looks good to me. Crys, can you do the honors?
--
nosy: +gvanrossum
resolution: -> accepted
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Guido van Rossum added the comment:
Oops, some tests fail. ctypes and hotshot at least.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1537>
__
___
Python-bugs-
Guido van Rossum added the comment:
This was done intentionally -- if you define a comparison without
defining a hash, the default hash will not match your comparison, and
your objects will misbehave when used as dictionary keys.
Can you give more details about the Zope issue? I agree that
Guido van Rossum added the comment:
I take it back, that was a build error. After cleaning out the build
directory the hotshot and ctypes tests pass.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
I think this is not quite right; you shouldn't return self unless it is
an exact string instance. If it is a subclass of PyString should make a
copy.
--
nosy: +gvanrossum
__
Tracker <[EMAIL PROTECTED
Guido van Rossum added the comment:
There's already an except clause for copystat() that ignores
WindowsError in copytree(). If copying this same code into copy2() makes
the OP happy I think we can place a similar except clause around the
copystat() call in copy2().
--
nosy: +gvanr
Guido van Rossum added the comment:
You have a point. Can you suggest a patch that fixes this?
Question though -- what semantics are used for __lt__ and __gt__ that
they don't require overriding __eq__?
__
Tracker <[EMAIL PROTECTED]>
<http://b
Guido van Rossum added the comment:
Fair enough.
Still, this would go much faster if someone other than myself could be
coerced into researching how to fix this (at least the Zope use -- I
haven't heard back from the OP).
__
Tracker <[EMAIL PROTECTED
Guido van Rossum added the comment:
Well, the name_op array is used for other purposes. Perhaps the main
issue is that the presence of any of these causes the "rich comparison"
functionality to be overridden. But please do look into this if you can!
Guido van Rossum added the comment:
Hm, that means there's a bug in the existing copytree() code too!
Can you check whether WindowsError derives from OSError? If it does,
your proposal won't fly.
--
resolution: rejected ->
status: c
Guido van Rossum added the comment:
Not quite, because we only want to ignore WindowsError.
Maybe this would work?
try:
WindowsError
except NameError:
WindowsError = None
try:
except os.error, err:
if WindowsError is not None or not isinstance(err, WindowsError):
raise
Guido van Rossum added the comment:
You're right, my code was wrong. Yours will be be correct if you add
"else:" in front of the raise. I also still prefer "WindowsError is
not None" over just "WindowsError".
On Dec 3, 2007 2:25 PM, Raghuram Devarakonda <
Guido van Rossum added the comment:
Look at the except clause in copytree(); it does a bit more,
collecting the errors and raising them later.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Guido van Rossum added the comment:
I will look into this for 2.6. No promises. Somebody ought to check
whether this does not cause problems for pdb.
--
resolution: rejected ->
status: closed -> open
versions: +Python 2.6 -Python 2.5
__
Tracker &
Guido van Rossum added the comment:
In r59341 I added a flush of stdout and stderr at the end of each
command that restores the following behavior:
>>> n = sys.stdout.write('X')
X>>>
I still need to change io.py to properly implement line buffering
though; the cur
Guido van Rossum added the comment:
Thomas, ping? What do you think of Martin's claim that the fix is
incorrect?
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python
1001 - 1100 of 5563 matches
Mail list logo