A.M. Kuchling added the comment:
Closing this issue.
--
nosy: +amk
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
A.M. Kuchling added the comment:
I'm not following Py3K development at all, but the patch is pretty short
and seems reasonable. I think mailboxes should be 7-bit clean in
theory, but have no idea if things are that tidy in practice.
__
Tracker <[EMAIL P
A.M. Kuchling added the comment:
Here's a patch against the 3.3 trunk.
--
Added file: http://bugs.python.org/file23765/functional-patch.txt
___
Python tracker
<http://bugs.python.org/is
A.M. Kuchling added the comment:
Yes, linking to the functional module was to point people to a module that
might be useful, even if it's not in the stdlib. A numeric processing or
socket handling HOWTO would also pretty much have to link to non-stdlib
sources. The purpose of document
Changes by A.M. Kuchling :
--
nosy: -akuchling
___
Python tracker
<http://bugs.python.org/issue2636>
___
___
Python-bugs-list mailing list
Unsubscribe:
A.M. Kuchling added the comment:
This patch looks unproblematic to me, unless we're trying to keep
platform-specific error codes out of errnomodule.c.
I removed Python 2.7 and 3.1 from Versions, guessing that this change would be
unacceptable in a bugfix release.
--
nosy: +akuc
A.M. Kuchling added the comment:
I'll close this issue, then. Maybe something fancier needs to be built atop
the AsyncExc() function to allow a single thread to terminate all other
threads, but unless someone actually presents a current use case (or a PEP),
there seems little to do. P
A.M. Kuchling added the comment:
Committed to 3.2 in rev. 84188; thanks, Adam!
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
A.M. Kuchling added the comment:
Not likely to be worked on, and whether to write such a guide is a question for
the docs editor (or the Doc-SIG).
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue2212>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue2209>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
status: pending -> open
___
Python tracker
<http://bugs.python.org/issue2657>
___
___
Python-bugs-list
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue3786>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1687125>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue5368>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue4254>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue9557>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1723038>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1512163>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1745108>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1671676>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1751519>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1599254>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1488934>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue2124>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1028088>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1483>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
assignee: akuchling ->
___
Python tracker
<http://bugs.python.org/issue1665333>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by A.M. Kuchling :
--
nosy: -akuchling
___
Python tracker
<http://bugs.python.org/issue2650>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by A.M. Kuchling :
--
nosy: -akuchling
___
Python tracker
<http://bugs.python.org/issue9124>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
keywords: +easy
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue839496>
___
__
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/issue3151>
___
__
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
___
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:
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:
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
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:
Closing -- I'm not going to work on this patch further, and it seems
irrelevant.
--
status: pending -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
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:
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:
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:
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:
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:
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
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:
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
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:
itertools(product typo fixed in rev. 66231.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
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:
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:
Applied in rev. 66268; thanks!
--
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
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:
Documentation added in rev. 66272.
--
assignee: -> akuchling
nosy: +akuchling
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://b
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:
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:
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:
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 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:
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 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:
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:
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:
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:
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?
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:
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
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:
Should I backport the tutorial patch to the 2.6 tutorial?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by A.M. Kuchling <[EMAIL PROTECTED]>:
--
assignee: -> akuchling
nosy: +akuchling
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
A.M. Kuchling added the comment:
I finally got around to benchmarking this change, and unfortunately the results
are not good.
I used the regex tests in the Unladen Swallow test suite, regex_effbot and
regex_v8. The tests are written for Python 2.x, but the fixes for 3.x are
A.M. Kuchling added the comment:
Actually, I really want someone to verify that measurement. As a control, I
tried running the call_method benchmark (after a few more xrange fixes). The
Python 3.x trunk version with my patch is measured as 1.0227x slower, even
though the patch only touches
A.M. Kuchling added the comment:
Bumping priority so this doesn't get forgotten before 3.2; it seems important
because it fixes noncompliance with a PEP.
--
nosy: +akuchling
priority: normal -> high
___
Python tracker
<http://bugs
A.M. Kuchling added the comment:
They were disabled in r50949, with the comment:
Disable these tests until they are reliable across platforms.
These problems may mask more important, real problems.
One or both methods are known to fail on: Solaris, OpenBSD, Debian, Ubuntu.
They pass
A.M. Kuchling added the comment:
Gabriel: could you please update the patch to take Antoine's comment into
account?
--
nosy: +akuchling
___
Python tracker
<http://bugs.python.org/i
A.M. Kuchling added the comment:
The patch seems obviously correct to me; there's no way a user of pythread.h
can make NO_EXIT_PROG be undefined. The patch no long applies cleanly to
thread_nt.h -- one hunk is rejected -- but it looks like the change in that
hunk has already been ap
A.M. Kuchling added the comment:
Closing this bug is fine with me.
--
nosy: +akuchling
resolution: -> works for me
status: open -> closed
___
Python tracker
<http://bugs.python.org/
A.M. Kuchling added the comment:
What exactly needs to be finished in the documentation? There are sections for
the epoll and kqueue objects, and the epoll section looks fine, if brief. Is
the problem that the kqueue section says things like 'filter-specific data'
with no e
A.M. Kuchling added the comment:
Backported to 2.6-maint in commit 78324.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
A.M. Kuchling added the comment:
Should this patch just be rejected, then? Or is the more general locking
suggested in msg88021 of interest?
--
nosy: +akuchling
___
Python tracker
<http://bugs.python.org/issue4
A.M. Kuchling added the comment:
Thanks for the patches! Two comments on the addchstr change:
* I think that, instead of checking for a list, the method should accept any
Python sequence; a tuple is perfectly reasonable, for example, and if the code
is changed to use
A.M. Kuchling added the comment:
Thanks for your bug report!
Unfortunately, the fix isn't quite right, because on Windows you can't delete
files that are open. I think an even simpler fix is just to remove that
locking; if self._locked is true, this process presumably has exclus
A.M. Kuchling added the comment:
Here's a patch that updates the 2.7 docs.
Adam, have you submitted a contributor agreement
(http://www.python.org/psf/contrib/)?
--
nosy: +akuchling
Added file: http://bugs.python.org/file16318/posix-statvfs-flag-doc
A.M. Kuchling added the comment:
Does the attached, slightly simpler patch, also fix it?
The patch just sets the .encoding attribute after
creating it with _SpoofOut().
The revised patch doesn't seem to break anything on MacOS; I don't have access
to Windows to test whether it s
A.M. Kuchling added the comment:
The original problem has been fixed since 2007. Improving the #if condition
doesn't seem very important to anyone, so I'll just close this bug.
--
nosy: +akuchling
resolution: -> fixed
status: o
A.M. Kuchling added the comment:
I tried figuring out to rebuild the codecs using the scripts in Tools/unicode/
but failed. Is the use of that directory documented anywhere?
--
___
Python tracker
<http://bugs.python.org/issue1097
A.M. Kuchling added the comment:
I can no longer confirm this bug, either; trying the scripts with the current
trunk doesn't seem to leak. Backing out Jeffrey's r61011 didn't bring the
problem back, so I'll just conclude that the problem has gotten fixed al
A.M. Kuchling added the comment:
Unfortunately I think this will break many users of tokenize.py.
e.g. http://browsershots.googlecode.com/svn/trunk/devtools/pep8/pep8.py
has code like:
if (token_type == tokenize.OP and text in '([' and ...):
If tokenize now returns LPAR, this co
A.M. Kuchling added the comment:
The stop_serving() code was only added on the Py3k branch
in rev59424. It was removed in rev60350,
which is a merge commit; the diff is
http://svn.python.org/view/python/branches/py3k/Lib/test/test_xmlrpc.py?r1=60094&r2=60350.
I don't know if
A.M. Kuchling added the comment:
Updating version; does someone want to revive this for 3.2?
--
nosy: +akuchling
versions: +Python 3.2 -Python 3.0
___
Python tracker
<http://bugs.python.org/issue2
Changes by A.M. Kuchling :
--
status: open -> languishing
___
Python tracker
<http://bugs.python.org/issue706392>
___
___
Python-bugs-list mailing list
Un
New submission from A.M. Kuchling :
While looking at #4440, I grepped for similar problems and found one in
platform.py in the following line:
if no_os_uname or not filter(None, (system, node, release, version, machine))
In 3.x, filter() returns an object, not a list, so 'not filter()&
A.M. Kuchling added the comment:
Thanks for your bug report and patch!
The original 2.x version was pretty ugly code with a lambda that used default
arguments, so I rewrote the line to be more modern; it now does
' all((x in abbrevs) for x in line.split())'.
Committed my version t
A.M. Kuchling added the comment:
Added a warning to 2.x trunk in r79607, and Gabriel's doc change in r79608.
This thread-unsafety seems specialized and rarely of great importance, so I
used the note:: directive, not warning::.
--
nosy: +akuchling
resolution: -> fixed
stat
New submission from A.M. Kuchling :
The examples of set operations in
http://docs.python.org/dev/library/stdtypes#dictionary-view-objects don't work
in the current 2.7 trunk:
-> ./python.exe
Python 2.7b1+ (trunk:80084:80085M, Apr 14 2010, 21:17:06)
[GCC 4.0.1 (Apple Inc. build 5
A.M. Kuchling added the comment:
Could I get a login on the buildbot to make a fix?
I bet the problem is with the stdscr object. PyCurses_InitScr()
does 'return (PyObject *)PyCursesWindow_New(stdscr);'.
PyCursesWindow_Dealloc() does:
if (wo->win != stdscr) delwin(wo->win)
A.M. Kuchling added the comment:
Here's a possible patch; it at least doesn't seem to break the module on MacOS,
though MacOS doesn't crash with the current code either.
--
keywords: +patch
Added file: http://bugs.python.org/file16935/free
A.M. Kuchling added the comment:
(commenting on a closed bug, because I'm not sure it should be re-opened)
While coming up with examples, I found a weird inconsistency. Was it
intentional for viewkeys() and viewitems() to support set operations, but not
viewvalues()?
>>> d
A.M. Kuchling added the comment:
The fix is easy, I think; just add Py_TPFLAGS_CHECKTYPES to the
PyDictValues_Type's definition.
--
___
Python tracker
<http://bugs.python.org/i
1 - 100 of 596 matches
Mail list logo