Raymond Hettinger added the comment:
Thanks for the patch. It reads well and is informative.
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17462
___
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20898
___
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15025
___
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: - rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21786
___
___
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: serhiy.storchaka - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21708
___
Josh Rosenberg added the comment:
@Tim: Sorry, forgot the internals there (I read all that a while ago, but it's
not easy to keep all the details in mind). Apparently there are four reasons
this isn't actually a problem. :-)
I agree it's kind of silly that it's converted to a hex string
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: docs@python - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11974
___
grossdm added the comment:
I believe it was the same page.
Looking through my browser history, I see that I looked at the download page
for an older version - I did find the links on that page.
Perhaps it was just a hiccup in my browser.
Thanks for responding; I know the proper place to
Kay Hayen added the comment:
I can confirm that Python3.4 is not affected. Python 3.3 and 3.2 still are.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16967
___
Kay Hayen added the comment:
Are you still tracking this as a feature request. If so, please note that I
don't need it anymore. The meta path based import mechanism is fully sufficient
to me.
--
___
Python tracker rep...@bugs.python.org
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21635
___
Raymond Hettinger added the comment:
What behavior both looks wrong and gets improved by the change?
The incorrect behavior is that matching_blocks is incorrectly cached so that
calls to get_matching_blocks() returns an answer without the named tuple (in
contravention of the documented
Raymond Hettinger added the comment:
[Cherniavsky Beni]
it's makes copy-paste code between the shell and editor
windows confusing
This has been a continual source of frustration for students in my Python
courses as well. I'm looking forward to it being fixed.
--
priority: normal -
New submission from Sworddragon:
If I'm receiving data from a socket (several bytes) and making the first call
to socket.recv(1) all is fine but the second call won't get any further data.
But doing this again with socket.recv(2) instead will successfully get the 2
bytes. Here is a testcase:
101 - 114 of 114 matches
Mail list logo