Some library files, such as pdb.py, begin with
#!/usr/bin/env python
In various discussions regarding some issues I submitted I was told
that the decision had been made to call Python 3.x release
executables python3. (One of the conflicts I ran into when I made
'python' a link to python
. If
it needs a new maintainer I hereby volunteer. Discussions about my
qualifications should probably be conducted through email to me
personally, rather than through this mailing list, using the address
I use when submitting issues to the tracker: m...@acm.org.
--
Mitchell L Mo
Would whoever is responsible for IDLE please take a look at the
patches I submitted for Python 2 & 3 [tracker IDs 5233 and 5234
respectively]. These change the behavior of IDLE so that IDLESTARTUP
or PYTHONSTARTUP files are executed with each restart. This allows
loading frequently used package
The python man page, dated 2005 even in 3.1, has this curious entry:
~/.pythonrc.py
User-specific initialization file loaded by the user module; not
used by default or by most applications.
1. I couldn't figure out what the user module is.
2. I couldn't figure
In Digest Vol. 67, Issue 52 (13 Feb 2009) I pointed out that Python
2's prohibition against performing readlines on a file being iterated
over appears to have been lifted in Python 3. I asked if this was
intentional and whether it should be add to the "What's New"
documentation. I also express
I discovered today that Python 2's prohibition against performing
readlines on a file being iterated over appears to have been lifted
in Python 3. Is this intentional? If it is, should it be added to the
What's New in the documentation? I haven't been able to find anything
mentioning the change
I have submitted patches to idlelib/PyShell.py for Python 2.7 (Issue
5233) and 3.1 (5234), made against local repository copies as updated
an hour ago. The purpose of the patch is to have IDLE load
IDLESTARTUP or PYTHONSTARTUP on restart.
Along the way I also made -s the default so IDLESTARTUP
I was trying to disentangle some IDLE behavior today and discovered
that If the user has a .Idle.py file IDLE will run it when it starts
up. This is independent of running IDLESTARTUP or PYTHONSTARTUP when
the -s switch is given. It is run by Tk.readprofile as called from
Tk.__init__. The "Idle
I have a patch for IDLE, but I've never submitted a patch before and
not quite sure of the procedure, despite reading the guidelines at
http://www.python.org/dev/patches/. But I'll be brave and persevere.
The question I have at the moment is should I only submit the patch
vs. 3.1 or also for 3.
I have a small change (shown below) to PyShell.py in idlelib that
causes the subprocess interpreter to read IDLESTARTUP or
PYTHONSTARTUP each time it restarts. To me this would make IDLE much
more useful for myself and students I teach. It isn't quite clear
what behavior to install with the en
cannot convince myself that the docmentation ever covers sequence
slicing. I'm not sufficiently confident of this to post as a bug, so
I decided to post here first.
--
--- Mitchell L Model
___
Python-Dev mailing list
Python-Dev@python.org
ht
11 matches
Mail list logo
