Brad Miller bonel...@gmail.com added the comment:
On Thu, Mar 26, 2009 at 4:29 PM, Barry A. Warsaw rep...@bugs.python.orgwrote:
Barry A. Warsaw ba...@python.org added the comment:
I propose that you only document the getitem header access API. I.e.
the thing that info() gives you can
Changes by Brad Miller bonel...@gmail.com:
--
nosy: +bmiller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4773
___
___
Python-bugs-list mailing
Brad Miller bonel...@gmail.com added the comment:
I get the same problem when I try to change the key set. This is on on
intel build using Tk 8.5, and the latest 3.1 source checked out with
bzr.
I too changed the order of /Library/Frameworks and
/System/Library/Frameworks in setup.py
Brad Miller bonel...@gmail.com added the comment:
I hand applied the patch because I hoped it would fix the problem of the
cursor going all the way to the left of the in the Python shell when
you press home or ctrl-a. The patch as it is does not solve this problem
on the Mac. I've uploaded
Brad Miller bonel...@gmail.com added the comment:
Here's a simple patch that documents the different startup files. It is
missing a good use case for .Idle.py but I'd be happy to add that if
someone can give me one.
--
keywords: +patch
message_count: 1.0 - 2.0
nosy: +bmiller
Brad Miller bonel...@gmail.com added the comment:
Just to restart the discussion on the original issue since I see that
the latest 3.1 has solved the problem with dict_keys, dict_values, etc
al objects. Many thanks!
A suggestion was made by Alexander to create a custom displayhook
Brad Miller [EMAIL PROTECTED] added the comment:
For the example in unixclient.py using b'Hello World' works fine. But for
the example in the socketserver documentation the strings to convert come
from argv[1:]
On Sat, Nov 8, 2008 at 5:48 AM, STINNER Victor [EMAIL PROTECTED]wrote:
STINNER
Brad Miller [EMAIL PROTECTED] added the comment:
Here's a combined patch that fixes:
Doc/library/socketserver.rst examples tested and working
Demo/sockets/udpecho.py
Demo/sockets/unixclient.py
Added file: http://bugs.python.org/file11967/socketpatches.patch
Brad Miller [EMAIL PROTECTED] added the comment:
I found a similar problem in the Demo/sockets/unixclient.py code.
from socket import *
FILE = 'unix-socket'
s = socket(AF_UNIX, SOCK_STREAM)
s.connect(FILE)
s.send('Hello, world')
data = s.recv(1024)
s.close()
print('Received', repr(data
Brad Miller [EMAIL PROTECTED] added the comment:
After looking at the socket documentation pointed to from another issue
it looks like the right solution is to convert to a byte array.
I've attached a patch with fixes for all the examples in
socketserver.rst there were several other problems
Brad Miller [EMAIL PROTECTED] added the comment:
On Tue, Jun 17, 2008 at 12:23 AM, Martin v. Löwis
[EMAIL PROTECTED] wrote:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
After reviewing this again, I'm skeptical that this is a good idea. It
doesn't achieve its original purpose
Brad Miller [EMAIL PROTECTED] added the comment:
Is there any chance this patch will make it into the latest alpha??
Brad
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2610
Brad Miller [EMAIL PROTECTED] added the comment:
On May 7, 2008, at 1:55 PM, Martin v. Löwis wrote:
Thanks for the very clear answer.
This being my first attempt at contributing to the Python core, I am
looking for some sort of clarity on the future of this patch. It
feels like some sort
Brad Miller [EMAIL PROTECTED] added the comment:
Based on the discussion on python-dev I've worked up a patch and tests
for repr of dict_items, dict_keys, and dict_values. I've also modified
the patch and test for str of the range object. (If there was a way to
get the str(range(10
Brad Miller [EMAIL PROTECTED] added the comment:
On Apr 17, 2008, at 4:26 PM, Amaury Forgeot d'Arc wrote:
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Some review of dv_range.patch:
- repr(d.keys()) depends on the internal ordering of items, their hash
values, the insertion
Brad Miller [EMAIL PROTECTED] added the comment:
Here is a new patch file. This one contains the modifications to
rangeobject.c as well as test_range.py
I think this is everything. If there is something else I need to do
please let me know. I looked to see if there was any documentation I
Brad Miller [EMAIL PROTECTED] added the comment:
The patch does not change the behavior of repr. It modifies the
behavior of str.
I agree that learning list/tuple sooner is better, but students who have
never written a line of code before can only absorb so much information,
this little
Brad Miller [EMAIL PROTECTED] added the comment:
Our use of range in the first few classes is exactly for iteration
purposes, but I do not like students to have to have too many mysteries.
So I always have liked to show that range(10) simply produces a sequence
of integers. In Python 3.0
Brad Miller [EMAIL PROTECTED] added the comment:
Clearly neither Alexander nor I are going to get the other to come
around to our point of view. Thats fine, I think we can disagree here,
and I can adapt and change my class either way.
My question is how does this get resolved. When I posted
Brad Miller [EMAIL PROTECTED] added the comment:
I would suggest considering a custom displayhook approach. You can
write a custom displayhook that will print range(..), {}.keys(),
{}.values() etc in a student-friendly way. I believe a module
installing such display hook can be included
New submission from Brad Miller [EMAIL PROTECTED]:
I use Python in my CS1 and CS2 curriculum and I have a question.
As I've been using the Python 3.0 alphas one of the things that I am
bothered by is that I cannot see the sequence produced by range
without introducing students to the list
Brad Miller [EMAIL PROTECTED] added the comment:
Thanks for all of the help. Using range_item certainly simplified my
job. Although I more than made up for it with all of the decref and
error checking calls.
One side effect of using range_item is that str(range(...)) is now
subject
Changes by Brad Miller [EMAIL PROTECTED]:
--
nosy: +bmiller
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1513695
_
___
Python-bugs-list mailing list
Brad Miller [EMAIL PROTECTED] added the comment:
I have xturtle 0.95a0 running under Python 3.0. Mostly the 2to3 program
just worked for everything except in three places:
1. in __forward methods I had to change:
fromClass.__dict__[method] = d[method]to
setattr(fromClass,method,d[method
24 matches
Mail list logo