Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 84f803fdc0d2 by Eli Bendersky in branch '3.2':
Issue #13365: correct an error in the documentation of str.expandtabs
http://hg.python.org/cpython/rev/84f803fdc0d2
New changeset 25191fe10da9 by Eli Bendersky in
Eli Bendersky eli...@gmail.com added the comment:
Committed. Thanks for contributing.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13365
___
Stefan Behnel sco...@users.sourceforge.net added the comment:
Reading the proposed patch, I must agree that it makes more sense in
ElementTree to support this as a serialiser feature. ET's tree model doesn't
have a notion of prefixes, whereas it's native to lxml.etree.
Two major advantages of
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 61976390763f by Eli Bendersky in branch '3.2':
Issue #13191: typo in argparse docs
http://hg.python.org/cpython/rev/61976390763f
New changeset edf944ab87c5 by Eli Bendersky in branch 'default':
Issue #13191: typo in
Changes by Eli Bendersky eli...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13191
___
___
Python-bugs-list
Eli Bendersky eli...@gmail.com added the comment:
Attaching a patch with a clarifying comment in Grammar/Grammar. Should be
enough for now?
--
keywords: +patch
Added file: http://bugs.python.org/file23656/issue13239.patch
___
Python tracker
Eli Bendersky eli...@gmail.com added the comment:
Brian, I see this text (along with the implementation) was added by you in
60197:0ab89e8bdedc
Could you state your opinion on this issue?
--
nosy: +brian.curtin
___
Python tracker
Antoine Pitrou pit...@free.fr added the comment:
Has it been reported?
Yes, in http://sourceware.org/bugzilla/show_bug.cgi?id=13401
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13309
New submission from Jason R. Coombs jar...@jaraco.com:
If the version or name passed to distutils.core.setup is unicode, this results
in a UnicodeDecodeError. Consider this setup.py:
from distutils.core import setup
setup(
name=u'issue13381',
version=u'1.0',
Ezio Melotti ezio.melo...@gmail.com added the comment:
This is a duplicate of #11638.
--
nosy: +ezio.melotti
resolution: - duplicate
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Jason R. Coombs jar...@jaraco.com added the comment:
First, the term 'gztar' doesn't appear in this ticket, and since the issue only
applies when sdist --format gztar, I mention that here.
Also, issue8396 suggests encoding using sys.getfilesystemencoding().
--
nosy: +jason.coombs
Nick Coghlan ncogh...@gmail.com added the comment:
Calling this one done - any further adjustments can be handled as new tracker
issues.
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker
Nick Coghlan ncogh...@gmail.com added the comment:
doctests by their very nature tend to overspecify things - that's why actual
regression tests should be written with unittest, while doctest is kept for its
originally intended purpose of testing examples included in docstrings and
other
Changes by Giampaolo Rodola' g.rod...@gmail.com:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3974
___
___
Changes by Florent Xicluna florent.xicl...@gmail.com:
--
nosy: +flox
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3974
___
___
Python-bugs-list
Brian Curtin br...@python.org added the comment:
But it is useless for terminating a process with os.kill() in combination
with signal.SIGTERM, which corresponds to a CTRL-C-EVENT.
SIGTERM does not correspond to CTRL_C_EVENT. They may be similar in what they
do, but os.kill on Windows only
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 477f633aa09d by Eli Bendersky in branch '2.7':
Issue #13191: typo in argparse docs
http://hg.python.org/cpython/rev/477f633aa09d
--
___
Python tracker
flacs 0f1...@gmail.com added the comment:
As a workaround, it is possible to make every glob character a character set of
one character (wrapping it with [] ). The gotcha here is that you can't just
use multiple replaces because you would escape the escape brackets.
Here is a function adapted
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8402
___
___
Python-bugs-list
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 369487785e9f by Eli Bendersky in branch '2.7':
Issue #13161: fix doc strings of __i*__ operators
http://hg.python.org/cpython/rev/369487785e9f
--
nosy: +python-dev
___
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 9fbaa190f011 by Eli Bendersky in branch '3.2':
Issue #13161: fix doc strings of __i*__ operators
http://hg.python.org/cpython/rev/9fbaa190f011
New changeset d58de3e9870a by Eli Bendersky in branch 'default':
Issue
Changes by Eli Bendersky eli...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13161
___
___
Python-bugs-list
New submission from Robert Xiao nneon...@gmail.com:
Lib/random.py in Python 3.2 contains the line
from __future__ import division
even though it is no longer necessary, as true float division is the default in
Python 3.
Trivial patch:
--- lib/python3.2/random.py 2011-09-03
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 3fdc5a75d6e1 by Brian Curtin in branch '3.2':
Fix #13384. Remove __future__ import in 3.x code.
http://hg.python.org/cpython/rev/3fdc5a75d6e1
--
nosy: +python-dev
___
Changes by Brian Curtin br...@python.org:
--
assignee: - brian.curtin
nosy: +brian.curtin
resolution: - fixed
stage: - committed/rejected
status: open - closed
type: - behavior
versions: -Python 3.4
___
Python tracker rep...@bugs.python.org
Brian Curtin br...@python.org added the comment:
Marked #1559549 as a dependency. I combine the patch in this issue with the one
over there.
--
dependencies: +ImportError needs attributes for module and file name
___
Python tracker
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset bcd347cd6bf2 by Florent Xicluna in branch 'default':
Use unittest.skipUnless to skip the test related to the glibc bug, issue #13309.
http://hg.python.org/cpython/rev/bcd347cd6bf2
--
Florent Xicluna florent.xicl...@gmail.com added the comment:
Thank you for the investigation, and the bug report to the glibc team.
I propose to close it as won't fix.
--
resolution: - wont fix
stage: test needed - committed/rejected
status: open - pending
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 02e4d3ebbb02 by Eli Bendersky in branch '2.7':
Issue #12875: explicitly specify default value of the optional 'flags' argument
to re.* functions. Closes #12875
http://hg.python.org/cpython/rev/02e4d3ebbb02
Changes by Eli Bendersky eli...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12875
___
___
Python-bugs-list
New submission from Eli Bendersky eli...@gmail.com:
The flags 're' accept are numeric underneath, and the current value of no
flags is just 0, which is also specified in the documentation as the default
value. However, using raw numeric values is not a good programming practice.
The
Eric V. Smith e...@trueblade.com added the comment:
Since the flags are OR'd together, I don't see what other value the no flags
parameter could have, other than zero. That said, I don't feel strongly about
it, and if it helps readability I'm not opposed.
--
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
The documentation now shows::
match(pattern, string[, flags=0])
Is it normal to have the brackets *and* the default value?
--
nosy: +amaury.forgeotdarc
status: closed - open
___
Python
Georg Brandl ge...@python.org added the comment:
No, it's not.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12875
___
___
Brett Cannon br...@python.org added the comment:
I think the clarification should be enough.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13239
___
Antoine Pitrou pit...@free.fr added the comment:
As Eric, I don't really think it's useful, and it might actually be confusing
(people will start wondering if there's a difference between 0 and NOFLAGS).
--
nosy: +pitrou
___
Python tracker
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
I thought we had a policy that future imports would never be removed.
--
nosy: +rhettinger
status: closed - open
___
Python tracker rep...@bugs.python.org
Brian Curtin br...@python.org added the comment:
That's news to me since it probably pre-dates my involvement around here. I'll
revert if that's correct.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13384
Ezio Melotti ezio.melo...@gmail.com added the comment:
I think a proper solution would be fixing #11957. Adding a NOFLAGS alias for 0
would help fixing #12875, but I don't think it will be useful/use otherwise.
--
___
Python tracker
Changes by Cody C cca...@gmail.com:
--
type: - crash
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12988
___
___
Python-bugs-list mailing list
Cody C cca...@gmail.com added the comment:
Still an issue as of 11/11/11.
--
nosy: +Cody.C
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12988
___
Benjamin Peterson benja...@python.org added the comment:
Things won't ever be removed from the __future__ module, but there's no harm in
removing ones with no effect.
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
Changes by Ned Deily n...@acm.org:
--
nosy: +amaury.forgeotdarc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12988
___
___
Python-bugs-list
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 0a94e2f807c7 by Antoine Pitrou in branch '3.2':
Issue #13193: fix distutils.filelist.FileList under Windows
http://hg.python.org/cpython/rev/0a94e2f807c7
New changeset 80d5040f2a78 by Antoine Pitrou in branch '3.2':
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
At one point, for 2.x at least, we weren't removing the from __future__
imports even after the feature became available.
--
___
Python tracker rep...@bugs.python.org
Ezio Melotti ezio.melo...@gmail.com added the comment:
AFAIK on 2.x there are a few modules that are supposed to work even with older
version of Python (I think I even saw one that is supposed to still be
compatible with Python 1.5).
I don't think this is the case for Python 3 though.
Ezio Melotti ezio.melo...@gmail.com added the comment:
FWIW Wikipedia says Other characters must be encoded in UTF-16 (hence U+1
and higher would be encoded into surrogates) and then in modified Base64.
So one possible interpretation is that while encoding a non-BMP char, it should
be
Eli Bendersky eli...@gmail.com added the comment:
Antoine, what's the outcome of people wondering about the difference? I don't
see what's bad about it, it's not as if people are writing (or supposed to
write) code that does arithmetic on these flag values. Their only usage is to:
1. Provide
Eli Bendersky eli...@gmail.com added the comment:
Amaury Georg,
Grepping through the docs disagrees with your claims ;-) Try to grep for
\=None\] to see what I mean. There are tons of places where default values
are placed inside the brackets. For example in
Ezio Melotti ezio.melo...@gmail.com added the comment:
If you want to provide no flags, I think it's easier to provide no flags,
rather than having to learn some NOFLAGS constant value that can be used to
make the fact that you are passing no flags more explicit than it already is.
I might
Ezio Melotti ezio.melo...@gmail.com added the comment:
but can we first get the convention documented somewhere?
+1
This was on my todo list, but feel free to open a new issue about it.
Grepping through the docs disagrees with your claims
That's because is not documented and not everyone
Eli Bendersky eli...@gmail.com added the comment:
Ezio, what do you suggest to do regarding *this* issue?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12875
___
Eli Bendersky eli...@gmail.com added the comment:
I propose the attached patch for the documentation. Any objections?
--
keywords: +patch
Added file: http://bugs.python.org/file23657/issue12767.1.patch
___
Python tracker rep...@bugs.python.org
Eli Bendersky eli...@gmail.com added the comment:
Graeme, any news on this?
If you re-do the patch for current tip and address the review comments, I think
we can commit it.
--
___
Python tracker rep...@bugs.python.org
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12188
___
___
Python-bugs-list
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11173
___
___
Python-bugs-list
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3849
___
___
Python-bugs-list
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10838
___
___
Python-bugs-list
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5088
___
___
Python-bugs-list
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10501
___
___
Python-bugs-list
Ezio Melotti ezio.melo...@gmail.com added the comment:
I suggest removing the [].
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12875
___
___
Ezio Melotti ezio.melo...@gmail.com added the comment:
+ This method wakes up at most *n* of the threads
+ The current implementation wakes up exactly *n* threads
+ A future, optimized implementation may occasionally wake up more than
+ one thread.
Isn't this a bit
Eli Bendersky eli...@gmail.com added the comment:
Hmm, I've just notice that this [default=val] pattern already exists in the
're' docs in 2.7, for example:
subn(repl, string[, count=0])
So my change was consistent within the documentation of this module.
No doubt, the conventions are
Eli Bendersky eli...@gmail.com added the comment:
Ezio, thanks for the catch. I missed that one. Attaching a new, fixed patch.
--
Added file: http://bugs.python.org/file23658/issue12767.2.patch
___
Python tracker rep...@bugs.python.org
New submission from Ezio Melotti ezio.melo...@gmail.com:
AFAIU the conventions for optional argument in the doc are as follow:
If a function has optional arguments and it accepts keyword arguments, the
func(arg=default) notation should be used, for example:
str.splitlines(keepends=False)
If
Ezio Melotti ezio.melo...@gmail.com added the comment:
I created #13386 about the conventions that should be followed in the doc.
Converting the whole page is fine with me.
--
___
Python tracker rep...@bugs.python.org
66 matches
Mail list logo
