Barry A. Warsaw added the comment:
On Apr 02, 2013, at 03:04 PM, Eric V. Smith wrote:
>I think it would be a bug fix and thus should be backported. It's not like
>we'd be breaking any working code, unless it was expecting the exception.
That would
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17621>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Okay, so this is not a Python problem, but an Ubuntu problem. It's also not a
problem with Ubuntu's version of Python. I can reproduce it on Ubuntu 13.04
with hg trunk, but not Debian Wheezy with hg trunk.
Closing as invalid and will investigate
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17630>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17636>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17685>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I just ran into this too.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue15657>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
We should fix the code for 3.2 through 3.4, but change the docs for 3.2 and 3.3
to remove the parenthetical note. For 3.4 we can leave the parenthetical note
but say this is new in 3.4 (or maybe, that it doesn't actually work in some
versions <
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
>From a documentation standpoint, path='' is not the same as "When no path is
>specified", so indeed it should return None when path=''. Serhiy's patch
>looks good to me.
--
_
Changes by Barry A. Warsaw :
--
assignee: -> barry
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Barry A. Warsaw :
--
assignee: barry -> serhiy.storchaka
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Python-bugs-list mai
Barry A. Warsaw added the comment:
Serhiy, I'd say go ahead and commit it. +1 from me.
--
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17750>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry, doko
___
Python tracker
<http://bugs.python.org/issue17712>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Possibly this issue: Possibly this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=312011
I'm seeing tons of this on Ubuntu 13.04.
--
___
Python tracker
<http://bugs.python.org/is
New submission from Barry A. Warsaw:
socket.gethostbyname('sadflkjsasf.i.nvali.d') gives a TimeoutError instead of
an IOError on Ubuntu 13.04, causing the test to fail.
% ./python -m unittest test.test_urllibnet
.E../home/barry/projects/python/cpython/Lib/test/test_urlli
Barry A. Warsaw added the comment:
I couldn't wait. :)
--
assignee: serhiy.storchaka -> barry
___
Python tracker
<http://bugs.python.org/issue17012>
___
_
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Python-bugs-list
Barry A. Warsaw added the comment:
On Apr 16, 2013, at 03:26 PM, R. David Murray wrote:
>I can't see how this could be classed as a bug in Python. An invalid domain
>should quickly return a DNS error on a correctly configured operating system,
>which is what the test is tes
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17788>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
As described here:
http://www.wefearchange.org/2013/04/python-3-language-gotcha-and-short.html
the following code will produce an UnboundLocalError when the exception is
triggered:
def bad():
e = None
try:
do_something()
except
Barry A. Warsaw added the comment:
On Apr 19, 2013, at 12:01 AM, Ezio Melotti wrote:
>
>Maybe we could raise a warning when the deleted name already exists in the
>local namespace?
Ideally, I think a SyntaxError if you could detect a previously bound name in
the namespace being u
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue4617>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Apr 19, 2013, at 12:37 AM, R. David Murray wrote:
>And what if it weren't a print statement? An error is better than a
>"randomly" changed value, I think. I'm really not sure there is anything we
>can do here, beyond Ezio
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17800>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Ezio, the problem with your patch is that it also gives a warning on this code,
which is totally safe:
def good():
exc = None
try:
bar(int(sys.argv[1]))
except KeyError as e:
print('ke')
exc = e
except Value
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17843>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17827>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17828>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17839>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17853>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17872>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue15535>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17921>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17961>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On May 12, 2013, at 10:57 AM, Nick Coghlan wrote:
>I encountered an interesting suggestion [1] regarding the enum.Enum
>convenience API: use the member names as their values, rather than the
>current integers starting from one.
>
>Since
Barry A. Warsaw added the comment:
On May 12, 2013, at 8:35 PM, Ethan Furman wrote:
> Ethan Furman added the comment:
>
> The class syntax (and default Enum) no longer have preferential treatment for
> integers (even __int__ is gone); so it is completely up to us as what should
Barry A. Warsaw added the comment:
On May 13, 2013, at 10:10 AM, Antoine Pitrou wrote:
>I agree with Nick here, there's no reason to auto-number constants in
>Python. This is not C :-)
Why should they be strings? Why not object()?
Why is `x.value == str(x)` a useful invari
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17966>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
It's not *particularly* silly[1], but I think that with Government backing, he
could make it very silly.
[1] I mean, the right hand side isn't silly at all and the left hand side
merely does a forward aerial half turn every alternative
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17959>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On May 12, 2013, at 06:51 AM, Nick Coghlan wrote:
>>>> class Shape(Enum):
>... square = 2
>... diamond = 1
>... circle = 3
>... alias_for_square = square
I see Guido pronounced against it, but I'm just registering that I
Barry A. Warsaw added the comment:
On May 13, 2013, at 02:06 PM, Antoine Pitrou wrote:
>Antoine Pitrou added the comment:
>
>> >I agree with Nick here, there's no reason to auto-number constants
>> >in
>> >Python. This is not C :-)
>>
>
Barry A. Warsaw added the comment:
On May 13, 2013, at 02:24 PM, Nick Coghlan wrote:
>Yep. Since we no longer have a compelling reason for it to be anything
>else, it may as well be the human readable string.
Again, why does it matter? That's the whole point of having a human r
Barry A. Warsaw added the comment:
LGTM too. Needs test and docs.
--
___
Python tracker
<http://bugs.python.org/issue17941>
___
___
Python-bugs-list mailin
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17954>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17974>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
The docs[1] say:
.. function:: urlopen(url, data=None[, timeout], *, cafile=None, capath=None,
cadefault=True)
The code[2] says:
def urlopen(url, data=None, timeout=socket._GLOBAL_DEFAULT_TIMEOUT,
*, cafile=None, capath=None, cadefault=False
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue17977>
___
___
Python-bugs-list
New submission from Romulo A. Ceccon:
I have patched (see attachment) Python 2.7.4 (as available for download at
python.org/download) to disable initialization of Unicode (an embeded system
requirement) and now it segfaults with the following program:
#include
int main(int argc
Romulo A. Ceccon added the comment:
I've made some further investigation on this issue. Here's the output and the
stack trace using --with-pydebug (and the attached patch applied):
run no. 0
[8766 refs]
free_list[0]->ob_refcnt before XDECREF: 2
run no. 1
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue13146>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue8604>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Of course, I have my own atomic-rename thing, but I'm not going to post the
code here. It's fairly limited to my own use case and I have no interest in
making it cross platform.
That being said, I personally found that a context manager with a
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17222>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Antoine says:
> Ah, right. Well, there would be an argument not to use os.replace() in
> py_compile, since it's an offline processing step which generally
> shouldn't race with another (online) processing step.
But I think that's not
Changes by Barry A. Warsaw :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue13146>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Proposed patch for 2.7
--
Added file: http://bugs.python.org/file30324/13146-2.7.patch
___
Python tracker
<http://bugs.python.org/issue13
Barry A. Warsaw added the comment:
I'm re-opening this because I'd like to get RM pronouncement on applying a
patch to 2.7, 3.2, and 3.3 to make py_compile.py atomically rename its pyc/pyo
file.
Attached is a patch for 2.7 based on importlib's approach in 3.4. It should be
Barry A. Warsaw added the comment:
Oh btw, if Georg and Benjamin deny this for the stable releases, I'll very
likely patch the Ubuntu versions anyway.
--
___
Python tracker
<http://bugs.python.org/is
Barry A. Warsaw added the comment:
On May 20, 2013, at 09:52 PM, Antoine Pitrou wrote:
>Some people already complained about this change. I'm not sure it's fit for a
>bugfix release. http://bugs.python.org/issue17222
Yeah, but that's a crazy use case. :)
>Besides
Barry A. Warsaw added the comment:
On May 20, 2013, at 09:57 PM, Charles-François Natali wrote:
>IIRC, os.rename() will fail on Windows if the target file already exists.
>That's why os.replace() was added.
Ah, that's probably a more serious blocker for adding it to upstream Py
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue7434>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue11959>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22597>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22627>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
<http://bugs.python.org/i
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22680>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
t
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'
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22636>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22869>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22914>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22966>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
<http://bugs.pytho
Changes by Barry A. Warsaw :
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue22966>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue22966>
___
___
Python-bugs-list
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 -> clo
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue22995>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
Andrej A Antonov added the comment:
@demian.brecht , your example code-fragment is too big. :-)
too many lines -- just only for adding "timeout". it is uncomfortably.
most people will not using that: most likely they just will forget about
"timeout" (but in *MOST*
Andrej A Antonov added the comment:
@demian.brecht , socket.setdefaulttimeout([timeout]) -- it is bad practice,
because setting this global varible we may spoil other cases. example "TCP
keepalive" [ s.setsockopt(socket.SOL_SOCKET, socket.SO_KEEPALIVE, true) ]
and global variab
Andrej A Antonov added the comment:
ok, let's go to other side of this problem:
question: why default transport (xmlrpc.client.Transport()) is not setting
value of timeout?``
answer: because *unknown* which value need to using by default.
in various cases programmer need various ti
Andrej A Antonov added the comment:
>> if you NOT point timeout in "RPC-client" -- you program will freeze or will
>> maked resource leak (with small probability).
> Assuming a lack of concurrency, your program will indeed freeze until the
> system timeout has been
Andrej A Antonov added the comment:
I just will write next code-fragment:
import socket
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM, socket.IPPROTO_TCP)
s.connect(('python.org', 80))
print(
'is my operation system using (by default) "tcp
Andrej A Antonov added the comment:
>> in GNU/Linux "system timeout has been reached" -- means that system timeout
>> will *never* reached.
> That's quite likely because the system limits may be very large.
I tested system-timeout GNU/Linux (on various computer
Andrej A Antonov added the comment:
@demian.brecht , for high probably to catch *infinite_freeze* (at GNU/Linux) --
if we may will run requests of "xmlrpc.client.ServerProxy" -- parallely:
(when running next code -- need to make some network-disconnections on
"network-
nough to need to appear in the tag.
Antoine has a point there. Together with the problems I mentioned
with non-mainstream platforms, it would be better to use a compile
time definition of the platform tag as you've chosen for Windows.
PEP 425 unfortunately ignores the mentioned problems of get_pl
Andrej A Antonov added the comment:
good patch (issue14134.patch) ! thanks!
--
___
Python tracker
<http://bugs.python.org/issue14134>
___
___
Python-bugs-list m
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 sprea
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue23149>
___
___
Python-bugs-list mailing list
Unsubscribe:
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, P
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue23228>
___
___
Python-bugs-list mailing list
Unsubscribe:
Adding a note to the documentation is fine.
The .reset() method doesn't have anything to do with the underlying
stream. It's only meant to work at the codec level and needed for
codecs that keep internal state.
--
Marc-Andre Lemburg
te(self, object):
+self.stream.write(self._encoder.encode(object))
+
+def reset(self):
+self.stream.write(self._encoder.encode(final=True))
+
Note that the doc-string mentions a non-existing attribute and there
are doc-string missing for the other methods.
The purpose appears to be a Strea
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue23342>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 /bin are
relative, while they are absolute with pyvenv. This means that virtual
environments created with virtualenv can
2201 - 2300 of 2582 matches
Mail list logo
