Barry A. Warsaw added the comment:
On Sep 15, 2013, at 06:05 PM, R. David Murray wrote:
>For the security fix, the check should only be done if the file is the the
>default .netrc. (Which would also make your error message
>correct...otherwise it is not :) Also, it would make more
Changes by Barry A. Warsaw :
--
nosy: +benjamin.peterson, georg.brandl, larry
priority: high -> release blocker
___
Python tracker
<http://bugs.python.org/issu
Barry A. Warsaw added the comment:
On Sep 15, 2013, at 05:34 PM, Serhiy Storchaka wrote:
>Oh, right. The correct code should be as I proposed in msg173413 or... as
>Andrew has committed. Good.
Excellent. So we're good for this in 2
Barry A. Warsaw added the comment:
On Sep 15, 2013, at 06:51 PM, R. David Murray wrote:
>I could write a 2.6 test for the permissions part, but not for the incorrect
>owner part. Do you want one without the other?
Yeah, I guess you can't mock os or stat in 2.6. ;)
Let's tes
Barry A. Warsaw added the comment:
After further contemplation and without objection from __ap__ and Crys on IRC,
I am de-targeting this for 2.6. I won't apply it for 2.6.9.
--
versions: -Python 2.6
___
Python tracker
<http://bugs.py
Barry A. Warsaw added the comment:
FWIW, the Ubuntu manpage netrc(5) says:
password string
Supply a password. If this token is present, the auto-login
process will supply the specified string if the remote server
requires a password as part of
Barry A. Warsaw added the comment:
==
FAIL: test_retrlines_too_long (__main__.TestFTPClass)
--
Traceback (most recent call last):
File "Lib
Barry A. Warsaw added the comment:
@RDM: In netrc.rst, s/posix/POSIX/
It also looks like you're keeping the ownership test. Did I misunderstand
msg197815? I thought you were only going to keep the permission test?
--
___
Python tracker
Barry A. Warsaw added the comment:
@RDM: Please commit to 2.6 and null merge to 2.7. Thanks!
--
___
Python tracker
<http://bugs.python.org/issue14984>
___
___
Barry A. Warsaw added the comment:
On Sep 16, 2013, at 03:12 PM, R. David Murray wrote:
>Well, I was planning to merge it, since 2.7 needs the fix as well.
Oh yeah, that's fine of course. And thanks!
--
___
Python tracker
<http://bugs
Barry A. Warsaw added the comment:
Yep, confirmed that ftplib.patch causes test_ftplib to fail, at least on Ubuntu
10.04 chroot.
--
___
Python tracker
<http://bugs.python.org/issue16
Barry A. Warsaw added the comment:
Succeeds on OS X 10.8 (although there are other failures)
--
___
Python tracker
<http://bugs.python.org/issue16038>
___
___
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19043>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Okay, this one is quite odd. It's definitely a timing issue.
If I put a `import time; time.sleep(1)` at the beginning of
test_retrlines_too_line() -- i.e. first line of the method -- then the test
reliably passes. If I put a `print(len(line))` just b
Barry A. Warsaw added the comment:
Looks good for 2.6. The NEWS file hunk doesn't apply, but I'll fix that when I
commit this to 2.6.
--
___
Python tracker
<http://bugs.python.o
Barry A. Warsaw added the comment:
Since the merge 2.6 -> 2.7 did not apply cleanly, and had other problems. I
null merged the 2.6 changes. I'll leave it to Benjamin to work out whatever
patches 2.7 needs.
--
versions: -Python 2.6
__
Barry A. Warsaw added the comment:
Please don't add 2.6 back to the Versions, unless there's actually something to
do for 2.6. AFAIK, this issue is resolved for 2.6.
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.o
Barry A. Warsaw added the comment:
On Sep 23, 2013, at 03:36 PM, Serhiy Storchaka wrote:
>What about time.sleep(0.1)?
I usually don't like introducing sleeps to fix race conditions, but if that's
the only option for landing this patch, maybe we'll have to hold o
Barry A. Warsaw added the comment:
On Sep 23, 2013, at 06:33 PM, Giampaolo Rodola' wrote:
>Barry can you paste the traceback caused by the race condition? What's not
>clear to me is when (what line) it occurs. One solution might be to send a
>"NOOP" command (se
Barry A. Warsaw added the comment:
On Sep 24, 2013, at 01:12 PM, Giampaolo Rodola' wrote:
>Giampaolo Rodola' added the comment:
>
>I believe the problem is the set of next_retr_data attribute here:
>
>def test_retrlines_too_long(self):
>self.server
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19084>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Sep 24, 2013, at 09:59 PM, Serhiy Storchaka wrote:
>Added file: http://bugs.python.org/file31862/ftplib_maxline.patch
This looks great and fixes the test failure problem. Thanks! Serhiy, please
feel free to apply this to the 2.6 branch, or let me know
Changes by Barry A. Warsaw :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue16038>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19092>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
As we discussed in other issues regarding the similar problem, I don't really
want to introduce a new exception in a point release of 2.6. Is there any
reason not to just raise HTTPException with the error message text? Code that
has to work a
Barry A. Warsaw added the comment:
I'm just going to go ahead and commit this patch to 2.6 with the change I
mentioned. Does anything else need to be done for 2.6?
--
___
Python tracker
<http://bugs.python.org/is
Barry A. Warsaw added the comment:
Thanks!
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue16037>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
Looks good, although only the POP3 exception is actually tested. The POP3_SSL
exception isn't tested. Any chance you could add a test for that (obviously,
only if `import ssl` succeeds)?
--
___
Python tr
Changes by Barry A. Warsaw :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue16041>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Sep 30, 2013, at 08:41 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>
>Arfrever Frehtes Taifersar Arahesis added the comment:
>
>> New changeset 7214e3324a45 by Barry Warsaw in branch '2.6':
>> - Issue #16041: CVE-2013-1
Barry A. Warsaw added the comment:
Looks great, thanks! I'll apply this to 2.6.9 but let others forward port it
to 2.7.
--
___
Python tracker
<http://bugs.python.org/is
Barry A. Warsaw added the comment:
On Sep 30, 2013, at 09:43 PM, Jyrki Pulliainen wrote:
>I also wonder if there should be data error risen instead? Current docstrings
>of the errors are not that well fit.
I guess a data error makes the least nonsense here, so I'll change it over to
Changes by Barry A. Warsaw :
--
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/issue16040>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue16040>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Oct 01, 2013, at 01:44 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>s/lenght/length/ in new comment in Lib/nntplib.py
Fixed, thanks.
--
___
Python tracker
<http://bugs.python.org/issu
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19205>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19209>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue9548>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue19216>
___
___
Python-bugs-list mailing list
Unsubscribe:
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:
1801 - 1900 of 2582 matches
Mail list logo