Eli Bendersky added the comment:
Committed to release27-maint, revision 88741
--
___
Python tracker
<http://bugs.python.org/issue11386>
___
___
Python-bugs-list m
Eli Bendersky added the comment:
Documentation fix and some unit tests committed in revision 88742
--
___
Python tracker
<http://bugs.python.org/issue11
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue11426>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Bendersky added the comment:
The attached patch tries to be true to the convention in other documentation
pages, by using "with" in complete code samples (examples), but not using it in
prompt (>>>) samples, where usage of "with" unnecessa
Eli Bendersky added the comment:
SilentGhost: yep, thanks for the reminder :)
--
___
Python tracker
<http://bugs.python.org/issue11426>
___
___
Python-bugs-list m
Changes by Eli Bendersky :
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue11426>
___
___
Python-bugs-
Eli Bendersky added the comment:
Would it not be better to just recommend Windows users not to put that last
backslash in at all? IIUC it's only needed to later append file names to
directory names, but that's better achieved with os.path.join
--
nosy: +eli
Eli Bendersky added the comment:
> Ezio Melotti added the comment:
>
> I would rephrase:
> +There is one subtle aspect to raw strings that is of special concern to
> Windows
> +programmers: a raw string may not end in an odd number of ``\``
> characters.
>
> to some
New submission from Eli Bendersky :
Report here:
http://stackoverflow.com/questions/5316928/python-os-path-isdir-is-slow-on-windows
It could be a problem with Windows itself, but I'm opening this to keep track
of the issue, just to be on the safe side.
--
components: Library
Eli Bendersky added the comment:
On Thu, Mar 17, 2011 at 12:46, Martin v. Löwis wrote:
I opened this in order not to forget to look at the implementation of isdir
on windows, making sure it's the most optimal thing we can do. If you know
it is, the issue can be closed as far as I'm
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue11625>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Eli Bendersky :
The comment string above the implementation of _PyBytes_FromStringAndSize in
Objects/bytesobject.c starts with:
/*
For both PyBytes_FromString() and PyBytes_FromStringAndSize(), the
parameter `size' denotes number of characters to allocate
Eli Bendersky added the comment:
Sure, I just wanted confirmation from another dev that it's indeed an error and
I'm not missing anything.
I suppose the fix is just replace "for both PyBytes_FromString() and
PyBytes_FromStringAndSize()" with just "for PyBytes_Fr
Eli Bendersky added the comment:
Yes it does, but the comment says something about "parameter 'size'" which is
clearly absent from the function signature of PyBytes_FromString.
--
___
Python tracker
<http://bug
Eli Bendersky added the comment:
I propose the attached patch (for the latest default branch). It simply removes
the first paragraph of that comment, since it's misleading and redundant. The
*last* paragraph explains the same thing just in a clear and correct way
(except that it also
Changes by Eli Bendersky :
--
keywords: +patch
Added file: http://bugs.python.org/file21354/issue11634.1.patch
___
Python tracker
<http://bugs.python.org/issue11
Eli Bendersky added the comment:
Patch reviewed by Nick Coghlan and committed
--
resolution: -> fixed
status: open -> closed
versions: +Python 2.7 -Python 3.2
___
Python tracker
<http://bugs.python.org/i
Changes by Eli Bendersky :
--
nosy: -eli.bendersky
___
Python tracker
<http://bugs.python.org/issue11071>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Eli Bendersky :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue11388>
___
___
Python-bugs-list
Eli Bendersky added the comment:
Terry, Nick - is it OK to commit a fix for the comments?
--
___
Python tracker
<http://bugs.python.org/issue9904>
___
___
Pytho
Changes by Eli Bendersky :
--
stage: -> needs patch
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue9904>
___
___
Python-
Eli Bendersky added the comment:
I committed the fixes to 3.3 (see no reason to backport these). So unless there
are objections I will close the issue in a few days.
--
stage: needs patch -> commit review
status: open -> pending
___
Python t
New submission from Eli Bendersky :
The documentation of subprocess.Popen mentions a function named list2cmdline():
On Windows: the Popen class uses CreateProcess() to execute the child
program, which operates on strings. If args is a sequence, it will be converted
to a string using
Eli Bendersky added the comment:
I also prefer (2) since I see no reason for the user to use list2cmdline()
directly, let alone from subprocess (had there been rationale for such a public
function it should probably be in another module).
As for 'it', I guess you can say it means &
Eli Bendersky added the comment:
Thanks for the pointer, Ross.
So I propose to remove the mention of list2cmdline from the documentation of
subprocess, explaining instead what it does to the path (since I think this
should be publicly known, otherwise it's just black magic).
I
Eli Bendersky added the comment:
Issue #11827 seems to be strongly related
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue10838>
___
___
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue11836>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Bendersky added the comment:
Attaching a proposed patch for 3.2, focusing only on the documentation for the
time being (I realize that deprecation is a loaded issue and should be probably
handled in a centralized manner).
The patch removes mention of list2cmdline, instead explaining its
Eli Bendersky added the comment:
On Wed, Apr 13, 2011 at 14:54, Boštjan Mejak wrote:
>
> Boštjan Mejak added the comment:
>
> Also, please fix the main title of the argparse section...
>
> from
> 15.4.
> argparse<http://docs.python.org/dev/library/argpars
Changes by Eli Bendersky :
--
resolution: -> fixed
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue9904>
___
___
Python-bugs-list
Changes by Eli Bendersky :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue11827>
___
___
Python-bugs-list mailing list
Unsubscri
Eli Bendersky added the comment:
Patch committed to 3.3, 3.2, 3.1, 2.7
In case no objections arise, I will close this issue in a couple of days
--
status: pending -> open
___
Python tracker
<http://bugs.python.org/issu
Eli Bendersky added the comment:
Thanks for the clarification, Éric
--
___
Python tracker
<http://bugs.python.org/issue9904>
___
___
Python-bugs-list mailin
Eli Bendersky added the comment:
Agreed. Will fix
--
keywords: +easy
nosy: +eli.bendersky
priority: normal -> low
resolution: -> accepted
versions: -Python 3.4
___
Python tracker
<http://bugs.python.org/i
Changes by Eli Bendersky :
--
resolution: accepted -> fixed
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue11855>
___
___
Pyth
Changes by Eli Bendersky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue11827>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Eli Bendersky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10912>
___
___
Python-bugs-list mailing list
Unsubscri
Eli Bendersky added the comment:
Can this be committed and closed? [it's still an annoying problem for some
Windows users who want to compile Python]
--
___
Python tracker
<http://bugs.python.org/is
Eli Bendersky added the comment:
> Eli, do you want to expand this patch further (and how :) or do you think
> it's still the version you want to commit? Can a core devel, then, give this
> patch a deeper look?
>
I will review this again in a couple of days and will commit.
Eli Bendersky added the comment:
Any news on this? Can you check that your patches apply for latest trunk and
commit them?
--
___
Python tracker
<http://bugs.python.org/issue11
Eli Bendersky added the comment:
Terry,
I've incorporated your suggestions except the new formulation for verbosity to
doctest.testmod, since it's not really clear which one is more accurate. I
think it's intelligible as it is now (especially given that test.support is for
Eli Bendersky added the comment:
Antoine, can you be more specific? I recall finding it quite useful when first
learning Python. Perhaps it can be improved in a few specific places, but
overall I don't think it's a bad document.
--
nosy: +eli
Eli Bendersky added the comment:
This issue Jean-Paul raises seems to be a plain error. select() certainly can
return that some given socket is both readable and writable (this is explicitly
discussed in Steven's APitUE $14.5), and I see no evidence in the
implementation of Pyt
Eli Bendersky added the comment:
Can this issue be closed?
--
___
Python tracker
<http://bugs.python.org/issue11015>
___
___
Python-bugs-list mailing list
Unsub
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue2091>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Bendersky added the comment:
In Python 3, the documentation no longer mentions that 'U' should not work with
'+' (or 'w' or 'a', for that matter), and the code throws ValueError if 'U' is
used with 'w' or 'a', but not
Eli Bendersky added the comment:
I think that if this note should stay in the docs at all, it should be as
concise as possible, so I like Terry's -1+2*(step<0) option. I also tested it
on a few more inputs and it works fine.
If there are no objections, I can commit it to python 2.7 d
Eli Bendersky added the comment:
It makes sense to bring this up for discussion on pydev, then. Perhaps it will
be decided to remove this document from the official documentation, possibly
relegating it to the Wiki.
In the meantime, is there an objection to removing the incorrect statement
New submission from Eli Bendersky :
>From the docs maillist, by Herman L. Jackson:
---
Hi,
When running the tokenize example at the bottom of
http://docs.python.org/py3k/library/re.html#match-objects
I received the following error:
Traceback (most recent call l
Changes by Eli Bendersky :
--
assignee: eli.bendersky ->
___
Python tracker
<http://bugs.python.org/issue12146>
___
___
Python-bugs-list mailing list
Unsubscri
Eli Bendersky added the comment:
The Tokenizer example seems to have appeared in 3.2, it's not present in 3.1
--
___
Python tracker
<http://bugs.python.org/is
Eli Bendersky added the comment:
This was fixed by Georg in 538a6b23b18f and 12a2c1085621
--
assignee: rhettinger ->
___
Python tracker
<http://bugs.python.org/issu
Changes by Eli Bendersky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12146>
___
___
Python-bugs-list mailing list
Unsubscri
Eli Bendersky added the comment:
Raymond, I see you assigned the issue to yourself. The assignment was removed
by mistake when I closed the issue - is this still something you need to look
at?
--
___
Python tracker
<http://bugs.python.
Eli Bendersky added the comment:
Éric,
I went over both the diffs and the HTML output from "make clean html" on the
latest 3.2 trunk. Looks good to me!
Just a tiny nit re unittest.rst, where it says "supports three command-line
options". This is the kind of comment t
Eli Bendersky added the comment:
Terry, when is the deadline for producing the patch for 3.2? Perhaps we should
at least submit the 2.7 patch for now so that it goes in for sure?
--
___
Python tracker
<http://bugs.python.org/issue2
Eli Bendersky added the comment:
I ran Misc/NEWS through rst2hml, and apart from unknown python-specific
interpreter roles, there are two warnings:
Misc/NEWS:64: (WARNING/2) Inline strong start-string without end-string.
Misc/NEWS:128: (WARNING/2) Inline emphasis start-string without end
Eli Bendersky added the comment:
A fix to Misc/NEWS was committed by Georg in revision 86550. Now Misc/NEWS no
longer causes warnings with `rst2html`. Éric - if this is what you meant, the
issue can be closed.
--
___
Python tracker
<h
Eli Bendersky added the comment:
I will write a codecs.rst for this. Any suggestion of where in c-api/index.html
it should be linked?
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue10
Eli Bendersky added the comment:
While preparing a .rst document for this, I ran into a possible inaccuracy in a
comment in codecs.h:
/* Lookup the error handling callback function registered under the
name error. As a special case NULL can be passed, in which case
the error handling
Eli Bendersky added the comment:
Submitting a patch. What was touched:
1. Include/codecs.h - minor inaccuracy and inconsistency in a comment
2. Doc/c-api/codec.rst - new reST documentation file for the codecs.h C API
3. Doc/c-api/utilities.rst - for linking to codec.rst, per Georg's sugge
Eli Bendersky added the comment:
Éric, although grepping for all such references may be tricky, could you
specify the places where you did see them? I guess a few fixed places is better
than none at all.
--
nosy: +eli.bendersky
___
Python tracker
Eli Bendersky added the comment:
Eric, I'm attaching a provisional fix for library/atexit.rst just to be sure
this is what you mean.
--
Added file: http://bugs.python.org/file19659/atexit.rst
___
Python tracker
<http://bugs.python.org/is
Changes by Eli Bendersky :
--
keywords: +patch
Added file: http://bugs.python.org/file19660/issue10461.1.diff
___
Python tracker
<http://bugs.python.org/issue10
Changes by Eli Bendersky :
Removed file: http://bugs.python.org/file19659/atexit.rst
___
Python tracker
<http://bugs.python.org/issue10461>
___
___
Python-bugs-list mailin
Eli Bendersky added the comment:
Amaury,
Thanks for the review & comments.
I'm attaching a fixed patch.
--
Added file: http://bugs.python.org/file19661/issue10439.2.patch
___
Python tracker
<http://bugs.python.or
Eli Bendersky added the comment:
Georg,
Thanks. Submitting fixed patch with 3-space indentation in directives.
--
Added file: http://bugs.python.org/file19662/issue10439.3.patch
___
Python tracker
<http://bugs.python.org/issue10
Eli Bendersky added the comment:
Eric, which whitespace change do you refer to. I changed to 4-spaces
indentation in the code sample to conform to PEP-8. Shouldn't I have?
--
___
Python tracker
<http://bugs.python.org/is
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue10468>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Bendersky added the comment:
>From IRC:
the PyUnicode*Error_Foo access functions are not documented
they are in exceptions.c / pyerrors.h
--
___
Python tracker
<http://bugs.python.org/issu
Eli Bendersky added the comment:
I'm trying to port the example in tutorial/stdlib2.rst, but the sample in
"working with binary data record layouts" fails (before my porting to 'with'...)
struct.error: unpack requires a by
Eli Bendersky added the comment:
Attaching patches for library/atexit.rst and for tutorial/stdlib2.rst
--
Added file: http://bugs.python.org/file19667/issue10461.atexit.rst.diff
___
Python tracker
<http://bugs.python.org/issue10
Changes by Eli Bendersky :
Added file: http://bugs.python.org/file19668/issue10461.stdlib2.rst.diff
___
Python tracker
<http://bugs.python.org/issue10461>
___
___
Pytho
Changes by Eli Bendersky :
Removed file: http://bugs.python.org/file19660/issue10461.1.diff
___
Python tracker
<http://bugs.python.org/issue10461>
___
___
Python-bug
Eli Bendersky added the comment:
SilentGhost,
Your patches look fine. I have a doubt re collections.rst, however - about the
Python prompt. The same issue is in faq/library.rst and I didn't want to touch
it because I thought that on the prompt personally I probably wouldn't use
Eli Bendersky added the comment:
On Sat, Nov 20, 2010 at 20:44, Ãric Araujo wrote:
>
> Ãric Araujo added the comment:
>
> Eli, SilentGhost: Please open other bug reports for doc errors like the
> struct one in stdlib2 or the r/rb one.
>
> SilentGhost: with stateme
Eli Bendersky added the comment:
Simon's patch fix for 3.2 looks good to me - applies cleanly to py3k and tests
pass.
--
___
Python tracker
<http://bugs.python.org/i
Eli Bendersky added the comment:
I will take a shot at this now. If there's anything special I should look out
for, let me know :)
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/is
Changes by Eli Bendersky :
--
Removed message: http://bugs.python.org/msg121903
___
Python tracker
<http://bugs.python.org/issue10470>
___
___
Python-bugs-list m
Eli Bendersky added the comment:
I'm attaching a patch for unittest/main.py that implements this.
However, something is funny with the tests of the unittest module. When the
patch is applied and the tests are run through regrtest.py, it complains that
sys.path is modified. I'm inv
Eli Bendersky added the comment:
Attaching a patch to unittest/test/test_program.py that fixes the sys.path
warning in regrtest
What happens is that with the new capability added to unittest (running
discovery when called as -m without args), a few tests in test_program now
cause discovery
Eli Bendersky added the comment:
Submitting a complete patch file for this:
1. Modified Lib/unittest/main.py to implement the change
2. Modified Lib/unittest/test/test_program.py to make the tests pass without
warnings from regrtest.py
3. Updated the documentation in Doc/library/unittest.rst
Changes by Eli Bendersky :
Removed file: http://bugs.python.org/file19738/unittest.main.diff
___
Python tracker
<http://bugs.python.org/issue10470>
___
___
Python-bug
Changes by Eli Bendersky :
Removed file: http://bugs.python.org/file19741/unittest.test.test_program.diff
___
Python tracker
<http://bugs.python.org/issue10470>
___
___
Changes by Eli Bendersky :
--
Removed message: http://bugs.python.org/msg121909
___
Python tracker
<http://bugs.python.org/issue10470>
___
___
Python-bugs-list m
Changes by Eli Bendersky :
--
Removed message: http://bugs.python.org/msg121918
___
Python tracker
<http://bugs.python.org/issue10470>
___
___
Python-bugs-list m
Eli Bendersky added the comment:
Attaching a patch for Doc/c-api/exceptions.rst
Added a new section named "Unicode exceptions", and documented the relevant
functions from Include/pyerrors.h
--
keywords: +patch
Added file: http://bugs.python.org/file19747/issue104
Changes by Eli Bendersky :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue10468>
___
___
Python-bugs-list mailing list
Unsubscri
Eli Bendersky added the comment:
Michael,
I feared this might be the case. Without knowing the module deeply, it's not
easy to be aware of all the possible paths, preconditions, and consequences
(and tests obviously didn't catch that). A suggestion - maybe documenting these
p
Eli Bendersky added the comment:
Éric,
Yes, in a consequent patch I fixed this - kept the formatted code indented at 3
spaces, while adhering to PEP-8 internally. If there's anything else, let me
know.
--
___
Python tracker
Eli Bendersky added the comment:
Terry, I agree with Simon re closing and opening a new feature request. This
issue has too much baggage in it, and you we always link to it. A new feature
request should be opened strictly for 3.2
If you want I can close this issue and open a new one, but I
Changes by Eli Bendersky :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue10516>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Bendersky added the comment:
Éric, good idea - I'll do it.
--
___
Python tracker
<http://bugs.python.org/issue9264>
___
___
Python-bugs-list m
Eli Bendersky added the comment:
There's something weird going on with cmdoption... I've applied for
subscription to the docs mailing list, but while I'm awaiting moderator
approval, here's the brain-dump. Suppose this option description:
.. program:: trace
.. cmd
Eli Bendersky added the comment:
Objects/listobject.c has a static function named list_clear used internally. Is
it possible to just expose this function as a clear() method?
One problem is that it has this strange comment in the end:
/* Never fails; the return value can be ignored
Eli Bendersky added the comment:
>
> Hi, I'm also looking at listobject.c also... if we want list.clear() to
> behave exactly like del list[], we may be able to just call list_ass_slice
> on the list. Similarly for list.copy which should behave like a=l[:]
>
Note that when
Eli Bendersky added the comment:
Georg,
Thanks. Of course it should be wrapped like the others :-)
Xuanji,
Yes, I will try to get in something preliminary today.
--
___
Python tracker
<http://bugs.python.org/issue10
Eli Bendersky added the comment:
Éric,
I sent an inquiry about this problem to the d...@python.org list. In the
meantime, I will implement it with the workaround you suggest (I checked it
works in this case too).
--
___
Python tracker
<h
Eli Bendersky added the comment:
Attaching a patch for list.clear():
1. Implements a new function in Objects/listobject.c named listclear() (to be
consistent with the other "method functions")
2. listclear() is registered in list_methods and just calls list_clear(),
returning
Changes by Eli Bendersky :
Removed file: http://bugs.python.org/file19834/unnamed
___
Python tracker
<http://bugs.python.org/issue10516>
___
___
Python-bugs-list mailin
201 - 300 of 1229 matches
Mail list logo