Georg Brandl <[EMAIL PROTECTED]> added the comment:
One more thing: with r63891 the encoding and errors arguments for the
creation of sys.stderr were made configurable; you'll have to adapt the
patch so that it defaults to backslashescape but can be overridden by
PYTHO
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Applied in trunk, 25-maint and 3k.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Review:
* Why is an empty string not printable? In any case, the empty string
should be among the test cases for isprintable().
* Why not use PyUnicode_DecodeASCII instead of
PyUnicode_FromEncodedObject? It should be a bit faster.
*
Georg Brandl <[EMAIL PROTECTED]> added the comment:
ascii() should probably be in future_builtins.
Whether the C API stuff and .isprintable() should be backported to 2.6
is something for Guido to decide.
___
Python tracker <[EMAIL PROTECTE
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Have you tried it? :)
The example is correct as it is.
--
resolution: -> invalid
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Okay, closing as "wfm".
--
resolution: -> works for me
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<h
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> loewis
components: +Extension Modules -Library (Lib)
keywords: +easy
nosy: +loewis
priority: normal -> high
type: -> crash
versions: +Python 2.6, Python 3.0
___
Python
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I would expect "abc".isprintable() give me a bool and "abc".printable()
to return a printable string, as with "abc".lower() and "abc".islower().
___
Python track
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r63958.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
What did you expect? Quoting from the docs,
"""The chars argument is not a prefix; rather, all combinations of its
values are stripped:
>>> 'www.example.com'.lstrip('cmowz.')
'exam
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
versions: +Python 3.0 -Python 2.3, Python 2.4
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> wont fix
status: open -> pending
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
New submission from Georg Brandl <[EMAIL PROTECTED]>:
This patch makes the 2.6 Mapping ABC use the 2.6 dict interface. It also
removes registering list as a KeysView, ValuesView and ItemsView.
--
assignee: gvanrossum
components: Library (Lib)
files: abcoll.diff
keywords: 26ba
Georg Brandl <[EMAIL PROTECTED]> added the comment:
OK, committed as r64018.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I found a few more bytes/str problems, committed patch in r64023.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Why not warn in the AST, like for the other syntax-related changes?
The relevant location is ast_for_arguments, line 680 in current SVN.
___
Python tracker <[EMAIL PROTECTED]>
<http://
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Hmm, I'd even go a step further and factor out the whole checking for
invalid/warnable names, like in Py3k's forbidden_name.
Also the warning text shouldn't start with uppercase a
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Also a test is missing.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3060>
___
__
New submission from Georg Brandl <[EMAIL PROTECTED]>:
It decodes the system strftime's result using TZNAME_ENCODING which is
also used to decode timezone names. This may be correct for timezone
names themselves (I don't know), but the strftime result is encoded in
the LC_TI
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I got it wrong too at first; the "logical line" refers to the last tuple
item, the line string, not the line *number* passed.
It should now be clear as of r64037.
--
resolution: -> fixed
sta
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed in r64033.
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Replace "upacking" with "unpacking" and you can commit it :)
___
Python tracker <[EMAIL PROTECTED]>
&
Georg Brandl <[EMAIL PROTECTED]> added the comment:
The macro at the top of the patch should be removed, then this can be
checked in.
--
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Attaching reviewed docs patch.
Added file: http://bugs.python.org/file10572/mpdocs.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed in r64067.
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2997>
___
___
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> works for me
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Patch committed to Py3k branch in r64138. Thanks all!
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: gvanrossum -> georg.brandl
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
versions: +Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> duplicate
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> duplicate
status: open -> closed
superseder: -> Remove cl usage from aifc
___
Python tracker <[EMAIL PROTECTED]>
<http://b
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Where does the strftime.c come from? It is not in the Python sources --
is this a Mac-specific thing?
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
> No, it returns a 2-character string.
Which hopefully is the proper surrogate sequence :)
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, added in r64201.
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
This is a proof of concept how to add methods to a structseq type.
Of course PyStructSequence_InitType could also get a companion
PyStructSequence_InitTypeEx that takes a PyMethodDef* array.
--
keywords: +patch
nosy: +georg.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I think the easiest way is to just call AddObject after inserting the
values.
I fixed this, and the leaking BuildValue references, in r64223.
--
nosy: +georg.brandl
resolution: -> fixed
status: open
Georg Brandl <[EMAIL PROTECTED]> added the comment:
You'll have to produce a test case for this "dropping" -- otherwise I
don't believe that 16 MB cause *any* memory problems at all.
--
nosy: +georg.brandl
status: open -> pending
_
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I agree with Antoine that the standard behavior is what you want in most
simple command-line scripts.
It's easy enough to replace the parser's exit function to just print the
message, or raise an exception.
--
nos
Georg Brandl <[EMAIL PROTECTED]> added the comment:
It is true that sys.maxunicode reflects whether the build is using UCS-2
or UCS-4; however, the size of Py_UNICODE is not fixed by that, look at
unicodeobject.h.
(Though I don't think we have platforms that actually *do* use sizes
o
Georg Brandl <[EMAIL PROTECTED]> added the comment:
The title is misleading -- if what you show is correct then "import nul"
doesn't succeed :)
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<ht
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r64300.
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Looks good to me.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3098>
___
___
Python
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Great! When finished with the docs, just check them in, I'll look over
it then.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I know about this and will think about possible ways out of it. Of
course if someone has a patch it will probably be faster.
--
components: +Documentation tools (Sphinx)
___
Python tracker &
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I disagree. The AST classes are auto-generated, the leading underscore
of _fields is there to avoid clashes with field names from the AST types.
This is similar to
http://docs.python.org/dev/library/collections#collections.somename
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed in r64461. Thanks!
--
resolution: -> fixed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I fixed the docstring in r64463 (2.5 branch, already fixed in trunk) and
expanded the connect() docstring in r64464.
--
resolution: -> fixed
status: open -> closed
___
Python tra
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, should be fixed with Sphinx r64465.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I don't maintain the 2.5 docs anymore, at least for such minor bugs.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Only a few things -- I've done them in r64477. This is now done, thanks!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http:/
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Why do you think ConfigParser should be a new-style class?
--
nosy: +georg.brandl
resolution: -> invalid
status: open -> pending
___
Python tracker <[EMAIL PROTECTED]>
<h
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> duplicate
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Can't reproduce on Linux on 2.6 or 3.0.
--
assignee: georg.brandl ->
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Already fixed in SVN. Thanks!
--
resolution: -> out of date
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, committed as r64536.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3211>
___
___
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> invalid
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Changing the locale changes string.letters -- that is expected behavior.
--
nosy: +georg.brandl
resolution: -> wont fix
status: open -> pending
___
Python tracker <[EMAIL PR
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed docs in r64619.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
You're right, I fixed that too in r64621.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed in r64624.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2775>
___
___
Python
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Added a link to PEP 324 in r64625. The other issues were explained by
Martin; it will be easier to read the subprocess docs in 2.6 where
they're all on one page.
--
resolution: -> fixed
status:
Georg Brandl <[EMAIL PROTECTED]> added the comment:
> Lib Ref/Built-in Types/Sequence Types/Bytes and Byte Array Methods
>
> The following set/frozenset and dict sections repeat (and for dicts,
> expands upon) the constructor interface from the Built-in Functions
> sectio
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed with r64629.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Well, that wouldn't be different if you had set the locale in your
prompt. In short, ``u'a' in string.letters`` can never work with any
string.letters except the default, English-only one, a
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed the Execute parameter in r64630. add_data was already fixed.
Assigning to Martin; if someone is to write usage info, it's got to be him.
--
assignee: georg.brandl -> loewis
nosy: +loewis
resolution: -> fixed
Georg Brandl <[EMAIL PROTECTED]> added the comment:
This is already on my to-do list. Thanks for raising it as an issue
though, I won't forget it so easily this way :)
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Paddy: IMO hasattr() is the "if it quacks like a duck" part of
duck-typing. It e.g. allows testing "hasattr(x, 'write')" to see if it's
a writable file-like object, and doing something else otherwise.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Fixed in r64634.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Added note in r64635.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Reworded a bit and applied as r64638.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Thanks, fixed in r64642.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: georg.brandl ->
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2351>
___
__
Georg Brandl <[EMAIL PROTECTED]> added the comment:
What real-life use case do you have for a condition that is a boolean
operation on two constant values anyway? Things like
while 1:
...
are properly optimized since they serve a useful purpose.
--
nosy: +georg.
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3279>
___
___
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Should be fixed in r64701...
--
nosy: +georg.brandl
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> georg.brandl
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Committed in r64722. Thanks everyone!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I don't understand the comment about poll().
In any case, I plan on referencing Doug's PyMOTW pages for all modules
he does, since they are indeed excellent tutorials.
___
Python tracker &
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Please bring it up on python-dev.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3292>
___
_
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I think you're right.
However, Martin, what flags except -I can/must we keep?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Georg Brandl <[EMAIL PROTECTED]> added the comment:
There is an ambiguity: did you mean """ " or " """ (spaces added for
clarity). Python does not count quotes, parentheses or similar in
strings, so the first occurrence of """ will cl
Georg Brandl <[EMAIL PROTECTED]> added the comment:
The last quote starts another string literal, so this is valid Python:
"""A "test"""" B"
and results in a string 'A "test B'. The lexer cannot know whether the
second s
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> loewis
nosy: +loewis
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> loewis
nosy: +loewis
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
The same is true for all other _bisect functions.
The pure Python versions from bisect work with negative indices by
interpreting them as in slice notation. This should probably be harmonized.
--
assignee: -> rhetti
Georg Brandl <[EMAIL PROTECTED]> added the comment:
This seems to be new in trunk; 2.5.2 raises a TypeError.
--
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> effbot
nosy: +effbot
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
priority: -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3299>
___
___
Georg Brandl <[EMAIL PROTECTED]> added the comment:
> It can also be used in constructors, to destroy an object that was just
> created if something goes wrong.
It appears that this is not true in debug builds: PyObject_NEW adds the
object to the global linked list of all ob
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> georg.brandl
nosy: +georg.brandl
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Georg Brandl <[EMAIL PROTECTED]> added the comment:
> If you open file with 'r' - all line endings will be mapped precisely to
> '\n' anyways, so it has nothing to do with 'U' mode.
No they won't -- only the platform-specific newline will. On Un
Georg Brandl <[EMAIL PROTECTED]> added the comment:
In addition to what Benjamin said, the Python docs are released together
with the source, so even if the issue was corrected in the 2.5 docs now,
the correction would not show up until 2.5.3 is released, which is not
even planned befo
Georg Brandl <[EMAIL PROTECTED]> added the comment:
I'd say go ahead.
--
nosy: +georg.brandl
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
resolution: -> wont fix
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: -> rhettinger
nosy: +rhettinger
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Georg Brandl <[EMAIL PROTECTED]>:
--
assignee: georg.brandl
components: Documentation, Documentation tools (Sphinx)
nosy: georg.brandl
priority: low
severity: normal
status: open
title: Use Python 3 lexer for 3.0 docs
versions: Pyth
1401 - 1500 of 5257 matches
Mail list logo