Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23731
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
Poor performance could fall under the category of bug fixes, so for an
in-maintenance mode release, a fix that does not in any way change user visible
behavior could be acceptable. It would probably be fine for 3.4 but I'm just
+0 on it. Larry's call
Barry A. Warsaw added the comment:
Ha! Apparently this bug broke coverage for the Mailman 3 source code:
https://bitbucket.org/ned/coveragepy/issue/360/html-reports-get-confused-by-l-in-the-code
--
___
Python tracker rep...@bugs.python.org
http
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19035
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
Let's just Won't Fix this. Use a contextlib.ExitStack.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12782
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12782
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23399
New submission from Barry A. Warsaw:
There is a subtle behavior difference between virtualenv and pyvenv. When you
create a venv with virtualenv, the symbolic links files venv/bin are
relative, while they are absolute with pyvenv. This means that virtual
environments created with virtualenv
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23342
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23228
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
That's a backward compatibility break since existing code may be expecting
None. At least it needs to be carefully considered, and should have no
possibility of be applied to anything before Python 3.5.
--
nosy: +barry
versions: -Python 2.7, Python
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23149
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Dec 31, 2014, at 01:54 AM, Nick Coghlan wrote:
As we've started working through the post-release PEP 440 changes, I think
this is definitely worthy of a separate PEP.
I'm open to discussion and ideas, but I want to caution against spreading
information
Barry A. Warsaw added the comment:
Targetting to 3.5 and nosying myself. It would be nice if it were possible to
suppress the help of an entire subparser, but I took a quick look at the code
and it seems tricky.
--
nosy: +barry
versions: +Python 3.5 -Python 2.7
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22995
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
I already pushed a fix.
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.4/builds/702/steps/test/logs/stdio
(although asyncio is still failing there but that should be unrelated)
--
status: open - closed
Barry A. Warsaw added the comment:
I'll take this one. I think it should be easy to add a test case, which I'll
do.
--
assignee: - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22966
Changes by Barry A. Warsaw ba...@python.org:
--
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22966
___
___
Python-bugs-list
Barry A. Warsaw added the comment:
Not counting importlib.h, here's the diff I'm going to apply to 3.4. It passes
all the existing tests and includes a new test for this behavior.
--
Added file: http://bugs.python.org/file37339/22966.txt
___
Python
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22966
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22966
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22914
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22869
___
___
Python-bugs-list mailing
New submission from Barry A. Warsaw:
I'm classifying this as a security issue, since using uuid_generate_time() --
i.e. the not _safe() variety -- does return collisions in real world cases that
we've seen, and those could have security implications. However, I don't know
that this can
Barry A. Warsaw added the comment:
On Nov 06, 2014, at 08:10 PM, Alex Gaynor wrote:
FWIW, I'm not convinced the pure python fallback code is sufficient either;
time.time() doesn't have the necessary resolution AFAIK? Also clock_seq is
generated using the random module's messerne twister
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22636
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22680
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
I changed the link to point here: https://docs.python.org/devguide/patch.html
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21189
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22627
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22597
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22562
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19642
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
components: +Library (Lib)
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22570
___
___
Python-bugs
New submission from Barry A. Warsaw:
pathlib is really nice, but currently it's rather inconvenient to use due to
the lack of support in other parts of the stdlib for Path objects. For
historical reasons, everything accepts string paths, but few places accept
Paths. As an example
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22570
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Oct 06, 2014, at 03:43 PM, Georg Brandl wrote:
I'd rather write str(path) all over the place than having to look up in the
docs each time if that specific API happens to support passing Paths
directly.
Have you tried to write a large-ish application using
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22555
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Oct 03, 2014, at 04:19 PM, Tshepang Lekhonkhobe wrote:
Looks like a safe change. There is only one user in all Debian sources, and
it's on Python 2:
http://codesearch.debian.net/search?q=email.__version__
Hahahahahahahaha
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 02:40 PM, Ram Rachum wrote:
I'd like Enum objects to expose their serial numbers.
Can you please provide some motivating use cases?
--
___
Python tracker rep...@bugs.python.org
http
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 02:28 PM, Ram Rachum wrote:
I suggest making Enum members orderable, according to their order in the enum
type.
Can you please provide a motivating use case?
--
nosy: +barry
___
Python tracker
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 03:35 PM, Ram Rachum wrote:
Just because I want to be able to get the `int` value of an enum object,
doesn't mean I want the enum object to *be* an `int`, which is what `IntEnum`
means. I don't want it to be comparable to an int, I don't
Barry A. Warsaw added the comment:
https://docs.python.org/3/library/enum.html#orderedenum
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22504
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 02:59 PM, Ram Rachum wrote:
Right now I want it for this:
http://bugs.python.org/issue22504
https://docs.python.org/3/library/enum.html#orderedenum
Another use case I can think of is that if you store enum values in a
database, you're
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 04:15 PM, Ram Rachum wrote:
The main principle is: If something has an important property (in this case
an enum object's numerical value), it should be publicly exposed.
I think this is a misunderstanding. Only IntEnum members have
Barry A. Warsaw added the comment:
On Sep 27, 2014, at 09:05 PM, R. David Murray wrote:
There is no longer a concept of a separate 'email' release from the stdlib
release. The __version__ string didn't get updated in either 3.3 or 3.4 (my
fault). I propose that we simply delete
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9951
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22385
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
Note that this change broke eventlet:
https://github.com/eventlet/eventlet/issues/135
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21308
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22438
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
I tend to agree. I don't even think it was documented. I wonder though if it
makes sense to at least mention this in the PEP and/or release notes for 2.7.9.
--
___
Python tracker rep...@bugs.python.org
http
New submission from Barry A. Warsaw:
redirect_stdout is almost exactly what I want, except I want to redirect
stderr! redirect_stdout.__init__() should take a 'stream_name' argument
(possibly keyword-only) which could be set to 'stderr'. I propose it's
implemented as setattr(sys
Barry A. Warsaw added the comment:
On Sep 11, 2014, at 02:25 PM, STINNER Victor wrote:
Why not adding a new redirect_stderr() function?
With a little refactoring redirect_stdout into a subclass, that would work
too.
--
___
Python tracker rep
Barry A. Warsaw added the comment:
On Sep 11, 2014, at 07:23 AM, STINNER Victor wrote:
The changeset d0ff527c53da5b925b61a8a70afc686ca6e05960 related to this issue
introduced a regression in test_unittest. The test now fails on
Windows.
Darn. I don't have Windows handy to work out a fix
Changes by Barry A. Warsaw ba...@python.org:
--
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
___
___
Python-bugs-list
Changes by Barry A. Warsaw ba...@python.org:
--
assignee: michael.foord - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
___
___
Python
Changes by Barry A. Warsaw ba...@python.org:
--
versions: -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
___
___
Python-bugs
Barry A. Warsaw added the comment:
One thing I really do not like about Rob's last patch is that it exacerbates
the documentation discrepancy for loadTestsFromModule(). As previously
mentioned, use_load_tests arg was already not documented, and now the patch
adds another undocumented pattern
Barry A. Warsaw added the comment:
pattern will have to be documented and accepted as official API
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
Barry A. Warsaw added the comment:
So, I think what I'm going to do is change the sig of the method to:
def loadTestsFromModule(self, module, *args, pattern=None, **kws):
I.e. the new `pattern` arg will be keyword-only. *args and **kws will be parsed
for use_load_tests usage
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
New submission from Barry A. Warsaw:
Lots of them, just like this:
==
FAIL: test_NULL_ob_type (test.test_gdb.PrettyPrintTests)
Ensure that a PyObject* with NULL ob_type is handled gracefully
Changes by Barry A. Warsaw ba...@python.org:
--
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22327
___
___
Python-bugs-list
Barry A. Warsaw added the comment:
On Aug 30, 2014, at 07:34 PM, Ethan Furman wrote:
In other words, this was a bug that no one noticed for many many releases,
and I'm not sure we should fix it in 2.7 now.
Arguments for fixing?
-1 on fixing it, but we *can* document workarounds. Here's what
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22257
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22195
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Aug 06, 2014, at 09:43 PM, Nick Coghlan wrote:
I'd be +1 on a PEP to also expose it as a namespace builtin.
Is a PEP necessary? Seems like a rather isolated and simple enhancement.
--
___
Python tracker rep
Barry A. Warsaw added the comment:
I like it. Thanks for the contribution! Assigning to myself since I plan on
working to land this in 3.5.
--
assignee: - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21539
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21539
Barry A. Warsaw added the comment:
I'm not in favor of changing object() but exposing types.SimpleNamespace as
built-in namespace() doesn't seem like such a bad idea, especially given Tim's
penultimate Zen aphorism.
--
___
Python tracker rep
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22123
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21041
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
Aren't negative indexes well defined in Python? E.g.
p = Path('/tmp/tmp123/foo/bar/baz.xz')
p.parents[len(p.parents)-2]
PosixPath('/tmp')
p.parents[-2] should == p.parents[len(p.parents)-2]
--
___
Python
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21044
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21736
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
I'm -0 on this patch. I can understand that in some sense, frozen modules do
semantically have an associated file, but OTOH, once they're frozen the
connection to their file is broken. Also, I think anything that assumes
__file__ exists is simply broken
Barry A. Warsaw added the comment:
PBP might be reasonably used to justify it for the frozen case. I just don't
want to use that as a wedge to define __file__ in *all* cases, even when no
reasonable file name exists.
--
___
Python tracker rep
Barry A. Warsaw added the comment:
The os.chmod() will fail if path is a symlink. At the very least it must be
guarded by a `not os.path.islink()` call like above it. I'll add this check to
3.4 and 3.5.
--
nosy: +barry
___
Python tracker rep
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21643
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21539
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
I've just been writing some new code to use pathlib and ran into this one
myself. An exist_ok=False is fine, although it's a slight shame that for
backward compatibility we can't adopt os.makedirs() signature exactly
Barry A. Warsaw added the comment:
On May 27, 2014, at 08:48 PM, Antoine Pitrou wrote:
What do you mean by that? The os.makedirs() signature is
os.makedirs(name, mode=0o777, exist_ok=False)
Right, but this is Path.mkdir's signature:
Path.mkdir(mode=0o777, parents=False)
so it's too late
Barry A. Warsaw added the comment:
Agreed! I'll update the PEP. Thanks.
--
assignee: - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21540
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21540
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7776
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Apr 16, 2014, at 10:12 PM, Matthias Klose wrote:
distutils/sysconfig still parses the Makefile and config header; it should
use the same approach now as the toplevel sysconfig module.
Why do we still have two sysconfig modules?
--
nosy: +barry
Barry A. Warsaw added the comment:
The `python3` binary package is a sort of meta package that brings in the
interpreter (and some ancillary stuff) for all supported Python 3 versions.
For Ubuntu 14.04 that will be just python3.4. But if you want to build the
interpreter from source (e.g
Barry A. Warsaw added the comment:
On Apr 14, 2014, at 05:47 PM, R. David Murray wrote:
OK, so the devguide currently has
sudo apt-get build-dep python3
which did something on Glenn's machine, but did not enable him to build the
optional packages. So the question is, what should we put
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20895
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Mar 20, 2014, at 08:29 AM, STINNER Victor wrote:
from quopri import decodestring as _qdecode
from email.encoders import _bencode, _qencode
AFAICT, _qdecode is only used in email/messages.py, so perhaps it's better to
import it there and remove it from
Barry A. Warsaw added the comment:
On Mar 20, 2014, at 01:32 PM, R. David Murray wrote:
Well, one reason is I was afraid mailman might be using them. So if you are
cool with it, that removes that objection.
Nope, neither the 2.1 or 3.0 code uses those methods AFAICT.
The other reason
Barry A. Warsaw added the comment:
On Mar 13, 2014, at 05:15 AM, Éric Araujo wrote:
The source contains :meth:`self.gettext`, and Sphinx adds the parentheses
when creating markup for a function, probably because it’s common to say
things like “the len() function”. There is a Sphinx config
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20899
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20890
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20884
___
___
Python-bugs-list mailing
Barry A. Warsaw added the comment:
On Mar 06, 2014, at 05:31 PM, Larry Hastings wrote:
Larry Hastings added the comment:
According to #19021, this actually requires six revisions:
6a1711c96fa6
fa160c8145e5
efaf12106d68
7ecee9e0dc58
10ea3125d7b8
488ccbee6ee6
Is that correct?
Yes, at least
Barry A. Warsaw added the comment:
On Mar 06, 2014, at 06:41 PM, Serhiy Storchaka wrote:
I thought that 6a1711c96fa6 is already in RC1, that is why I hadn't opened
cherrypick issue for this. 6a1711c96fa6 is critical change because it not
only fixes one annoying warning, but it also fixes wrong
Barry A. Warsaw added the comment:
On Mar 06, 2014, at 05:43 PM, Larry Hastings wrote:
What do you want me to do? Hold off while you determine the correct set of
changes, or proceed with these six?
I have just verified that if you take the rc2 tarball and apply these six
changesets, it 1
Changes by Barry A. Warsaw ba...@python.org:
--
priority: normal - release blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19021
Barry A. Warsaw added the comment:
I've testing this patch on Ubuntu, and it seems to fix the problem. My quick
testing doesn't show any new problems, but we'll only know for sure once the
new Python 3.4 package hits the archive and folks start updating to it. So far
so good though.
Larry
Barry A. Warsaw added the comment:
Nosying Doko, since I think he may want to get this fix into Debian, if Larry
does not cherry pick it into 3.4.0 final.
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19021
901 - 1000 of 2236 matches
Mail list logo
