Change by irdb :
--
nosy: +irdb
___
Python tracker
<https://bugs.python.org/issue26568>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue19495>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue30024>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue14551>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from irdb:
__getitem__ was added to match objects as a resolution of issue24454.
Wouldn't it be nice to also have `__contains__` and `get` methods for match
objects? Is it even feasible to implement them in neat way?
They should work similar to dictionaries, i.e:
```
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue14965>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue10399>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue17301>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1647489>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue2506>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1602>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue24454>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue9618>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue18766>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from irdb:
I usually insert the following line in the middle of code to start the debugger
from there:
import pdb; pdb.set_trace()
More often than not, I need to run some commands immediately after entering the
debug mode, e.g. watch (display) some variables, create some
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue13504>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue694339>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue2704>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue5150>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue22742>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue21084>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue13153>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue23220>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue25522>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue7676>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1794>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue2636>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue10972>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue10614>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue15348>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
type: -> crash
___
Python tracker
<http://bugs.python.org/issue24455>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.p
New submission from irdb:
# Open a module using IDLE
# Run the module (Press F5)
# Activate the debugger ([DEBUG ON])
# Set a breakpoint in the module
# Run the module again
# Run the module for the third time
# Hit the Quit button in Debug Control window (twice, as the first click
appears to
New submission from irdb:
It has been suggested by BDFL to use triple-quoted strings as multiline
comments.[1]
Allegedly, some editors already makes a distinction between these kind of
comments and docstring and highlight them differently.
It would be nice if IDLE could also highlight these
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue219960>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1442493>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue6143>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue19042>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from irdb:
I suggest adding a "Copy variable to clipboard" menu option to the edit menu of
IDLE.
Sometimes I need to copy a variable to clipboard, but because the variable is
so long, printing it in the IDLE window makes IDLE sluggish and then selecting
and copying t
irdb added the comment:
On cmd and powershell:
>python -c "import sys; print(sys.getdefaultencoding());"
utf-8
>python -c "import sys; print(sys.stdout.encoding);"
cp720
In IDLE:
>>> import sys; print(sys.getdefaultencoding());
ut
irdb added the comment:
Although in Python 3 IDLE can indeed print UTF-8 characters. But still
sys.stdout.encoding == locale.getpreferredencoding() != 'utf-8'.
>>> sys.stdout.encoding
'cp1256'
Shouldn't it be 'utf-8'?
--
_
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue22408>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue4823>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue3286>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue16893>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue17535>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue433030>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue3559>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1178>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue16296>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
irdb added the comment:
Yes, I am right-clicking the file through Windows Explorer as in some
situations it seems much faster. (Opening through IDLE's file menu in a
particular process works fine)
If this is supposed to be so please close the issue. Although I don't
understand why
Changes by irdb :
--
title: IDLE should should not open multiple instances of one file -> IDLE
should not open multiple instances of one file
___
Python tracker
<http://bugs.python.org/issu
New submission from irdb:
Currently users can open multiple instances of one file in IDLE. Sometimes this
leads to confusion and may cause loss of data. I'm not aware of any benefits of
this behavior and I think it's better to be prevented by IDLE.
Here are the steps to recreate the
irdb added the comment:
Thank you Serhiy for working on this. This patch solves the problem when all
your input characters are encodable using system preferred encoding. But
issue19625 persists. I still can't print something like 'Русский текст' in
interactive mode.
Another
irdb added the comment:
Well, if there is no other way around this, I think it's better to apply
Martin's patch. At least then we will be able to enter any valid utf-8
character in IDLE (although print statement won't print correctly unless the
string is decoded first).
(As
New submission from irdb:
>>> s = 'ی'
Unsupported characters in input
I'm using windows 8 and Python 2.7.6.
The same line works perfectly if I save it in a module with encoding set to
UTF-8; but it's really annoying that I can't test my code directly in
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue1519638>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from irdb:
Many other IDE's have this feature that allows automatic insertion of closing
parentheses as user is typing something. I think it saves time and increases
programming speed. Is it possible to have this on IDLE, too?
--
components: IDLE
messages: 196456
irdb added the comment:
I really think this information might help, if not, I promise not to post
anything else. :)
This is a sample program I run:
'''
# -*- coding: utf-8 -*-
import sys
import locale
de = sys.getdefaultencoding()
pd = locale.getpreferredencoding()
print de,
irdb added the comment:
Oops! My problem is that I get "Unsupported characters in input" when trying to
type any Unicode string in IDLE's interactive mode.
e.g. a simple command like: s = u'Русский текст' gives: Unsupported characters
in input
Probably unrelated to t
irdb added the comment:
Sorry, it's probably has the same problem as what Martin suggested. Although I
think it's better than having program interrupted.
--
___
Python tracker
<http://bugs.python.o
irdb added the comment:
How about passing on UnicodeError? Will it cause other problems?
--
Added file: http://bugs.python.org/file31400/PyShell.py.patch
___
Python tracker
<http://bugs.python.org/issue15
Changes by irdb :
--
nosy: +irdb
___
Python tracker
<http://bugs.python.org/issue17348>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
62 matches
Mail list logo
