Georg Brandl <[EMAIL PROTECTED]> added the comment:
You'll have to update the Pygments library; try a "rm -r tools/pygments;
make update".
--
resolution: -> works for me
status: open -> closed
___
Python tracke
Georg Brandl <[EMAIL PROTECTED]> added the comment:
There are also instances of set_daemon left in socketserver and
multiprocessing/dummy. How is that possible?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Benjamin, I think you're responsible.
--
assignee: -> benjamin.peterson
nosy: +benjamin.peterson, georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r66522. Also removed the last two paragraphs of the set
display explanation which were pasted from genexps and made no sense,
and added a sentence about {} not constructing a set.
--
resolution: -> fixed
sta
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Committed patch in r66523. At least for now, code and docs are
consistent again.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed in r66524.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed as r66525.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, this is already fixed in SVN and will be in the 2.6 docs coming
out soon.
--
resolution: -> out of date
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r66526.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Bruce is right.
I fixed "decorated", the duplicate "funcdef" and the "?" in r66527 and
r66528.
Bruce, usually adding comments with more issues, especially if they are
so small, is fine; however, since t
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Committed r66529.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
This was fixed some time ago on the trunk.
--
nosy: +georg.brandl
resolution: -> out of date
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r66530.
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Jean-Michel, you'll need to apply the idlelib/run.py patch; replace
sockthread.set_daemon(True)
with
sockthread.daemon = True
around line 75.
--
resolution: -> fixed
status: open -> closed
versions: +Pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Which version of Sphinx did you use to build the docs? The Python docs
currently need the unreleased SVN version (that will of course change
for the final release).
If you have a Sphinx release installed as a Python egg, it will cause
pr
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I think the patch is okay; I guess you're processing the result of
getproxies() yourself and relying on "no" being a key?
--
resolution: -> accepted
___
Python tracker &
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Docs done in r66534.
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Noted in r66535.
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: fixed ->
status: closed -> open
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed in r66541.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Amaury's patch looks good.
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Closing this one then.
--
nosy: +georg.brandl
resolution: -> duplicate
status: open -> closed
superseder: -> Regexp 2.7 (modifications to current re 2.2.2)
___
Python tracker &l
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks! Removed this and a few more references in r66577.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Gregor doesn't have commit rights. Patch looks OK, would you apply it
please, Ben?
--
assignee: -> benjamin.peterson
nosy: +georg.brandl
resolution: -> accepted
___
Pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Looks ok, like the 3.0 code. Benjamin, please review and commit.
--
assignee: -> benjamin.peterson
nosy: +georg.brandl
resolution: -> accepted
___
Python tracker <[EMAIL PR
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Looks fine. Since it is minor, why not commit it now?
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
It certainly isn't a feature. I don't immediately see how to fix it,
though. unicode_literals doesn't change the repr() of unicode objects
(it obviously can't, since that change would not be module-local).
Let's
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Regardless of the smiley, I certainly wouldn't object if you requested
permissions on python-dev...
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Though I can't look at the code at this time, I just want to express how
good it feels that you both are doing these great things for regular
expressions in Python! Especially atomic grouping is something I've
often wished
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
components: +Documentation -Documentation tools (Sphinx)
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Added in r66606.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
(It's called "cmember").
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3875>
___
___
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Hmm, I can't really tell what may cause the "Too many }" error. Can you
try and play around with sphinx.sty, commenting out stuff, to find where
it comes from?
___
Python tracker <
Georg Brandl <[EMAIL PROTECTED]> added the comment:
My apologies then.
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Actually this is all right. The generated HTML looks like this:
Blah¶
So the id is in the span tag, not the a tag. The link generated for the
¶ is a convenience so that you can right-click and say "copy link
location" if you wa
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Committed as r66626 (2.5 branch only).
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Committed in r66627 (2.5 branch only).
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
If that solves the problem, that is very curious indeed. There must not
be a \fi after \newif; its syntax is
\newif\ifname\default
Later it can be used as \ifname ... \fi.
What TeX distribution and version of tex/latex are you
Georg Brandl <[EMAIL PROTECTED]> added the comment:
You need to make your docstring a unicode string. Then both tests work
for me.
--
nosy: +georg.brandl
resolution: -> works for me
status: open -> closed
___
Python tracker <[EMAIL PR
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed typo 1) in r9, thanks for that. For 2), "iff" is a usual
abbreviation for "if and only if".
About your two questions, comments in modules are written in whatever
way the author likes to write his comments. T
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I don't see that inter-document links *wouldn't* work, except on antique
browsers that insist on tags only for defining anchors.
___
Python tracker <[EMAIL PROTECTED]>
<http://
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed the prints in r66680.
The multiprocessing docs are a special case because they arrived after
we "upgraded" examples in the documentation to Python 3.0 code.
--
resolution: -> fixed
sta
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> wont fix
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> invalid
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I don't see the bug in the code, nor what is solved by the code you propose.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Please stop wasting our time. There is no bug in how this class is written.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Georg Brandl <[EMAIL PROTECTED]> added the comment:
There's also an applyAsync left in the introductory Pool example.
Jesse, while you're at it, could you please add a blurb that some
examples won't work when tried at the interactive interpreter
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I e.g. tried a minimal example with Pool.map():
>>> from multiprocessing import Pool
>>> p = Pool(5)
>>> def f(x):
... return x*x
...
>>> p.map(f, [1,2,3])
Process PoolWorker-1:
Traceback (most
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Will it correctly distinguish between +0.0 and -0.0?
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Christian, I guess it's all fixed now?
--
assignee: -> christian.heimes
nosy: +christian.heimes, georg.brandl
resolution: -> fixed
status: open -> pending
___
Python track
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r66793.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed all of them in r66794.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I concur with Terry on all counts. Specifically:
1. How the underscores are displayed depends on the font you've selected
as your monospace font. Replacing them with an image is ugly and will
never look remotely nice.
2. I w
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Are you sure you're doing "make all-pdf" in the build/latex directory?
--
resolution: -> works for me
status: open -> pending
___
Python tracker <[EMAIL PROTE
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Yes, closing tickets (and changing metadata like priority) is only
possible for developers.
--
status: pending -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Would be nice, yes.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3288>
___
___
Python
Georg Brandl <[EMAIL PROTECTED]> added the comment:
[Sphinx issues are now tracked at http://code.google.com/p/sphinx --
moved the issue there.]
--
resolution: -> duplicate
status: open -> closed
___
Python tracker <[EMAIL PR
Georg Brandl <[EMAIL PROTECTED]> added the comment:
OK, no problem. I should have thought about that sooner. Happy TeXing :)
--
resolution: -> works for me
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I disagree that missing section numbers are a severe usability hit.
Especially in the context that the new docs are constantly updated,
there's no telling when section numbers will shift, misleading those who
only navigate by section
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed as r66854.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed as r66855.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
OK, committed as r66856, should get merged to 3.0 soon.
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Your analysis is correct -- the HTML is invalid. However, this problem
doesn't occur in new documentation since we don't use the system used
until 2.5 anymore.
--
resolution: -> wont fix
sta
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Duplicate of #4002.
--
resolution: -> duplicate
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Me too. There are too many cases where class statements can be executed
to get this right.
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl added the comment:
That was already fixed on trunk, but not yet merged to 2.6. I've done so now
in r77559.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python
Georg Brandl added the comment:
+1.
--
___
Python tracker
<http://bugs.python.org/issue6837>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Georg Brandl added the comment:
Duplicate of #7762.
--
resolution: -> duplicate
status: open -> closed
superseder: -> (C API) PyUnicode_Tailmatch documentation
___
Python tracker
<http://bugs.python.o
Georg Brandl added the comment:
Thanks, fixed in r77702.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Georg Brandl added the comment:
Thanks, fixed in r77703.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Changes by Georg Brandl :
--
assignee: georg.brandl -> rhettinger
___
Python tracker
<http://bugs.python.org/issue7764>
___
___
Python-bugs-list mailing list
Un
Georg Brandl added the comment:
Thanks, fixed in r77857.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Georg Brandl added the comment:
Thanks, that example was indeed wrong. ProtocolError is not meant to be raised
if the HTTP connection to the specified URI can't even be made, e.g. for
unknown hosts. Fixed in r77858.
--
resolution: -> fixed
status: open -
Georg Brandl added the comment:
Very likely, these functions are not meant to be anything but utilities. As
API functions, they also don't belong into pydoc.
--
assignee: georg.brandl ->
___
Python tracker
<http://bugs.python.or
Georg Brandl added the comment:
Would you like to contribute a patch?
--
___
Python tracker
<http://bugs.python.org/issue7733>
___
___
Python-bugs-list mailin
Changes by Georg Brandl :
--
resolution: -> duplicate
status: open -> closed
superseder: -> pydoc doesn't work from the command line
___
Python tracker
<http://bugs.pyt
Changes by Georg Brandl :
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7817>
___
___
Python-bugs-list
Georg Brandl added the comment:
I agree. Docstrings never hurt.
--
___
Python tracker
<http://bugs.python.org/issue7838>
___
___
Python-bugs-list mailin
Changes by Georg Brandl :
--
assignee: -> loewis
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue7847>
___
___
Python-bugs-list mailing list
Un
Georg Brandl added the comment:
If you document -X, you should also document -J.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue7
Georg Brandl added the comment:
I've added "use ... instead" now in r78018.
--
___
Python tracker
<http://bugs.python.org/issue7864>
___
___
Pyt
Georg Brandl added the comment:
Thanks, committed as r78024, r78025, respectively.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/iss
New submission from Georg Brandl :
This patch adds a loggerClass attribute to logging's Manager, and a
setLoggerClass() function to set it. If no loggerClass is set, the global
_loggerClass is used. This is for maximum backwards compatibility.
There are no doc updates as the Manager i
Georg Brandl added the comment:
You mean, instead of "klass"? It is used in the other setLoggerClass(), and
therefore consistent.
--
___
Python tracker
<http://bugs.python.
Georg Brandl added the comment:
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue7868>
___
___
Python-bugs-list mailing list
Unsubscribe:
Georg Brandl added the comment:
Why not the un-magic context manager, which has an exc_value attribute with the
exception?
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue7
Changes by Georg Brandl :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7848>
___
___
Python-bugs-list mailing list
Unsubscri
Georg Brandl added the comment:
I'd say go ahead and commit without test.
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue7835>
___
___
Changes by Georg Brandl :
--
assignee: -> benjamin.peterson
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue7826>
___
___
Python-
New submission from Georg Brandl :
test_memoryio.TextIOTestMixin has duplicate (and conflicting!) definitions of
test_relative_seek() and test_textio_properties().
--
assignee: pitrou
components: Tests
messages: 98994
nosy: georg.brandl, pitrou
priority: high
severity: normal
status
Changes by Georg Brandl :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue7870>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Georg Brandl :
test_heap has a duplicate "test_get_only" test method, and the one that's
overwritten seems to end up in an infinite loop.
--
assignee: rhettinger
messages: 98995
nosy: georg.brandl, rhettinger
severity: normal
status: open
title:
Georg Brandl added the comment:
Fixed in r78182.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7926>
___
__
Changes by Georg Brandl :
--
assignee: georg.brandl -> eric.smith
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue7928>
___
___
Python-
Georg Brandl added the comment:
Thanks, should be fine now in r78188.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7926>
___
_
Georg Brandl added the comment:
No, this is correct. isCallable() was deprecated since 2.0, but the
replacement was the builtin callable() until 2.6.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.p
Georg Brandl added the comment:
They exist only in interactive mode. They won't be present if you do e.g.
python -c "import sys; print dir(sys)"
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
&l
Georg Brandl added the comment:
Added a link to the checkout FAQ in r12861.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Georg Brandl added the comment:
The latter is no inconsistency; tuples are immutable, lists are not.
Therefore, for lists, __init__ is the initializer, not __new__. In order not
to duplicate argument checking, __new__ does nothing special with them.
--
nosy: +georg.brandl
Georg Brandl added the comment:
There's only so much free time developers can spend on Python. Also, most
demos still work in 2.x, even if they are unmaintained, ugly or demonstrate old
concepts. In contrast, most demos weren't tested after porting to 3.x, so many
of them don&
1701 - 1800 of 5257 matches
Mail list logo
