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 ques
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
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20895>
___
___
Python-bugs-list mailing list
Unsubscribe:
A Hettinger added the comment:
The specific thing I'm interested in is the custom extension
"1.3.6.1.4.43167.0.0", but all of the X509 data should be imported.
Client shows both the openssl and python outputs. I would expect anything the
ssl system doesn't explicitly know
Changes by A Hettinger :
Added file: http://bugs.python.org/file34625/cert.pem
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
Changes by A Hettinger :
Added file: http://bugs.python.org/file34624/Server.py
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
Changes by A Hettinger :
Added file: http://bugs.python.org/file34623/Client.py
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
A Hettinger added the comment:
There was a request on the python-dev to check this on windows 8.
I confirm the same behavior.
Windows 8.1 Pro 64bit
Python 3.4.0 32bit (release)
Installed current user:
Does not show up in Add/Remove Programs
Installer correctly sees installation and can remove
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 r
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 rem
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 Sphi
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20899>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20890>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20884>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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,
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
>488ccbe
Changes by Barry A. Warsaw :
--
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/issue19021>
___
___
Python-bugs-list mai
Barry A. Warsaw added the comment:
On Feb 28, 2014, at 09:42 PM, Serhiy Storchaka wrote:
>Note that the changeset 6a1711c96fa6 introdused several errors (mostly tests
>failures), so it needs other changesets to fix it. Related changesets which
>should be cherry picked: 6a1
Barry A. Warsaw added the comment:
http://bugs.python.org/issue19021
--
___
Python tracker
<http://bugs.python.org/issue20808>
___
___
Python-bugs-list mailin
New submission from Barry A. Warsaw:
This commit fixes the traceback we're seeing on Ubuntu with Python 3.4, in
Popen.__del__ on interpreter shutdown.
--
assignee: larry
components: Interpreter Core
messages: 212443
nosy: barry, doko, larry
priority: release blocker
severity: n
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
<http://bugs.python.org/issue19
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
Barry A. Warsaw added the comment:
On Feb 27, 2014, at 07:23 PM, Antoine Pitrou wrote:
>Hmm... if this *already* affects Ubuntu users, shouldn't this be fixed in 3.4
>proper? It's extremely likely that someone else will be affec
Barry A. Warsaw added the comment:
If this fixes the problem, shouldn't the issue be closed and a NEWS item added?
I'm going to test the patch locally.
--
___
Python tracker
<http://bugs.python.o
Barry A. Warsaw added the comment:
On Feb 27, 2014, at 03:46 PM, STINNER Victor wrote:
>Serhiy fixed the issue #19255 with the changeset 6a1711c96fa6, but this
>changeset will wait Python 3.4.1.
Okay, thanks. I was reviewing and rather liked the less invasive patch, but
if this one is
Barry A. Warsaw added the comment:
We're seeing this in Ubuntu now that 3.4 is the default.
https://bugs.launchpad.net/python/+bug/1284469
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/is
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20770>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Feb 20, 2014, at 06:13 AM, Larry Hastings wrote:
>Benjamin, Barry: I take it #20261 should go in to 3.4.0?
Yes please!
--
title: 3.4 cherry-pick: b328f8ccbccf pickle shouldn't look up dunder methods on
instances -> 3.4 cherry-pick: b
Barry A. Warsaw added the comment:
Bumping to release blocker so Larry can make a determination.
--
nosy: +larry
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/issu
Changes by Barry A. Warsaw :
--
nosy: +rbcollins
___
Python tracker
<http://bugs.python.org/issue20687>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
See issue #20687
--
___
Python tracker
<http://bugs.python.org/issue16997>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
The change for issue #16997 82844:5c09e1c57200 introduced a regression with
testtools. See attached file and instructions for reproducing it (it requires
the testtools package).
--
components: Library (Lib)
files: test_expected_failure.py
keywords
Barry A. Warsaw added the comment:
We just discovered that this change breaks testtools. I will file a new bug on
that.
--
___
Python tracker
<http://bugs.python.org/issue16
Barry A. Warsaw added the comment:
On Feb 18, 2014, at 07:57 PM, Serhiy Storchaka wrote:
>This is sad. Because after a release, change it will be much harder.
OTOH, if default-pickling-by-name could be overridden, so can
default-pickling-by-va
Barry A. Warsaw added the comment:
On Feb 17, 2014, at 07:03 AM, Serhiy Storchaka wrote:
>
>Currently enums are pickled by values. It means that if the value of enum is
>platform depending, pickling one enum you can unpickle other enum on other
>platform.
It's probably a good
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20534>
___
___
Python-bugs-list mailing list
Unsubscribe:
A. Libotean added the comment:
> Which encoding are you using, such that the difference in length between
> encoded and decoded messages is significant?
I agree right off the bat that the error in size is not significant. Only the
length of the last appended line is computed erroneously
A. Libotean added the comment:
You can go ahead and close this.
I ran some tests and concluded that indeed the IO system will take care of the
line separators.
Sorry to have wasted your time.
--
___
Python tracker
<http://bugs.python.
Gustavo J. A. M. Carneiro added the comment:
Regardless, if you don't mind, take this patch for Python 3.5 to avoid ctypes,
at least in the Linux case (I don't have Windows to test). Creating a proper
extension module is safer and really not that hard...
--
keywords: +p
Gustavo J. A. M. Carneiro added the comment:
I have narrowed it down to one line of code:
ctypes.create_string_buffer(16)
That is enough to create 7 objects that have reference cycles.
[, {'__module__': 'ctypes', '__doc__': None,
'__weakref__': , '
Gustavo J. A. M. Carneiro added the comment:
Well, this isn't a big problem, but I have an application that needs to run
with the GC disabled, since it causes pauses of a couple of seconds each time a
full collection runs (we have a few million objects allocated). I will run the
GC only
New submission from Gustavo J. A. M. Carneiro:
If you try the attached program, you will find that for every iteration the
uuid.uuid4() call generates objects that contain reference cycles and need the
help of the garbage collector. This is not nice. If I make the ctypes module
not able to
Changes by A Hettinger :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from A Hettinger:
I have crafted an ssl cert which contains a custom extension, when I check the
cert using OpenSSL on the commandline, I clearly see the extension, but when I
have the server try to pprint.pprint(s.getpeercert()), I do not see these
fields.
Overall, I think it
Barry A. Warsaw added the comment:
On Jan 31, 2014, at 04:23 PM, R. David Murray wrote:
>If backward compatibility is the concern, I'd think you'd just want to
>restore that one message.
Yeah. I think the tests are a little more difficult to adjust in that case,
and of course,
Barry A. Warsaw added the comment:
So, here's a patch that should work. One thing I'm not positive about is that
this is a more expansive change then just merging the two messages in the one
case in the original description. But it probably makes sense to be
consistent. Or sho
Barry A. Warsaw added the comment:
What do you think of combining the error messages, e.g.
No JSON object could be decoded, expecting value: line 1 column 1 (char 0)
?
--
___
Python tracker
<http://bugs.python.org/issue20
New submission from Barry A. Warsaw:
Run the attached file under Python 3.3 and you get:
No JSON object could be decoded
Run the same file under Python 3.4 and you get:
Expecting value: line 1 column 1 (char 0)
So a couple of things:
Since the error message changed, it makes it difficult to
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20309>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Jan 20, 2014, at 05:10 PM, Gerrit Holl wrote:
>This is potentially confusing. The documentation in this section has not
>made any mention of %-based substitutions. Rather, a novel reader may, at
>this point, think that {}-based substitution is n
Barry A. Warsaw added the comment:
I ran into this recently while porting nose to 3.4. I duped
http://bugs.python.org/issue20261 to this issue, but note that in
http://bugs.python.org/issue20261#msg208109 I notice that the presence or
absence of __getnewargs__() regresses the specific
Barry A. Warsaw added the comment:
I'll go ahead and dupe this to 16251, but will note the __getnewargs__()
regression in 3.4.
--
superseder: -> pickle special methods are looked up on the instance rather
than the type
___
Python tracke
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue16251>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Hmm, actually, this is a regression in Python 3.4. Let's amend the test class
to include a __getnewargs__():
class Picky(object):
"""Options container that returns None for all options.
"""
def __getstate_
New submission from Barry A. Warsaw:
I've been debugging a crash in nose 1.3.0, the root cause of which turned out
to be an instance containing an attribute which itself was an instance of the
following class (boiled down):
class Picky:
def __getstate__(self):
return {}
A. Libotean added the comment:
Let me write also a test for this and come back with a reply.
--
___
Python tracker
<http://bugs.python.org/issue20136>
___
___
A. Libotean added the comment:
Sure, will come back shortly with a patch.
--
___
Python tracker
<http://bugs.python.org/issue20137>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
On Jan 06, 2014, at 08:23 PM, Larry Hastings wrote:
>Could you live with this being checked in to 3.4?
For sure!
--
___
Python tracker
<http://bugs.python.org/issu
Barry A. Warsaw added the comment:
It seems a little unfortunate that you lose the symbolic default, especially
since the expanded number just appears random.
>>> print(inspect.signature(os.stat))
(path, *, dir_fd=None, follow_symlinks=True, fake=9223372036854775807)
>&g
New submission from A. Libotean:
Current implementation of RotatingFileHandler ignores the encoding when
computing the entry byte length.
I've attached a modified version that will compute the entry lenght in bytes.
--
components: Library (Lib)
files: rotatingfilehandler.py
mes
New submission from A. Libotean:
The StreamHandler implementation uses hardcoded Unix/Linux line separators.
This generates inconveniences when running on Windows as the file viewers
expect DOS line terminators.
I've attached a fix that will use os.linesep as the line terminator thus m
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue20096>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Thanks for the patch! I don't care if the old email address is retained in the
test data (maybe it's even a good thing those point to nonexistent addresses
:). Definitely change the one in py
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19984>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Oops, correct!
--
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-list mailing list
Unsubscribe:
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)
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 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 :
--
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
Changes by Barry A. Warsaw :
--
resolution: invalid ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-
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
Barry A. Warsaw added the comment:
D'oh! Should have looked closer. ;)
--
___
Python tracker
<http://bugs.python.org/issue19888>
___
___
Python-bugs-list m
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:
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
Changes by Barry A. Warsaw :
--
nosy: +barry
___
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/issue19837>
___
___
Python-bugs-list mailing list
Unsubscribe:
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.
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 = &
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:
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 :
--
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
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue2506>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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:
assertTrue(dtrt)
--
___
Python tracker
<http://bugs.python.org/issue19590>
___
___
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
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19563>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19560>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 '
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
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:
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
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
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:
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
Barry A. Warsaw added the comment:
Indeed, this happens for me too in default head.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19555>
___
___
1201 - 1300 of 2582 matches
Mail list logo
