Matthew Cowles added the comment:
I disagree with the decision not to fix this bug. If a RuntimeWarning is
warranted when a temporary variable is used, it's warranted when the value is
used directly, without a temporary variable.
--
nosy: +mdcowles
Matthew Cowles <mdcow...@users.sourceforge.net> added the comment:
My thanks to David for the clarification. I don't find the logic he describes
(but does not necessarily subscribe to!) persuasive in this case. In my
opinion, "Let's be incorrect for the sake of simplicity,"
Matthew Cowles <mdcow...@users.sourceforge.net> added the comment:
If David is right and people have previously decided not to change wording like
this, can someone explain why? As it stands, the meaning is clear and incorrect.
--
nosy: +md
Matthew Cowles added the comment:
> a) for IDLE to run without stumbling over user files
> b) for user code to see the same sys.path when executing under IDLE as when
> executed directly with the same cpython binary in the same mode.
If you can achieve that, no one will be more impre
Matthew Cowles added the comment:
I'm very willing to believe that I'm missing something critical here, but
wouldn't it be satisfactory to just move "" from the beginning to the end of
sys.path in IDLE?
I can imagine that it might cause a few problems for users, but it
Matthew Cowles added the comment:
> Do you have access to IDLE on any system other than Windows?
I don't have a Windows machine at all.
For what it's worth, here's the behavior I'm talking about, albeit with an old
version of Python:
$ mkdir testidle
$ cd testidle
$ /usr/local/bin/pyt
Matthew Cowles added the comment:
This bug should be fixed urgently. Over at python-help we just got another
Python beginner who was using IDLE and then started to get the "IDLE's
subprocess didn't make connection" error. The problem was that the user had
named one of their programs
Matthew Cowles mdcow...@users.sourceforge.net added the comment:
Apologies! Further investigation indicates that the user had set a timeout in
the ftplib module. I'll close this. In an ideal world, errors due to timeouts
would look like they were related to timeouts. But that's a different
Matthew Cowles mdcow...@users.sourceforge.net added the comment:
[Replying to various posts]
[neologix]
That's one broken networking stack...
I'm not disagreeing, but you'd have to take that up with Apple.
How would you circumvent this problem anyway ?
The code has to go around again
Matthew Cowles mdcow...@users.sourceforge.net added the comment:
A minimal example which reproduces the behavior. :)
Unfortunately the problem wasn't mine originally. I'm just the guy on
python-help who happened to figure out the answer. But if someone can get me
access to an FTP server
Matthew Cowles mdcow...@users.sourceforge.net added the comment:
if you get this type of error, it's probably because you're using non-
blocking sockets
That's what I thought at first too. But the user's sockets were set to blocking.
spinning around the send call trying to resend the data
New submission from Matthew Cowles mdcow...@users.sourceforge.net:
[Originally from a post to the python-help list]
Over at:
http://docs.python.org/py3k/tutorial/datastructures.html#sets
it says:
fruit = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana']
fruit = set(basket
New submission from Matthew Cowles mdcow...@users.sourceforge.net:
[From a question first posted to python-help]
A socket's send function may return 0 if no bytes have been sent. Under at
least OS X 10.6.2, it may also raise errno 35 (resource temporarily
unavailable) if no network buffers
New submission from Matthew Cowles mdcow...@users.sourceforge.net:
[From a question sent to the python-help list.]
In the Python 3 tutorial at:
http://docs.python.org/3.0/tutorial/datastructures.html#dictionaries
it says:
The keys() method of a dictionary object returns a list of all
14 matches
Mail list logo
