Changes by A.M. Kuchling :
--
nosy: +akuchling
___
Python tracker
<http://bugs.python.org/issue2889>
___
___
Python-bugs-list mailing list
Unsubscribe:
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Committed to 2.5 in rev. 67693.
Do I need to 'svnmerge block' this revision to prevent
future merges from attempting to apply it to trunk?
--
status: open -> closed
___
Pyt
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
(copied from the Optik bug tracker -- I haven't tried
to replicate this.)
--
components: Library (Lib)
messages: 75848
nosy: akuchling
severity: normal
status: open
title: optparse: "1 2 3" should be seen a
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
(copied from the Optik bug tracker)
Related bug:
http://www.mail-archive.com/python-bugs-list@python.org/msg07227.html
Hi all,
It seems to me that the workaround to the above bug in optparse.py versio
1.5.3 introduces a new bug whe
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
(Copied from an anonymous submission
in the Optik bug tracker.)
There have been some recent discussions on comp.lang.python about the
optparse/optik module, and Steve Bethard suggested you might be interested
in some of the work done
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Re-opening, since Optik is no longer externally maintained.
--
assignee: -> akuchling
nosy: +akuchling
resolution: invalid ->
status: closed -> open
title: Documentation missing for OptionGroup class in optparse -&
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Re-opening as a documentation bug; we should at least make the re.sub
docstring match the text documentation.
--
assignee: -> akuchling
resolution: invalid ->
status: closed -> open
___
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
nosy: +akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4185>
___
__
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
The URL for module documentation generated by pydoc is no longer valid.
The attached patch corrects it for Python 2.5.3 by assembling the URL
using the Python version.
This patch shouldn't be forward-ported to 2.6 or 2.7; Sph
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
assignee: -> akuchling
nosy: +akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Should I backport the tutorial patch to the 2.6 tutorial?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Docstring portion of the patch applied to the trunk in rev.
66804; the change will appear in Python 2.6.1 and 2.7. Thanks!
--
resolution: -> accepted
status: open -> closed
___
Py
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I think this item doesn't need to be handled
by Mark. There's a comment at the top of
PC/getpathp.c giving the rules, so it's
just a matter of editing the text and adding reST
markup. But where in the docs should thi
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
assignee: gward -> akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1415508>
___
_
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Added to the documentation in rev. 3; thanks for your
patch!
Barry, there's also a patch adding two docstrings
to optparse.py. Is it
OK to add docstrings at the rc level, or should I wait until
the trunk is re-opened for 2.7?
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
vdupras's test case now passes with Python 2.6; we should apply
the patch to the test suite, though. We could ask Barry if he wants to
apply it to 2.6rc, or adding the test can wait until 2.7.
--
nosy:
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
A paragraph has been added in rev. 2, using
a modified version of your text. Thanks for
your suggestion!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Py
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Changed in rev. 0 to use the X.Y form. Thanks!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
The web pages seem to have been updated to correctly describe
the releases (now, they're release candidates). Thanks for your report!
--
nosy: +akuchling
resolution: -> fixed
status:
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Patch committed in rev. 66435.
Do we want to mention it in the tutorial? If not,
this issue could now be closed.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
The patch seems fine to me.
The docstring at the top of the file says:
It ends when Python causes a segmentation fault because the limit is
too high. On platforms like Mac and Windows, it should exit with a
MemoryError.
On my Macbo
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Changes to curses/ committed in rev. 66424.
Changes to threading/ committed in rev. 66425.
Changes to Demo/classes/Dates.py committed in rev. 66426.
Changes to md5driver/ committed in rev. 66427.
Rest of the changes committed in rev.
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
The attached patch documents the as_integer_ratio method; I'll commit it
once Barry allows commits.
Added file: http://bugs.python.org/file11482/stdtypes.txt
___
Python tracker <[EMAIL PRO
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
While writing docs for as_integer_ratio(), I noticed a few typos in the
docstrings of the new float methods. Patch attached.
--
nosy: +akuchling
Added file: http://bugs.python.org/file11481/float-docstri
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I've edited the suggested text and added it to the FAQ
in rev. 11722. Thanks for your contribution!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMA
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Documentation added in rev. 66272.
--
assignee: -> akuchling
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://b
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
components: -Documentation
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1674032>
___
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Applied in rev. 66268; thanks!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
This is fixed in the Python 2.6 documentation, where the HOWTOs
have been incorporated and the link is therefore automatic. Thanks for
your report!
--
nosy: +akuchling
resolution: -> fixed
status: open
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Fixed in rev. 66250 of trunk; thanks!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
itertools(product typo fixed in rev. 66231.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Many of the items are fixed in rev66217; thanks! A few of them were
fixed in the revisions I did this past weekend.
Not fixed:
* the links for apply() and map() in the PEP 371 section. Georg, is
there a way to override where the m
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Closing this item; the 2.6 "What's New" is done, except for any small
fixes that get reported.
--
resolution: -> fixed
status: open -> closed
___
Python tracke
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1985>
___
__
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Oh, and it might be more realistic to keep the 3.0 document as a set of
notes, and aim to have a more finished document in 3.1. ISTM it'll be
hard to finish writing it in time for a planned 3.0 release, even if you
spent your 20% w
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I agree; we don't want to require people to read the 2.6 document, and
then the 3.0 document to get a complete picture.
Besides, the organization of the 2.x documents may not be suitable for
the 3.0 document. The 2.x do
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
It's in good shape. There are a few items in my saved-email folder that
need to be added, and a few XXX markers here and there, but I've done
the large stuff, like writing a section on the multip
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
This patch was applied in rev. 65539, but then reverted; it turns out to
break Lib/test/test_parser.py. The exception is:
raise TestFailed(err)
test.test_support.TestFailed: Traceback (most recent call last):
File &qu
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I took one test and an idea from Niels' patch -- checking for the
existence of
os.stat as well as os.umask -- and applied it as rev. 65536.
Closing this issue now. Thanks, everyone!
--
assignee: -> akuchl
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Is there still time to do the backport for 2.6 at this late date?
--
nosy: +akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Closing -- I'm not going to work on this patch further, and it seems
irrelevant.
--
status: pending -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2305>
___
___
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I agree with tjreedy that this change is not very interesting for a demo
program. It would be more interesting to add larger features such as
different cellular automata, mouse or colour support, or something like
that.
Thanks for your
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
There's another use of os.open in the module in the MH class's
__setitem__ that doesn't provide a mode, but I think this occurrence is
harmless; it's truncating a file that always exists, so the existing
mode is pre
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Committed to trunk in rev. 65472, along with two corresponding tests.
--
nosy: +akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
This bug was fixed in 2.5 and 2.6, in rev. 60118 and 60119. Thanks for
your bug report!
--
assignee: -> akuchling
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3151>
___
__
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
bytearray's methods aren't consistent in what they accept.
append() takes either an in
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue839496>
___
__
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Closing, per the last comment.
--
resolution: -> fixed
status: pending -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Brett backed out my commit in r63002 because I forgot to include the
distutils.config module. Re-committed in r63014 and r63060.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I've applied Facundo's version of the patch in r63059.
--
nosy: +akuchling
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<h
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I think removing those old classes in 3.0 would be very sensible.
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Committed to trunk as r62998; thank you very much for the patch!
--
keywords: -easy
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Is the only purpose of the '-r' in sys.argv code to
avoid having to specify arguments multiple times when you're doing
multiple commands on a line? Perhaps it would be acceptable to then
just drop that bit of code
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Oh, and I don't understand Raymond's comment: sys.maxsize isn't an
alias for anything, but a new piece of information (the largest size of
containers). Maybe that information isn't useful, or 2.6 doesn't
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
djmitchell noticed this patch at the bug day -- should it be committed,
or just closed?
--
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
assignee: -> akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1858>
__
___
Python-b
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Applied to trunk to r62996.
--
assignee: -> akuchling
nosy: +akuchling
resolution: -> accepted
status: open -> closed
_
Tracker <[EMAIL PROTECTED]>
<http://bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I haven't assessed the patch, but wouldn't mind to see it applied to
an alpha release or to 3.0; +0 from me. Given that the next 2.6 release
is planned to be a beta, though, the release manager would have to rule.
Note th
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
assignee: -> akuchling
nosy: +akuchling
title: curses -> Curses sometimes fails to initialize terminal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
On my MacOS 10.4.11 machine, the example SSL server and client in the
documentation don't work, and they fail with a mysterious error 0. The
attached tarball contains my slightly-modified version of the scripts
and the test k
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Fixed in r62373; thanks for reporting this!
--
assignee: georg.brandl -> akuchling
nosy: +akuchling
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
&l
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
components: +Regular Expressions -Library (Lib)
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2636>
__
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
It was applied to 2.5-maint after 2.5.2 was released, BTW, so the change
isn't in any stable released version, only the 2.6 alphas.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2636>
__
___
Python-bugs
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2535>
__
___
Python-bugs
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
Note that _rbufsize is only set to 1 if the _fileobject's bufsize is set
to 0. So perhaps the bug is that some library is turning off buffering
when it shouldn't.
I don't see how you would fix this in the C code, othe
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1649238>
_
___
Python-bugs
New submission from A.M. Kuchling <[EMAIL PROTECTED]>:
The following modules or features aren't documented: future_builtins,
__self__ and __func__ on method objects, the print() function.
--
assignee: georg.brandl
components: Documentation
messages: 64230
nosy: akuchling, g
A.M. Kuchling <[EMAIL PROTECTED]> added the comment:
I intend to finish writing the 2.6 document; PyCon has been taking up
all of my free time the past few weeks, but obviously that's over now.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Changes by A.M. Kuchling:
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2220>
__
___
Python-bugs-list mailing list
Unsubs
A.M. Kuchling added the comment:
There's also an alternate syntax for this, called possessive
quantifiers: a*+, a++, a{m,n}+.
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
A.M. Kuchling added the comment:
Also referred to as an atomic group: see
http://www.regular-expressions.info/atomic.html for a discussion.
Fredrik, when you say "the engine has code for this", what do you mean?
--
nosy: +akuchling
Track
Changes by A.M. Kuchling:
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2225>
__
___
Python-bugs-list mailing list
Unsubs
A.M. Kuchling added the comment:
Marking as easy, assuming you add the exception; implementing MD5-sess
is probably not easy.
--
keywords: +easy
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
A.M. Kuchling added the comment:
Applied to 2.6 in rev. 61105; it will be merged up to 3.0 at some point.
Thanks for the patch!
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by A.M. Kuchling:
--
assignee: -> akuchling
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2169>
__
___
Python-bugs-li
Changes by A.M. Kuchling:
--
keywords: +patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2001>
__
___
Python-bugs-list mailing list
Unsubs
A.M. Kuchling added the comment:
I mention urllib because, as noted earlier in the discussion, code that
fetches resources over HTTP should really be caching (looking at the
Expires header, sending an ETag and an If-Modified-Since header, etc.).
It's difficult for us to add these featur
A.M. Kuchling added the comment:
* I like factoring out the .pypirc code into a separate class.
* Overall I think the patch is acceptable. We'd need to decide whether
the new .pypirc is considered suitable -- I don't remember the reaction
to it on the distutils-sig or catalog-
A.M. Kuchling added the comment:
Random notes on bugday.distutils.patch:
* dist.py: this change should definitely be applied, no matter what
happens to the rest of the patch.
* Yay! Lots of tests!
* distutils.pypirc: I'm doubtful of the finalize_options() here;
looking for '
A.M. Kuchling added the comment:
I went ahead and pulled the 2.6 test back into 2.5-maint in
rev. 61016, and then realized that Nick actually backported the
change in rev. 60727. I decided to leave it alone; the 2.6
test should still avoid the problem, has the additional
feature of using
Changes by A.M. Kuchling:
--
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1311>
__
___
Python-bugs
Changes by A.M. Kuchling:
--
keywords: +easy
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1291>
__
___
Python-bugs-list mailing list
Unsubs
Changes by A.M. Kuchling:
--
assignee: -> josiahcarlson
nosy: +josiahcarlson
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1519>
__
___
Python-bu
Changes by A.M. Kuchling:
--
assignee: -> akuchling
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1714>
__
___
Python-bugs-li
A.M. Kuchling added the comment:
Could you please provide a simple little test case for the bug? I'd
like to add a test when I commit the change, but you can probably boil
the problem down into a test faster than I can.
--
nosy: +akuchling
__
Tr
A.M. Kuchling added the comment:
The patch looks reasonable. I'll commit it on Monday when I'm on a
machine with a more up-to-date autoconf.
--
keywords: +64bit
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.p
Changes by A.M. Kuchling:
--
assignee: -> akuchling
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1204>
__
___
Python-bugs-li
Changes by A.M. Kuchling:
--
assignee: -> akuchling
nosy: +akuchling
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2170>
__
___
Python-bugs-li
A.M. Kuchling added the comment:
Andreas Lauer's suggested fix on #1092502 is correct, and fixes the
problem for the non-SSL IMAP class. Applied to 2.6 trunk in rev. 61008
and to 2.5-maint in rev. 61009.
--
resolution: -> fixed
status: open -
A.M. Kuchling added the comment:
Andreas Lauer's suggested fix is correct. Applied to 2.6 trunk in rev.
61008 and to 2.5-maint in rev. 61009.
--
nosy: +akuchling
resolution: out of date -> fixed
_
Tracker <[EMAIL PROTECTED]>
<http:
A.M. Kuchling added the comment:
Fredrik's suggested fix for SSL IMAP committed as rev. 61006, and to
2.5-maint in rev. 61007.
There still seems to be a problem with the non-SSL version. I'm looking
into that next.
_
Tracker <[EMAIL PROT
Changes by A.M. Kuchling:
--
assignee: -> akuchling
nosy: +akuchling
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1389051>
_
___
Python-bu
A.M. Kuchling added the comment:
The solution of adding caching, If-Modified-Since, etc. is a good one,
but I quail in fear at the prospect of expanding the saxutils resolver
into a fully caching HTML agent that uses a cache across processes. We
should really be encouraging people to use more
A.M. Kuchling added the comment:
Presumably this was fixed in 10.1 or 10.2 at some point, because
MacPython 2.3 comes as an installer. Closing as 'fixed'; Jack, please
re-open
if this is still relevant.
--
nosy: +akuchling
resolution: -> fixed
status: o
A.M. Kuchling added the comment:
Patch applied to 2.6 in rev. 60995, and to 2.5-maint in rev. 60998.
Thanks for reporting the problem, and for finding the bugfix!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
_
Tracker &
A.M. Kuchling added the comment:
Given that we now have a print-specific stylesheet
for the documentation, a printed version of the HTML page for a module
seems acceptable. I just looked at a print-preview of the pickle docs,
the output looks good, so IMHO we don't need to do anything sp
A.M. Kuchling added the comment:
Thanks for the suggestion. I've added index entries for __reduce__,
as well as __reduce_ex__ and a few others in rev. 60994
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
Tracker <[E
401 - 500 of 596 matches
Mail list logo