[issue22113] memoryview and struct.pack_into

[Kristján Valur Jónsson]

Kristján Valur Jónsson added the comment:

lgtm :)

--

___
Python tracker 

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

[issue21862] cProfile command-line should accept "-m module_name" as an alternative to script path

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc added the comment:

The patch does not seem to allow parameters after the -m option.
I'm sure this restriction can be lifted.

--
nosy: +amaury.forgeotdarc

___
Python tracker 

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

[issue21279] str.translate documentation incomplete

[John Posner]

John Posner added the comment:

Regarding Martin's patch of 12-18:

stdtypes.rst -- looks good to me

unicodeobject.c -- I suggest changing this sentence:

If a character is not in the table, the subscript operation should raise 
LookupError, and the character is left untouched.

 ... to:

If the subscript operation raises a LookupError, the character is left 
untouched.

--

___
Python tracker 

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

[issue23085] update internal libffi copy to 3.2.1

[Gustavo Temple]

Gustavo Temple added the comment:

@steve.dower, so, can I abandon this issue?

--

___
Python tracker 

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

[issue23085] update internal libffi copy to 3.2.1

[Steve Dower]

Steve Dower added the comment:

I'm not entirely familiar with our layout of libffi, but I don't think your 
patch will affect Windows at all. If your intent was to update the version used 
in Windows builds, then you may as well abandon it. I'm not the one to ask 
about other platforms - apparently we need new ctypes maintainers...

--

___
Python tracker 

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

[issue23085] update internal libffi copy to 3.2.1

[Gustavo Temple]

Gustavo Temple added the comment:

@steve.dower, so no problems, because my patch won't affect Windows.

--

___
Python tracker 

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

[issue23089] Update config files

[Gustavo Temple]

New submission from Gustavo Temple:

Update config.guess and config.sub

--
components: Installation
files: config.patch
keywords: patch
messages: 232937
nosy: gustavotemple
priority: normal
severity: normal
status: open
title: Update config files
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file37506/config.patch

___
Python tracker 

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

[issue23089] Update config files

[Gustavo Temple]

Changes by Gustavo Temple :


--
nosy: +doko

___
Python tracker 

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

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
components: +Extension Modules -Library (Lib)
status: open -> closed

___
Python tracker 

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

[issue23089] Update libffi config files

[R. David Murray]

R. David Murray added the comment:

How does this patch relate to the discussion on python-dev about libffi?

--
components: +ctypes
nosy: +r.david.murray
title: Update config files -> Update libffi config files

___
Python tracker 

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

[issue23089] Update libffi config files

[Gustavo Temple]

Gustavo Temple added the comment:

@r.david.murray, I think they aren't related.

--

___
Python tracker 

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

[issue23089] Update libffi config files

[R. David Murray]

R. David Murray added the comment:

What is the purpose of your patch, then?

--

___
Python tracker 

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

[issue22896] Don't use PyObject_As*Buffer() functions

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Updated patch addresses Antoine's comments.

I still hesitate about C-contiguousity. Looks as all buffers created in the 
stdlib are C-contiguous, so we can't test non-contiguous buffers. Shouldn't 
PyObject_AsCharBuffer (or even PyObject_AsReadBuffer and_PyBuffer_Converter) 
accept only C-contiguous buffers? Who are buffer protocol experts?

--
Added file: http://bugs.python.org/file37507/buffers_2.patch

___
Python tracker 

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

[issue23089] Update libffi config files

[Gustavo Temple]

Gustavo Temple added the comment:

@r.david.murray, the config.guess inside the root folder fixes some 
verifications about IBM arch, the config.guess inside the libffi folder fixes 
some verifications about PowerPC, and the config.sub inside the libffi folder 
fixes some verifications about ppc64p7.

--

___
Python tracker 

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

[issue23063] `python setup.py check --restructuredtext --strict --metadata` fails with: `warning: check: Could not finish the parsing.` if the RST document uses code or code-block directives.

[Éric Araujo]

Éric Araujo added the comment:

An active core developer needs to see this and decide to commit the patch.  You 
can see if there’s someone on IRC.  If there’s no action in a week or two, feel 
free to ask on python-dev (maybe listing more than one waiting patch, or 
offering reviews in exchange for core dev time).

--
stage: patch review -> commit review

___
Python tracker 

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

[issue23090] fix test_doctest relying on refcounting to close files

[Brian Kearns]

Changes by Brian Kearns :


--
files: fix_test_doctest.patch
keywords: patch
nosy: bdkearns
priority: normal
severity: normal
status: open
title: fix test_doctest relying on refcounting to close files
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file37508/fix_test_doctest.patch

___
Python tracker 

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

[issue22896] Don't use PyObject_As*Buffer() functions

[Antoine Pitrou]

Antoine Pitrou added the comment:

> Shouldn't PyObject_AsCharBuffer (or even PyObject_AsReadBuffer 
> and_PyBuffer_Converter) accept only C-contiguous buffers?

PyBUF_SIMPLE enforces contiguity. See 
https://www.python.org/dev/peps/pep-3118/#access-flags and 
https://docs.python.org/3/c-api/buffer.html#c.Py_buffer.len

Also Stefan's post at 
http://mail.scipy.org/pipermail/numpy-discussion/2011-August/058189.html

Perhaps Stefan can confirm.

--
nosy: +skrah

___
Python tracker 

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

[issue23089] Update libffi config files

[R. David Murray]

R. David Murray added the comment:

How do these relate to the upstream libffi?  I think we probably need to deal 
with this as part of the libffi discussion on python-dev.

--

___
Python tracker 

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

[issue23051] multiprocessing.pool methods imap()[_unordered()] deadlock

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
title: multiprocessing.pool methods imap() and imap_unordered() cause deadlock 
-> multiprocessing.pool methods imap()[_unordered()] deadlock

___
Python tracker 

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

[issue22896] Don't use PyObject_As*Buffer() functions

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Ah, there is a way to create non-contiguous buffers.

>>> b = bytes(range(16))
>>> m = memoryview(b)
>>> m[::2].c_contiguous
False

> PyBUF_SIMPLE enforces contiguity.

Then contiguousity check in getbuffer() in Python/getargs.c is redundant. And 
in most cases the use of _PyBuffer_Converter() and PyObject_GetBuffer() could 
be replaced by the use of "y*" and "w*" format units.

--

___
Python tracker 

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

[issue22896] Don't use PyObject_As*Buffer() functions

[Stefan Krah]

Stefan Krah added the comment:

Yes, a PyBUF_SIMPLE request implies c-contiguous, so it's ok.

--

___
Python tracker 

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

[issue23059] cmd module should sort misc help topics

[Terry J. Reedy]

Terry J. Reedy added the comment:

cmd.Cmd has a documented do_help(self, arg) method (written in 2000).  If arg 
is '', it prints
1. Documented commands (do_x with help_x or do_x.__doc__ != ''), sorted
2. Other help topics (help_y with no do_y), unsorted
3. Undocumented commands (do_ without no help_x and no do_x.__doc__), sorted

The dict called 'help' (which should be a set, and might better be called 
'topics') ends up with a member for each help_y topic without a do_y command.  
Not sorting the keys is at least a design bug.  Leaving users aside, it makes 
do_help unpredictable and hard to test.  Our test.test_cmd omits misc help 
topics.  In verbose mode, it prints

Trying:
mycmd.do_help("")
Expecting:

Documented commands (type help ):

add  help

Undocumented commands:
==
exit  shell

ok

As near as I can tell, text_cmd would still pass if Misc topics were removed 
and never printed.  Topics can only be added to the test above is they are 
dependably ordered (ie, sorted).

---
This '?' or 'help' case is also not properly documented, but should be.  3.4 
cmd.__doc__ has this mishmash:

"With no arguments, it lists all topics with defined help_ functions, broken 
into up to three topics; documented commands, miscellaneous help topics, and 
undocumented commands."

3.4 doc says "With no argument, do_help() lists all available help topics (that 
is, all commands with corresponding help_*() methods or commands that have 
docstrings), and also lists any undocumented commands."

--
nosy: +terry.reedy
stage:  -> test needed
type:  -> enhancement

___
Python tracker 

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

[issue23061] Update pep8 to specify explicitly 'module level' imports at top of file

[Terry J. Reedy]

Terry J. Reedy added the comment:

I read Nick's post and I would like PEP8 to continue to discourage imports at 
class scope unless there is actually a use case.  I discovered yesterday that 
idlelib.ColorDelegator has several imports at the top of the module and more as 
the top of the class (of the same name).  I cannot think of any good reason for 
the split.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue23051] multiprocessing.pool methods imap()[_unordered()] deadlock

[Josh Rosenberg]

Changes by Josh Rosenberg :


--
nosy: +josh.r

___
Python tracker 

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

[issue23069] IDLE's F5 Run Module doesn't transfer effects of future import

[Terry J. Reedy]

Terry J. Reedy added the comment:

I agree that this is broken.  I verified that the following works in 2.7.9

>>> from __future__ import division, print_function
>>> 32 / 5
6.4
>>> print(2,3,sep='**')
2**3

#13296 was about self.compile.compiler.flags (in ModifiedInterpreter, which 
inherits .compile... from code.InteractiveInterpreter) not being *reset* to 
their original values upon Shell restart.  They are now.

This issue is about the same flags not being *set* by Run Module.  This will be 
tricky to fix, but I think it can be done using the previous flag issue as a 
hint.

self.compile (in InteractiveInterpreter) = codeop.CommandCompiler().
The docstring for the class says
"""Instances of this class have __call__ methods identical in
signature to compile_command; the difference is that if the
instance compiles program text containing a __future__ statement,
the instance 'remembers' and compiles all subsequent program texts
with the statement in force."""
The __call__ method handles partial or complete single statements.

Run -> Run Module F5, on the other hand,  is handled by the ScriptBindind.py 
extension.  ScriptBinding.run_module_event calls .checksyntax().  The latter 
calls builtin compile(), independent of the shell interpreter.compile, without 
saving the compile flags.

To save the compile flags, we could use codeop.Compile.__call__, which calls 
builtin compile() and then extracts and saves future compile flags from the 
resulting code object using constants defined in the module.

The next issue is timing.  The shell restarts (and resets its flags) only after 
the file passes compile and tabnanny steps.  After the restart, it should be 
possible to update the shell compile flags with any future flags saved by the 
Compile() instance.

I have skipped over some details (including the lack of tests for Run Module), 
but I *think* that the above outlines a safe solution.  As for 3.x, there are 
changes in 3.4 ScriptBinding.py, but the essential points for this issue seem 
the same.  3.x should be patched also to be ready for future __future__ imports.

--
nosy: +terry.reedy
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

[issue22896] Don't use PyObject_As*Buffer() functions

[Martin Panter]

Changes by Martin Panter :


--
nosy: +vadmium

___
Python tracker 

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

[issue23087] Exec variable not found error

[Terry J. Reedy]

Terry J. Reedy added the comment:

https://stackoverflow.com/questions/27554334/python-3-dictionary-comprehension-exec-error/27571212#27571212

--
nosy: +terry.reedy
resolution:  -> not a bug
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

[issue15443] datetime module has no support for nanoseconds

[mdcb]

mdcb added the comment:

patch in attachment is an attempt to provide the datetime type nanosecond 
support, handles pickle versioning, expose a new class method 
datetime.fromnanoseconds

--
keywords: +patch
nosy: +mdcb...@gmail.com
Added file: http://bugs.python.org/file37509/datetime.nanosecond.patch

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[mdcb]

Changes by mdcb :


___
Python tracker 

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

[issue15955] gzip, bz2, lzma: add option to limit output size

[Nikolaus Rath]

Nikolaus Rath added the comment:

*ping*. It's been another 8 months. It would be nice if someone could review 
the patch.

--

___
Python tracker 

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

[issue23004] mock_open() should allow reading binary data

[Aaron Hill]

Aaron Hill added the comment:

I've fixed the formatting issues.

--
Added file: 
http://bugs.python.org/file37510/mock-open-allow-binary-data-fix-formatting.patch

___
Python tracker 

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

[issue23080] BoundArguments.arguments should be unordered

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
nosy: +brett.cannon

___
Python tracker 

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

[issue21071] struct.Struct.format is bytes, but should be str

[Raymond Hettinger]

Raymond Hettinger added the comment:

I would like to see this and issue 8934 discussed as a usability bug.  As far 
as I can tell, the current state of affairs an unintended by-product of a 
rushed effort to split the standard library to bytes apis and unicode apis.  I 
don't see any reason that we should have to live with this forever.

--
nosy: +rhettinger

___
Python tracker 

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

[issue23091] unpacked keyword arguments are not unicode normalized

[S. Andrew Sheppard]

New submission from S. Andrew Sheppard:

I came across unexpected behavior working with unpacking keyword arguments in 
Python 3.  It appears to be related to the automatic normalization of unicode 
characters to NFKC (PEP 3131), which converts e.g. MICRO SIGN to GREEK SMALL 
LETTER MU.  This conversion is applied to regular keyword arguments but not 
when unpacking arguments via **.

This issue arose while I was working with some automatically generated 
namedtuple classes, but I was able to reproduce it with a simple function:

def test(μ):
print(μ)

>>> test(µ="test1") # chr(181)
test1

>>> test(μ="test2") # chr(956)
test2

>>> test(**{'μ': "test3"}) # chr(956)
test3

>>> test(**{'µ': "test4"}) # chr(181)

Traceback (most recent call last):
  File "", line 1, in 
TypeError: test() got an unexpected keyword argument 'µ'


I can obviously work around this, but wanted to bring it up in case it's a bug. 
 My naive expectation would be that unpacked ** keys should be treated exactly 
like normal keyword arguments.

--
components: Unicode
messages: 232956
nosy: ezio.melotti, haypo, sheppard
priority: normal
severity: normal
status: open
title: unpacked keyword arguments are not unicode normalized
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

[issue23092] Python 2.7.9 test_readline regression on CentOS 6

[Vinson Lee]

New submission from Vinson Lee:

test_readline regressed from Python 2.7.8 to Python 2.7.9 on CentOS 6

Python 2.7.8
$ ./python -m test.regrtest test_readline
test_readline
1 test OK.

Python 2.7.9
$ ./python -m test.regrtest test_readline
[1/1] test_readline
test test_readline failed -- Traceback (most recent call last):
  File "Python-2.7.9/Lib/test/test_readline.py", line 56, in test_init
self.assertEqual(stdout, b'')
AssertionError: '\x1b[?1034h' != ''

1 test failed:
test_readline

$ cat /etc/redhat-release
CentOS release 6.6 (Final)

$ rpm -qa | grep readline
readline-6.0-4.el6.x86_64
compat-readline5-5.2-17.1.el6.x86_64
readline-devel-6.0-4.el6.x86_64

--
components: Tests
messages: 232957
nosy: vlee
priority: normal
severity: normal
status: open
title: Python 2.7.9 test_readline regression on CentOS 6
versions: Python 2.7

___
Python tracker 

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

[issue23091] unpacked keyword arguments are not unicode normalized

[S. Andrew Sheppard]

S. Andrew Sheppard added the comment:

Here's a simple namedtuple example for good measure.

from collections import namedtuple
Test = namedtuple("Test", [chr(181)])

>>> Test(**{chr(956): "test1"})
Test(µ='test1')

>>> Test(**{chr(181): "test1"})
Traceback (most recent call last):
  File "", line 1, in 
TypeError: __new__() got an unexpected keyword argument 'µ'

--

___
Python tracker 

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

[issue23091] unpacked keyword arguments are not unicode normalized

[R. David Murray]

R. David Murray added the comment:

I suspect that the normalization is happening in the parsing phase.  That is, 
the keyword argument gets normalized when the python source is compiled, but 
the dictionary key is, of course, *not* normalized, since it is a literal 
string.  If I'm right, I think is not a bug.

--
nosy: +r.david.murray

___
Python tracker 

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

[issue23091] unpacked keyword arguments are not unicode normalized

[Benjamin Peterson]

Benjamin Peterson added the comment:

Yeah, kwarg dicts do not have the same checks applied to them as syntactic 
keyword args. It would be weird if, for example, dict(**mydict) normalized the 
keys of mydict.

--
nosy: +benjamin.peterson
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

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

[issue22836] Broken "Exception ignored in:" message on exceptions in __repr__

[Martin Panter]

Martin Panter added the comment:

Here is a patch that substitutes an explanation if the repr() fails. Output now 
looks like this, terminated with a newline:

=== BrokenObj ===
Exception ignored in: 
Traceback (most recent call last):
  File "", line 3, in __del__
Exception: in del
$ ./python -c 'import sys; sys.stdout.detach()'
Exception ignored in: 
ValueError: underlying buffer has been detached

I also made it work sensibly if printing the exception message fails:

>>> class Exception(Exception):
... def __str__(self): raise Exception("Exception is broken")
... 
>>> f = BrokenObj(); del f
Exception ignored in: 
Traceback (most recent call last):
  File "", line 3, in __del__
__main__.Exception: 
>>> raise Exception()
Traceback (most recent call last):
  File "", line 1, in 
__main__.Exception: 
>>>

--
keywords: +patch
Added file: http://bugs.python.org/file37511/unraisable-continue.patch

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[mdcb]

mdcb added the comment:

minor bug fixes and improvements in new attachment.

--
Added file: http://bugs.python.org/file37512/datetime.nanosecond.patch

___
Python tracker 

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

[issue5319] stdout error at interpreter shutdown fails to return OS error status

[Martin Panter]

Changes by Martin Panter :


--
nosy: +vadmium

___
Python tracker 

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

[issue23091] unpacked keyword arguments are not unicode normalized

[S. Andrew Sheppard]

S. Andrew Sheppard added the comment:

Fair enough.  For future reference by anyone coming across this issue, here's a 
simplified version of the workaround I used:

from unicodedata import normalize
def normalize_keys(data):
return {
normalize('NFKC', key): value
for key, value in data.items()
}

def test(μ):
print(μ)

>>> test(**normalize_keys({'µ': "test4"}))
test4

--

___
Python tracker 

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

[issue23065] Pyhton27.dll at SysWOW64 not updated when updating Python 2.7.X

[Steve Dower]

Steve Dower added the comment:

That's strange, and it isn't what normally happens, so I suspect it's a 
configuration or corruption issue on your machine (possibly Kapersky Pure is to 
blame?). The 2.7.7, 2.7.8 and 2.7.9 installers all have the correct version 
information and there's no indication that under normal circumstances the 
upgrade wouldn't be fine.

We're also not investing much time into the installer for 2.7 any more - the 
builds are still coming because I'm building them, but I'm not able to actively 
maintain it beyond that - and so we don't really have much interest in 
debugging issues with workarounds.

So thank you for reporting the problem, but there probably won't be a fix 
coming for it and you'll need to uninstall 2.7.9 before upgrading to the next 
version.

--

___
Python tracker 

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

[issue22671] Typo in class io.BufferedIOBase docs

[Chandan kumar]

Changes by Chandan kumar :


--
nosy: +Chandan.kumar

___
Python tracker 

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

[issue23092] Python 2.7.9 test_readline regression on CentOS 6

[Berker Peksag]

Berker Peksag added the comment:

This looks like a duplicate of issue 19884.

--
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Importing readline produces erroneous output
type:  -> behavior

___
Python tracker 

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

[issue23092] Python 2.7.9 test_readline regression on CentOS 6

[Vinson Lee]

Vinson Lee added the comment:

The regression is introduced with this commit.

commit fa06e2bb13a3e67a0641025483efb19ef569dbd9
Author: Victor Stinner 
Date:   Thu Jul 24 12:22:24 2014 +0200

Issue #19884: readline: Disable the meta modifier key if stdout is not a
terminal to not write the ANSI sequence "\033[1034h" into stdout. This 
sequence
is used on some terminal (ex: TERM=xterm-256color") to enable support of 8 
bit
characters.

--

___
Python tracker 

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