Changes by Cherniavsky Beni :
--
nosy: +cben
___
Python tracker
<http://bugs.python.org/issue7475>
___
___
Python-bugs-list mailing list
Unsubscribe:
Cherniavsky Beni added the comment:
Easily detecting interactive mode is of general interest for customization.
1. What if C also set sys.flags.interactive in "python" mode,
or exposed sys.flags.implicit_interactive (but with better name)?
2. It's more useful to have a h
Cherniavsky Beni added the comment:
On Tue, Sep 6, 2011 at 17:54, Antoine Pitrou wrote:
It covers the user's desire customization very well (esp. if it worked with
-i).
sys.__interactivehook__ has the benefit of being cleanly settable from
python code.
But it might well be a YAGNI
Cherniavsky Beni added the comment:
[sorry, html mail was bad idea]
On Tue, Sep 6, 2011 at 17:54, Antoine Pitrou wrote:
Éric Araujo added the comment:
> > It's more useful to have a hook called when entering interactive mode,
> > rather than a flag
> > that's
Cherniavsky Beni added the comment:
When you run a program using F5 in IDLE,
it completely restarts the underlying interpreter!
If you meant a different way of running, please elaborate.
(Exception: it uses the same interpreter if you're running "idle -n"; this
commonly happen
Cherniavsky Beni added the comment:
This is almost a duplicate of http://bugs.python.org/issue1196946
(though the solution there took a different direction).
--
___
Python tracker
<http://bugs.python.org/issue7
New submission from Cherniavsky Beni :
[Spinoff of http://bugs.python.org/issue3559]
If you manage to type several simple statements into the prompt (by
copy-pasting them, using Ctrl+J, or creative deletion), IDLE runs the first one
and silently ignores the rest:
>>> x = 1
x =
Cherniavsky Beni added the comment:
There are 2 issues here:
(1) There should be a quick & obvious way to paste and run several statements.
(2) If a user types several statements and presses Enter, all should run. The
current behavior is badly broken, and pasting is just one of the way
Cherniavsky Beni added the comment:
> As it happens, I do use Windows and almost exclusively start IDLE via
> right-clicks on .py files. I've never seen the behavior you describe
> documented anywhere.
You're right, it wasn't.
[IDLE does show a " No Subp
New submission from Cherniavsky Beni :
>>> help('nonlocal')
no Python documentation found for 'nonlocal'
As a language keyword, it clearly should have documentation.
--
assignee: d...@python
components: Documentation
messages: 115266
nosy: cben, d...@pyt
New submission from Cherniavsky Beni :
help('NAMESPACES') or any other long help is shows in a pager. That's great.
It's a bit surprising however that the text shown in the pager doesn't include
the "Related help topics: ..." line, which is shown when you l
Cherniavsky Beni added the comment:
Reopening because help('nonlocal') still doesn't work; attached patch fixes
that. It also cross-links all of global/nonlocal/NAMESPACES.
--
keywords: +patch
resolution: fixed ->
status: closed -> open
Added file: http://bugs
Cherniavsky Beni added the comment:
The FAQ for this was much improved in 2009 (issue 7290):
http://docs.python.org/py3k/faq/programming.html#why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value
To support the claim that this keeps biting people, at least the following bug
Cherniavsky Beni added the comment:
Hi Steven.
Please confirm if we can mark the bug closed; if you need farther advice,
posting your full code (not just the error case) on comp.lang.python or
StackOverflow would be more effective.
The documentation is indeed correct but hard to find (you
Cherniavsky Beni <[EMAIL PROTECTED]> added the comment:
The patch logic is very simple: inside the command area Up/Down move
through history.
But what about multi-line editing? Wouldn't this interfere when you
just want to move between lines in a multi-line command (e.g. a long
``
Cherniavsky Beni added the comment:
Editing a block of code from inside the config dialog (and storing it in the
config file?) seems a bad idea because you lose all the power of the normal
IDLE editor.
Instead, you should edit the startup code in the editor, save it to a file and
point the
Cherniavsky Beni added the comment:
(Another point I forgot to mention is that you must also run idle with the -s
command-line option to look at these envvars. This was silly and is also fixed
by the #5233 patch.)
--
___
Python tracker
<h
Cherniavsky Beni added the comment:
History access by Up/Down is important because it makes IDLE history much more
discoverable. Most users instinctively expect Up/Down to work; moving back
through the text of the session is nice but they probably won't guess that you
can press Ent
Cherniavsky Beni added the comment:
Oops! Mitchell's patch didn't actually run the startup code after restart.
Fixed patch attached (updated against 2.7 trunk). Also added some doc updates.
Too lazy to produce a 3.2 version now.
[Apology to Mitchell: I removed most of you
Cherniavsky Beni added the comment:
Mark: customizing tabs to be anything but 8 spaces is inadvisable with Python,
because Python always parses them as 8.
Sooner or later one would mix tabs and spaces and the result would be really
painful to debug.
--
nosy: +cben
Cherniavsky Beni added the comment:
I was only thinking of 3.4, which will have venv and a pip bootstrapper.
Is changing the doc build / doctest in scope for minor releases of 3.3 (or even
earlier)?
The commands I listed (using setup_distribute.py) also work with 3.3.
(But they're uns
New submission from Cherniavsky Beni:
[followup for issue 12642 which only fixed it for open()]
http://docs.python.org/library/functions.html#file
says the arg names are:
file(filename[, mode[, bufsize]])
but in practice they are:
file(name[, mode[, buffering]])
--
assignee: docs
Cherniavsky Beni added the comment:
Nice. 2 questions:
1. Why not change getch() to always use get_wch()?
2. I think you also want fix getkey() / introduce get_wkey().
--
nosy: +cben
___
Python tracker
<http://bugs.python.org/issue6
New submission from Cherniavsky Beni :
IDLE defaults to indenting with 4 spaces in editor windows, but hard TABs in
the Python Shell window. This is inconsistent with PEP 8; what's worse, it's
makes copy-paste code between the shell and editor windows confusing and
dangerous!
Cherniavsky Beni added the comment:
Perhaps it should not be an error at all? The default should probably
stay strict to the spec, but IMHO the module should provide an optional
lenient parsing mode that also accepts single quotes.
Why support single quotes and not any other imaginable
New submission from Cherniavsky Beni :
An interactive prompt should offer working completion out-of-the-box,
without requiring every Python user on earth to create a $PYTHONSTARTUP
with '''import readline; readline.parse_and_bind("tab: complete")'''.
Changes by Cherniavsky Beni :
--
components: +Interpreter Core
type: -> feature request
versions: +Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/iss
New submission from Cherniavsky Beni:
recent gdb versions by default won't auto-load python-gdb.py.
issue15043 fixed this in test_gdb, but manual action is still needed to when a
developer actually wants to run gdb.
Attached devguide patch.
After writing this I noticed it's already
Cherniavsky Beni added the comment:
The links to gdb docs presently are broken because sourceware.org is down for
maintenance, but it should be back up in a couple days.
--
___
Python tracker
<http://bugs.python.org/issue17
Cherniavsky Beni added the comment:
After a lot of experimentation, this worked for me to build AND doctest using
the local python:
cd Doc/
../python -m venv toolsenv
curl http://python-distribute.org/distribute_setup.py | toolsenv/bin/python
toolsenv/bin/easy_install pip
toolsenv/bin/pip
Cherniavsky Beni added the comment:
+1, is there anything missing to apply Paul's patch?
Can I additional suggest a change to the error message, e.g.:
$ prog --foo -bar
prog: error: argument --foo: expected one argument
(tip: use --foo=-bar to force interpretation as argument of
Changes by Cherniavsky Beni :
--
nosy: +cben
___
Python tracker
<http://bugs.python.org/issue15873>
___
___
Python-bugs-list mailing list
Unsubscribe:
32 matches
Mail list logo