[issue8315] ./python -m unittest test.test_importlib doesn't work

[Berker Peksag]

Berker Peksag added the comment:

test_importlib has been fixed in issue 22002.

$ ./python -m unittest test.test_importlib

--
Ran 963 tests in 1.533s

OK (skipped=15, expected failures=1)

--
nosy: +berker.peksag
resolution:  -> out of date
stage:  -> resolved
status: open -> closed
type:  -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22200] Remove distutils checks for Python version

[Berker Peksag]

Changes by Berker Peksag :


--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22299] resolve() on Windows makes some pathological paths unusable

[Antoine Pitrou]

Antoine Pitrou added the comment:

I'm a bit worried about the consequences still. If you take "C:" and join it 
with e.g. "foo", you get a drive-relative path. If you take "//?/C:/" and join 
it with e.g. "foo", you get an absolute path (or, if you remove the drive's 
trailing slash, you get something that's invalid AFAIK).

So the question is: how implicit/explicit will the conversion be, and at which 
stages will it happen?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22353] re.findall() documentation lacks information about finding THE LAST iteration of reoeated capturing group (greedy)

[Mateusz Dobrowolny]

New submission from Mateusz Dobrowolny:

Python 3.4.1, Windows.
help(re.findall) shows me:
findall(pattern, string, flags=0)
Return a list of all non-overlapping matches in the string.

If one or more capturing groups are present in the pattern, return
a list of groups; this will be a list of tuples if the pattern
has more than one group.

Empty matches are included in the result.

It seems like there is missing information regarding greedy groups, i.e. 
(regular_expression)*
Please take a look at my example:

-EXAMPLE-
import re

text = 'To configure your editing environment, use the Editor settings page and 
its child pages. There is also a ' \
   'Quick Switch Scheme command that lets you change color schemes, themes, 
keymaps, etc. with a couple of ' \
   'keystrokes.'
print('Text to be searched: \n' + text)
print('\nSarching method: re.findall()')

regexp_result = re.findall(r'\w+(\s+\w+)', text)
print('\nRegexp rule: r\'\w+(\s+\w+)\' \nFound: ' + str(regexp_result))
print('This works as expected: findall() returns a list of groups (\s+\w+), and 
the groups are from non-overlapping matches.')

regexp_result = re.findall(r'\w+(\s+\w+)*', text)
print('\nHow about making the group greedy? Here we go: \nRegexp rule: 
r\'\w+(\s+\w+)*\' \nFound: ' + str(regexp_result))
print('This is a little bit unexpected for me: findall() returns THE LAST 
MATCHING group only, parsing from-left-to-righ.')

regexp_result_list = re.findall(r'(\w+(\s+\w+)*)', text)
first_group = list(i for i, j in regexp_result_list)
print('\nThe solution is to put an extra group aroung the whole RE: \nRegexp 
rule: r\'(\w+(\s+\w+)*)\' \nFound: ' + str(first_group))
print('So finally I can get all strings I am looking for, just like expected 
from the FINDALL method, by accessing first elements in tuples.')
--END OF EXAMPLE-


I found the solution when practicing on this page:
http://regex101.com/#python
Entering:
REGULAR EXPRESSION: \w+(\s+\w+)*
TEST STRING: To configure your editing environment, use the Editor settings 
page and its child pages. There is also a Quick Switch Scheme command that lets 
you change color schemes, themes, keymaps, etc. with a couple of keystrokes.

it showed me on the right side with nice color-coding:
1st Capturing group (\s+\w+)*
Quantifier: Between zero and unlimited times, as many times as possible, giving 
back as needed [greedy]
Note: A repeated capturing group will only capture the last iteration. Put a 
capturing group around the repeated group to capture all iterations or use a 
non-capturing group instead if you're not interested in the data




I think some information regarding repeated groups should be included as well 
in Python documentation.

BTW: I have one extra question.
Searching for 'findall' in this tracker I found this issue:
http://bugs.python.org/issue3384

It looks like information about ordering information is no longer in 3.4.1 
documentation. Shouldn't this be there?

Kind Regards

--
assignee: docs@python
components: Documentation
messages: 226534
nosy: Mateusz.Dobrowolny, docs@python
priority: normal
severity: normal
status: open
title: re.findall() documentation lacks information about finding THE LAST 
iteration of reoeated capturing group (greedy)
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22353] re.findall() documentation lacks information about finding THE LAST iteration of repeated capturing group (greedy)

[Mateusz Dobrowolny]

Changes by Mateusz Dobrowolny :


--
title: re.findall() documentation lacks information about finding THE LAST 
iteration of reoeated capturing group (greedy) -> re.findall() documentation 
lacks information about finding THE LAST iteration of repeated capturing group 
(greedy)

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22354] Highlite tabs in the IDLE

[Christian Kleineidam]

New submission from Christian Kleineidam:

Python accepts both tabs and spaces. Code that mixes tab and spaces can lead to 
problematic issues. Especially beginners who are new to python can be confused 
if they copy some code and it doesn't work as they expected because of issues 
of invisible whitespace.

Beginners are also more likely to use the editor that comes with the IDLE 
instead of using a more specialised editor. 

If the IDLE would highlite the fact that tabs are used instead of spaces, it 
would be easier to spot the issue. I therefore suggest that the IDLE highlites 
tabs both in the shell mode and the editor mode.

Possible ways to highlite is to have a light grey: 
<--> 
» (at the beginning of the tab)
PyCharm style error underlining

--
components: IDLE
messages: 226535
nosy: Christian.Kleineidam
priority: normal
severity: normal
status: open
title: Highlite tabs in the IDLE
type: enhancement
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

[Saimadhav Heblikar]

Saimadhav Heblikar added the comment:

Hi Terry,

Would it be better if the current inlined code is moved into get_entity?
It will also make it easier to test. The try:... except ImportError block be 
present within the get_entity method itself?
Otherwise, I will make a patch on what you said earlier in 
http://bugs.python.org/issue18766#msg224663.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22355] inconsistent results with inspect.getsource() / inspect.getsourcelines()

[Iestyn Elfick]

New submission from Iestyn Elfick:

The functions inspect.getsource() and inspect.getsourcelines() return 
inconsistent results for frames corresponding to class definitions within a 
function.

Test code:

import sys
import inspect

def case1():
class C:
def __init__(self):
pass
c = C()

def case2():
a = 1
class C:
def __init__(self):
pass
c = C()

def case3():
def fn():
pass
class C:
def __init__(self):
pass
c = C()

def trace(frame,event,arg):
code = frame.f_code
print('name:',code.co_name)
print('source:\n',inspect.getsource(code),'\n')

for case in ('case1','case2','case3'):
print('#',case)
call = getattr(sys.modules[__name__],case)
sys.settrace(trace)
try:
call()
finally:
sys.settrace(None)

Result:

# case1
name: case1
source:
 def case1():
class C:
def __init__(self):
pass
c = C()

name: C
source:
 def case1():
class C:
def __init__(self):
pass
c = C()

name: __init__
source:
 def __init__(self):
pass

# case2
name: case2
source:
 def case2():
a = 1
class C:
def __init__(self):
pass
c = C()

name: C
source:
 def case2():
a = 1
class C:
def __init__(self):
pass
c = C()

name: __init__
source:
 def __init__(self):
pass

# case3
name: case3
source:
 def case3():
def fn():
pass
class C:
def __init__(self):
pass
c = C()

name: C
source:
 def fn():
pass

name: __init__
source:
 def __init__(self):
pass

The source listed for frames named 'C' (the class creation code) is not 
consistent across all three cases. It could be considered incorrect in all 
cases as it does not correspond only to the class definition source lines.

--
components: Library (Lib)
messages: 226537
nosy: isedev
priority: normal
severity: normal
status: open
title: inconsistent results with inspect.getsource() / inspect.getsourcelines()
type: behavior
versions: Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22355] inconsistent results with inspect.getsource() / inspect.getsourcelines()

[Iestyn Elfick]

Iestyn Elfick added the comment:

Possible fix:

--- /usr/lib64/python3.3/inspect.py 2014-06-30 19:21:52.0 +0200
+++ inspect.py  2014-09-07 17:41:29.463936079 +0200
@@ -600,7 +600,8 @@
 if not hasattr(object, 'co_firstlineno'):
 raise IOError('could not find function definition')
 lnum = object.co_firstlineno - 1
-pat = re.compile(r'^(\s*def\s)|(.*(? 0:
 if pat.match(lines[lnum]): break
 lnum = lnum - 1

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22356] mention explicitly that stdlib assumes gmtime(0) epoch is 1970

[Akira Li]

New submission from Akira Li:

See discussion on Python-ideas
https://mail.python.org/pipermail/python-ideas/2014-September/029228.html

--
assignee: docs@python
components: Documentation
files: docs-time-epoch_is_1970.diff
keywords: patch
messages: 226539
nosy: akira, docs@python
priority: normal
severity: normal
status: open
title: mention explicitly that stdlib assumes gmtime(0) epoch is 1970
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file36567/docs-time-epoch_is_1970.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22299] resolve() on Windows makes some pathological paths unusable

[eryksun]

eryksun added the comment:

> If you take "//?/C:/" and join it with e.g. "foo", you get an 
> absolute path (or, if you remove the drive's trailing slash, you 
> get something that's invalid AFAIK).

FYI, DOS device names such as "C:" are NT symlinks. Win32 looks for DOS device 
links in NT's \Global?? directory, and also per logon-session in 
\Sessions\0\DosDevices\LOGON_ID. 

A link named "C:foo" is actually possible:

>>> windll.kernel32.DefineDosDeviceW(0, "C:foo", "C:\\Python34")
1
>>> gfpn = os.path._getfinalpathname
>>> gfpn(r'\\?\C:foo')
'?\\C:\\Python34'
>>> os.listdir(r'\\?\C:foo')
['DLLs', 'Doc', 'include', 'Lib', 'libs', 'LICENSE.txt', 'NEWS.txt', 
'python.exe', 'pythonw.exe', 'README.txt', 'Scripts', 'tcl', 'Tools']

GLOBALROOT links to the native NT root:

>>> gfpn('?\\GLOBALROOT\\Global??\C:\\')
'?\\C:\\'
>>> gfpn('?\\GLOBALROOT\\Device\\HarddiskVolume1\\')   
'?\\C:\\'
>>> gfpn(r'\\?\GLOBALROOT\SystemRoot') 
'?\\C:\\Windows'
>>> p = r'\\?\GLOBALROOT\Sessions\0\DosDevices\-0f341de9\C:foo' 
   
>>> gfpn(p)
'?\\C:\\Python34'

Without the \\?\ prefix, "C:foo" is relative to the current directory on the C: 
drive:

>>> os.chdir('C:\\')
>>> os.mkdir('foo')
>>> os.listdir('C:foo')
[]

where the current directory on C: is stored in the "=C:" environment variable:

>>> buf = (c_wchar * 100)()
>>> windll.kernel32.GetEnvironmentVariableW("=C:", buf)
3
>>> buf.value
'C:\\'

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22198] Odd floor-division corner case

[Petr Viktorin]

Petr Viktorin added the comment:

I tried my hand at writing a patch. I hope it is helpful.

The message of the 2001 commit that introduces this says that "there's no 
platform-independent way to write a test case for this". I assume with 
@support.requires_IEEE_754 that is no longer true (at least for non-exotic 
platforms), or was there another issue?

I noticed there is no test suite for float floordiv, so I attempted writing a 
fuller one, but when I saw that
>>> float('inf') // 1.0
nan
I decided to keep my first CPython patch small and focused, so I can learn the 
ropes. I'll file more issues later.

--
keywords: +patch
nosy: +encukou
Added file: http://bugs.python.org/file36568/issue22198.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22198] Odd floor-division corner case

[Petr Viktorin]

Petr Viktorin added the comment:

Note: I signed the contributor agreement form recently, I should have a * soon.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22353] re.findall() documentation lacks information about finding THE LAST iteration of repeated capturing group (greedy)

[Guido van Rossum]

Guido van Rossum added the comment:

Do you have a specific sentence or paragraph in mind that could be added?

Be aware help() just shows what's in the docstring, which is typically 
abbreviated.  The full docs are on docs.python.org.  Can you find what you need 
there?

--
nosy: +gvanrossum

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22212] zipfile.py fails if zlib.so module fails to build.

[Alex Lord]

Alex Lord added the comment:

Just adding that I have also run into this problem.

--
nosy: +Alex.Lord

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22257] PEP 432: Redesign the interpreter startup sequence

[Jesús Cea Avión]

Changes by Jesús Cea Avión :


--
nosy: +jcea

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22357] inspect module documentation make no reference to __qualname__ attribute

[Iestyn Elfick]

New submission from Iestyn Elfick:

The documentation for the 'inspect' module should list the '__qualname__' 
attribute for 'method', 'function' and 'builtin' types in section '29.12.1 
Types and members'.

--
assignee: docs@python
components: Documentation
messages: 226545
nosy: docs@python, isedev
priority: normal
severity: normal
status: open
title: inspect module documentation make no reference to __qualname__ attribute
type: behavior
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5309] distutils doesn't parallelize extension module compilation

[Éric Araujo]

Éric Araujo added the comment:

> self.parallel = int(self.parallel) would raise ValueError when a
> non-number is passed. I suggest to print user-friendly error message.

The distutils idiom would be to catch the TypeError/ValueError and raise 
DistutilsOptionError.  Higher layers convert that to a message.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22357] inspect module documentation makes no reference to __qualname__ attribute

[Iestyn Elfick]

Changes by Iestyn Elfick :


--
title: inspect module documentation make no reference to __qualname__ attribute 
-> inspect module documentation makes no reference to __qualname__ attribute

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22358] Unnecessary JUMP_FORWARD(0) (NOP) in if statements without else or elif

[Attila Fazekas]

New submission from Attila Fazekas:

The following example function compiles to bytecode which contains,
an unnecessary JUMP_FORWARD 0 instruction:

def func():
if a: pass

Actual:
dis.dis(func)
  2   0 LOAD_GLOBAL  0 (a)
  3 POP_JUMP_IF_FALSE9
  6 JUMP_FORWARD 0 (to 9)
>>9 LOAD_CONST   0 (None)
 12 RETURN_VALUE  

Expected:
dis.dis(func)
  2   0 LOAD_GLOBAL  0 (a)
  3 POP_JUMP_IF_FALSE6
>>6 LOAD_CONST   0 (None)
  9 RETURN_VALUE

The above JUMP_FORWARD instruction increases the code size and also has a 
negative performance effect.
I do not see any reason to have the extra NOP in the byte code in this case.

***

The attached patch removes this NOP generation from the code compilation part, 
so it will take effect by default.

I had a little trouble when the code compiled from ast,
because the If.orelse had a different content. (NULL vs. zero sizes asdl_seq)

* The generated Assembly code updated in dis unit test.
* The compilation test updated to test a real 'if' by using a variable in the 
condition. (The True and False is not a variable anymore)

--
components: Interpreter Core
files: python_nop_ifelse.patch
keywords: patch
messages: 226547
nosy: Attila.Fazekas
priority: normal
severity: normal
status: open
title: Unnecessary JUMP_FORWARD(0) (NOP) in if statements without else or elif
type: performance
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file36569/python_nop_ifelse.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22358] Unnecessary JUMP_FORWARD(0) (NOP) in if statements without else or elif

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17095] Modules/Setup *shared* support broken

[Ned Deily]

Ned Deily added the comment:

Clearly this breaks running from the build directory for various modules when 
their optional C extension module build fails.  I'll either change the Setup 
shared builds to use a build directory or revert the path changes prior to the 
upcoming 3.4.2.

--
assignee:  -> ned.deily
nosy: +larry
priority: normal -> release blocker
stage: resolved -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22285] The Modules/ directory should not be added to sys.path

[Ned Deily]

Ned Deily added the comment:

Closing as a duplicate of the re-opened Issue17095 (since the changes there 
haven't been released yet)

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Modules/Setup *shared* support broken
versions: +Python 3.4, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22212] zipfile.py fails if zlib.so module fails to build.

[Ned Deily]

Ned Deily added the comment:

This problem has been introduced by the initial changes for Issue17095.  That 
issue has been re-opened and the resolution will be covered there.

--
nosy: +ned.deily
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> Modules/Setup *shared* support broken

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19884] Importing readline produces erroneous output

[Ned Deily]

Ned Deily added the comment:

Should this be a release blocker for 3.4.2?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21112] 3.4 regression: unittest.expectedFailure no longer works on TestCase subclasses

[Ned Deily]

Ned Deily added the comment:

Should this be fixed for 3.4.2?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21112] 3.4 regression: unittest.expectedFailure no longer works on TestCase subclasses

[Larry Hastings]

Larry Hastings added the comment:

Note: current plan for 3.4.2 is to release at the end of the month.  RC1 will 
be in about a week.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22358] Unnecessary JUMP_FORWARD(0) (NOP) in if statements without else or elif

[Jesús Cea Avión]

Jesús Cea Avión added the comment:

What about the peephole optimizer?.

--
nosy: +jcea

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19693] "make altinstall && make install" behaviour differs from "make install"

[Ned Deily]

Ned Deily added the comment:

Ping.  Also this will be presumably be an issue for the approved 2.7.x backport 
of ensurepip.

--
versions: +Python 2.7, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17095] Modules/Setup *shared* support broken

[John Malmberg]

Changes by John Malmberg :


--
nosy: +John.Malmberg

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15594] test_copyfile_named_pipe() fails on Mac OS X Snow Leopard: OSError: [Errno 22] Invalid argument

[Ned Deily]

Ned Deily added the comment:

Closing since there have been no further reports of this problem and this 
buildbot is no longer connected

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11487] build_installer.py should avoid relying on a young Python

[Ned Deily]

Ned Deily added the comment:

The changes for Issue21383 added calls to "make touch" to build_installer.py so 
the initial problem reported here should no longer occur on any OS X installer 
build.  As to the more general problem of needing to use "make touch" because 
hg checkouts do not preserve original file checkin time orders, there have been 
multiple issues opened (and closed) on that subject; there's no need to keep 
this issue open for that.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed
versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2, Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19884] Importing readline produces erroneous output

[STINNER Victor]

STINNER Victor added the comment:

The test fails on some platforms but it's not a regression.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com