Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19218>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19232>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19266>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Aug 15, 2013, at 08:25 PM, Antoine Pitrou wrote:
>Barry, do you still want to keep this issue open?
I don't necessarily need to. We've patched the Ubuntu version to be safe, so
I guess we'll just carry that del
Barry A. Warsaw added the comment:
2.6.9 doesn't produce a SystemError afaict:
Python 2.6.9rc1+ (unknown, Oct 18 2013, 10:29:22)
[GCC 4.4.3] on linux3
Type "help", "copyright", "credits" or "license" for more information.
>>> content = b&#
Barry A. Warsaw added the comment:
On Oct 18, 2013, at 02:33 PM, Barry A. Warsaw wrote:
>2.6.9 doesn't produce a SystemError afaict:
Please note that 2.6.9 is security only, so the threshold for worrying about
things is a remotely exploitable security vulnerability that cannot be
re
Changes by Barry A. Warsaw :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue19279>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
The failure in test_discovery.py is odd. It's failing because
loadTestsFromModule() is being passed a keyword arguemnt use_load_tests=False.
On the surface, the failure makes sense because if you look in
test_discover.py, it's defining a
Barry A. Warsaw added the comment:
On the second failure, the expected output just needs to be updated. Is that
the right thing to do?
--
___
Python tracker
<http://bugs.python.org/issue16
Barry A. Warsaw added the comment:
I'm going to close this as invalid:
Python 3.3.2+ (3.3:247344a0d12e, Oct 18 2013, 13:14:59)
[GCC 4.8.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from socket i
Changes by Barry A. Warsaw :
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue17759>
___
___
Python-bugs-
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19307>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue12029>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
PEP 8 says:
"""
Class Names
Almost without exception, class names use the CapWords convention. Classes for
internal use have a leading underscore in addition.
"""
yet there are some notable exceptions in practice, such as c
Changes by Barry A. Warsaw :
--
assignee: -> barry
___
Python tracker
<http://bugs.python.org/issue19331>
___
___
Python-bugs-list mailing list
Unsubscrib
Barry A. Warsaw added the comment:
On Oct 21, 2013, at 08:41 PM, Nick Coghlan wrote:
>That said, I quite like Paul's suggestions.
As do I.
--
___
Python tracker
<http://bugs.python.org
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19375>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I always prefer to keep PEP 8 guidelines as succinct as possible. I've looked
over Ethan's patch and the other changes suggested in comments and come up with
what I think is a simple patch to improve the guidelines. I don't think we
need t
Barry A. Warsaw added the comment:
Does this affect 2.6? Is there a patch we need to get into 2.6.9 final?
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue18
Barry A. Warsaw added the comment:
On Oct 24, 2013, at 08:14 PM, Ned Deily wrote:
>Barry: yes, 2.6 is affected. See discussion on python-dev.
Thanks Ned for the background over on python-dev. Unless I hear objections
otherwise, I am not going to apply this to
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19435>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: -python-dev
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue19331>
___
__
Barry A. Warsaw added the comment:
Thanks Ethan, your latest patch is wonderful. Applied!
--
___
Python tracker
<http://bugs.python.org/issue19331>
___
___
Pytho
Barry A. Warsaw added the comment:
Is this issue still relevant?
--
___
Python tracker
<http://bugs.python.org/issue1294959>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Nov 07, 2013, at 04:05 PM, jan matejek wrote:
>> - I would like to see any new OS-dependent locations in the sysconfig
>> module, not the sys module.
>
>how would you propose to put the va
Barry A. Warsaw added the comment:
On Nov 07, 2013, at 03:40 PM, jan matejek wrote:
>To reiterate, our current solution is to introduce "sys.lib" (and "sys.arch",
>but that is never used anymore) that is either "lib" or "lib64", and use this
>
Barry A. Warsaw added the comment:
On Nov 07, 2013, at 04:56 PM, Matthias Klose wrote:
>I disagree about sys.implementation. It's useless and wrong for cross builds.
>Please use sysconfig instead. What sysconfig is maybe missing is a set of
>variables which you can rely on
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19524>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I completely agree with Tim. The 'this' module was a *joke* and a stealthy one
at that.
http://www.wefearchange.org/2010/06/import-this-and-zen-of-python.html
About the only thing I'd support is adding some comments to the code to either
Barry A. Warsaw added the comment:
I'm going to close this issue as invalid; it hasn't affected me on ecryptfs
$HOME on Ubuntu in a long time, so let's chalk it up to better ecryptfs
implementations now.
If you disagree, feel free to re-open this and provide m
Barry A. Warsaw added the comment:
I think we've had plenty of time to adjust to the abi tags. Does anybody think
that nearly 3 years later anything really needs to be done here?
--
resolution: -> wont fix
status: open -> closed
___
Pyt
Changes by Barry A. Warsaw :
--
assignee: barry ->
___
Python tracker
<http://bugs.python.org/issue9419>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Barry A. Warsaw :
--
assignee: barry -> doko
___
Python tracker
<http://bugs.python.org/issue16754>
___
___
Python-bugs-list mailing list
Unsubscrib
Barry A. Warsaw added the comment:
Should this issue still remain open? The original report described a chained
exception, which obviously doesn't happen in 2.7 (nor with Georg's changeset,
in 3.2, 3.3, or 3.4).
RDM's message implies there still may still be bugs lurking h
Barry A. Warsaw added the comment:
I'm looking at this issue again with an eye toward Python 3.4.
Raymond describes what I think is a reasonable way to use defaults:
>>> x = Template('$foo $bar')
>>> defaults = dict(foo='one', bar='two')
Barry A. Warsaw added the comment:
This seems like a reasonable request. Do you care to submit a patch with tests
and doc updates?
--
___
Python tracker
<http://bugs.python.org/issue1198
Barry A. Warsaw added the comment:
Alright, I'm going to close this issue. Please open a new bug for Python 2.7.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.
Barry A. Warsaw added the comment:
Indeed, this happens for me too in default head.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
Barry A. Warsaw added the comment:
Never mind, this is an intentional change:
- Issue #16754: Fix the incorrect shared library extension on linux. Introduce
two makefile macros SHLIB_SUFFIX and EXT_SUFFIX. SO now has the value of
SHLIB_SUFFIX again (as in 2.x and 3.1). The SO macro is
Changes by Barry A. Warsaw :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Isn't this already fixed? We have _sysconfigdata for this now.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python
Barry A. Warsaw added the comment:
Here's a patch, sans NEWS and any docs.
--
Added file: http://bugs.python.org/file32577/issue19555.txt
___
Python tracker
<http://bugs.python.org/is
Changes by Barry A. Warsaw :
--
title: "SO" config var not getting set -> SO configuration variable should be
deprecated in 3.4
___
Python tracker
<http://bugs.pytho
Barry A. Warsaw added the comment:
Note that obviously the DeprecationWarning is not raised if you do
sysconfig.get_config_vars()['SO']
but it still gets mapped to EXT_SUFFIX in that case.
--
___
Python tracker
<http://bugs.python.o
Barry A. Warsaw added the comment:
On Nov 11, 2013, at 06:27 PM, Marc Abramowitz wrote:
>What would be the way to express this now in Python >= 3.4?
For now, use sysconfig.get_config_var('EXT_SUFFIX') though if no one objects
to my patch, I'll restore '
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19560>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19563>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Nov 14, 2013, at 01:44 AM, Antoine Pitrou wrote:
>Do we want to cut a new release quickly in order to spread the fix?
I am working on a 2.6.10 right now. IMHO this is the only critical security
fix to warrant the two digit last version num
Barry A. Warsaw added the comment:
assertTrue(dtrt)
--
___
Python tracker
<http://bugs.python.org/issue19590>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I believe this has been fixed for a while.
--
___
Python tracker
<http://bugs.python.org/issue9878>
___
___
Python-bugs-list m
Barry A. Warsaw added the comment:
I also can't reproduce this in Python 3.3 or 3.4 on Trusty Tahr (what will be
Ubuntu 14.04).
--
___
Python tracker
<http://bugs.python.org/is
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue2506>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
Python-bugs-list
Changes by Barry A. Warsaw :
--
assignee: -> barry
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
Python-bugs-list
Barry A. Warsaw added the comment:
LGTM. Now that 3.4b1 is spun, I say go for it.
--
___
Python tracker
<http://bugs.python.org/issue19760>
___
___
Python-bug
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19824>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Nov 28, 2013, at 05:07 PM, anatoly techtonik wrote:
>This class could be more useful with the following example:
>
>>>> from string import Template
>>>> t = Template('$who likes $what')
>>>> who = &
Barry A. Warsaw added the comment:
A few notes about flufl.i18n's style. We chose this (extracted from the GNU
Mailman project) because $strings are *way* less error prone for translators
than %s strings, especially when you consider that some languages change the
order of placeholders.
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19837>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Note that just iterating over namespace doesn't trigger the problem, e.g.
instead of
for name, value in namespace.items(): pass
using
list(namespace.items())
seems to work.
--
___
Python tracker
Barry A. Warsaw added the comment:
Also seems to be triggered on 2.7 (with appropriate syntax adjustments in
bug.py)
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue19
Barry A. Warsaw added the comment:
D'oh! Should have looked closer. ;)
--
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-list m
Changes by Barry A. Warsaw :
--
title: possible memory corruption caused by for-loop iteration over
namespace.items() in a metaclass defining __new__ -> type.__new__() name
argument is ignored
___
Python tracker
<http://bugs.python.org/issu
Changes by Barry A. Warsaw :
--
resolution: invalid ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-
Changes by Barry A. Warsaw :
--
versions: +Python 3.3, Python 3.4 -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bug
Barry A. Warsaw added the comment:
At best, this is an undocumented (afaict) change in behavior in 3.3. Let's
boil it down:
-snip snip-
class Type(type):
def __new__(mcls, name, bases, namespace):
return super().__new__(mcls, 'foo', bases, namespace)
clas
Barry A. Warsaw added the comment:
I think this is due to the switch from Subversion to Mercurial, which if I'm
reading PEP 385 and remembering correctly, happened about the time of Python
2.6.7. IIRC, we released that source tarball from Subversion so you're seeing
svn build num
Changes by Barry A. Warsaw :
Added file: http://bugs.python.org/file33000/qualname-19888.py
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bug
Barry A. Warsaw added the comment:
I don't see the value in opening a new bug. Now that we understand what's
going on, let's just repurpose and retitle this one.
Run qualname-19888.py with Python 3.3 and you'll get:
Obj.__name__ foo
Obj.__qualname__ Obj
repr(Obj)
Barry A. Warsaw added the comment:
Oops, correct!
--
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue21044>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue21041>
___
___
Python-bugs-list mailing list
Unsubscribe:
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]
--
___
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22123>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
<http://bugs.python.org/issu
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21539>
___
___
Python-bugs-list
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.
--
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22195>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22257>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 wor
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 :
--
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue22327>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue16662>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
assignee: michael.foord -> barry
___
Python tracker
<http://bugs.python.org/issue16662>
___
___
Python-bugs-list mailing list
Un
Changes by Barry A. Warsaw :
--
versions: -Python 3.4
___
Python tracker
<http://bugs.python.org/issue16662>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 pa
Barry A. Warsaw added the comment:
pattern will have to be documented and accepted as official API
--
___
Python tracker
<http://bugs.python.org/issue16
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 :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue16662>
___
___
Python-bugs-list
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
i
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
&l
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
Barry A. Warsaw added the comment:
Note that this change broke eventlet:
https://github.com/eventlet/eventlet/issues/135
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue21
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22438>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
<http://bugs.py
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue9951>
___
___
Python-bugs-list mailing list
Unsubscribe:
2101 - 2200 of 2726 matches
Mail list logo
