[issue22234] urllib.parse.urlparse accepts any falsy value as an url

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

`x != ''` emits BytesWarning if x is bytes. 'encode' attribute is not needed 
for URL parsing. any() is slower that a `for` loop.

I would suggest to look at efficient os.path implementations.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue26847] filter docs unclear wording

[Georg Brandl]

Georg Brandl added the comment:

You didn't test your examples:

>>> [] == False
False

False is not equal to the "empty value" of any other type than other numeric 
types.  (This is mostly because of how booleans were originally introduced to 
Python.)

"is false", on the other hand, is the conventional shorthand for `bool(x) == 
False`.

--
nosy: +georg.brandl
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

[issue26848] asyncio.subprocess's communicate() method mishandles empty input bytes

[Jack O'Connor]

Jack O'Connor added the comment:

Related: The asyncio communicate() method differs from standard subprocess in 
how it treats input bytes when stdin is (probably mistakenly) not set to PIPE. 
Like this:

proc = await create_subprocess_shell("sleep 5")
await proc.communicate(b"foo")  # Oops, I forgot stdin=PIPE above!

The standard, non-async version of this example, communicate would ignore the 
input bytes entirely. But here in the asyncio version, communicate will try to 
write those bytes to stdin, which is None, and the result is an AttributeError.

Since the user probably only hits this case by mistake, I think raising an 
exception is preferable. But it would be nice to raise an exception that 
explicitly said "you've forgotten stdin=PIPE" instead of the unhelpful 
"'NoneType' object has no attribute 'write'". Maybe it would be worth cleaning 
this up while we're here?

--

___
Python tracker 

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

[issue26848] asyncio.subprocess's communicate() method mishandles empty input bytes

[Jack O'Connor]

Jack O'Connor added the comment:

Thanks for the heads up, Berker, I've re-submitted the PR as 
https://github.com/python/asyncio/pull/335.

--

___
Python tracker 

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

[issue26848] asyncio.subprocess's communicate() method mishandles empty input bytes

[Berker Peksag]

Berker Peksag added the comment:

python/cpython is a semi-official read-only mirror of hg.python.org/cpython. We 
haven't switched to GitHub yet. You may want to open a pull request to 
https://github.com/python/asyncio See 
https://github.com/python/asyncio/wiki/Contributing for details.

--
nosy: +berker.peksag

___
Python tracker 

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

[issue26848] asyncio.subprocess's communicate() method mishandles empty input bytes

[Jack O'Connor]

New submission from Jack O'Connor:

Setting stdin=PIPE and then calling communicate(b"") should close the child's 
stdin immediately, similar to stdin=DEVNULL. Instead, communicate() treats b"" 
like None and leaves the child's stdin open, which makes the child hang forever 
if it tries to read anything.

I have a PR open with a fix and a test: 
https://github.com/python/cpython/pull/33

--
components: asyncio
messages: 264212
nosy: gvanrossum, haypo, oconnor663, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.subprocess's communicate() method mishandles empty input bytes
type: behavior
versions: Python 3.5, Python 3.6

___
Python tracker 

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

[issue22234] urllib.parse.urlparse accepts any falsy value as an url

[Luiz Poleto]

Luiz Poleto added the comment:

As discussed on the Mentors list, the attached patch (issue22234_37.patch) 
changes the urlparse function to handle non-str and non-bytes arguments and 
adds a new test case for it.

--
Added file: http://bugs.python.org/file42592/issue22234_37.patch

___
Python tracker 

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

[issue22234] urllib.parse.urlparse accepts any falsy value as an url

[Luiz Poleto]

Luiz Poleto added the comment:

As discussed on the Mentors list, the attached patch (issue22234_36.patch) 
includes the deprecation warning (and related test) on the urlparse function.

--
keywords: +patch
versions: +Python 3.6 -Python 3.4
Added file: http://bugs.python.org/file42591/issue22234_36.patch

___
Python tracker 

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

[issue26847] filter docs unclear wording

[Luke]

Luke added the comment:

josh, we're saying the same thing but misunderstanding each other. :)

I realize that they can be empty containers, etc., and that's why I think 
"equal to False" is appropriate -- because those things *are* equal to False:

>>> [] == False
True
>>> 0 == False
True
etc.

However, they are not identical to False:

>>> [] is False
False
>>> 0 is False
False

And that's why I think the wording "are false" is potentially misleading.

Perhaps there's a better wording than "equal to False" (compares equivalently 
to False? or simply: are falsey? :p), but anyhow, we're identifying the same 
behaviour here.

--

___
Python tracker 

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

[issue26847] filter docs unclear wording

[Josh Rosenberg]

Josh Rosenberg added the comment:

That's why lower case "false" is used, not "False"; the former is the loose 
definition, the latter is the strict singleton.

--

___
Python tracker 

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

[issue26847] filter docs unclear wording

[Josh Rosenberg]

Josh Rosenberg added the comment:

"are equal to False" would be wrong though. Any "falsy" value is preserved by 
filterfalse, and removed by filter. They need not be equal to False (the bool 
singleton); empty containers (e.g. (), [], {}, "") are all considered false, 
and behave as such, despite not being equal to False.

--
nosy: +josh.r

___
Python tracker 

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

[issue26847] filter docs unclear wording

[Luke]

New submission from Luke:

The current docs for both filter and itertools.filterfalse use the following 
wording (emphasis added):

all elements that are false are removed
returns the items that are false
This could be confusing for a new Python programmer, because the actual 
behaviour is that elements are equality-compared, not identity-compared.

Suggested wording: "are equal to False"

https://docs.python.org/3.5/library/functions.html#filter
https://docs.python.org/3.5/library/itertools.html#itertools.filterfalse

--
assignee: docs@python
components: Documentation
messages: 264206
nosy: docs@python, unfamiliarplace
priority: normal
severity: normal
status: open
title: filter docs unclear wording
type: enhancement
versions: Python 3.5

___
Python tracker 

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

[issue26039] More flexibility in zipfile write interface

[Martin Panter]

Martin Panter added the comment:

I understand Python’s zipfile module does not allow reading unless seek() is 
supported (this was one of Марк’s complaints). So it is irrelevant whether we 
are writing.

I left a few comments, but it sounds like it is valid read and write at the 
same time.

--

___
Python tracker 

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

[issue16662] load_tests not invoked in package/__init__.py

[Anthony Sottile]

Anthony Sottile added the comment:

I have a hunch that this fix here may be causing this: 
https://github.com/spotify/dh-virtualenv/issues/148

Minimally:

echo 'from setuptools import setup; setup(name="demo")' > setup.py
echo 'import pytest' > tests/__init__.py

$ python setup.py test
running test
running egg_info
writing dependency_links to demo.egg-info/dependency_links.txt
writing demo.egg-info/PKG-INFO
writing top-level names to demo.egg-info/top_level.txt
reading manifest file 'demo.egg-info/SOURCES.txt'
writing manifest file 'demo.egg-info/SOURCES.txt'
running build_ext

--
Ran 0 tests in 0.000s

OK


$ python3.5 setup.py test
running test
running egg_info
writing demo.egg-info/PKG-INFO
writing dependency_links to demo.egg-info/dependency_links.txt
writing top-level names to demo.egg-info/top_level.txt
reading manifest file 'demo.egg-info/SOURCES.txt'
writing manifest file 'demo.egg-info/SOURCES.txt'
running build_ext
tests (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/tmp/foo/tests/__init__.py", line 1, in 
import pytest
ImportError: No module named 'pytest'


--
Ran 1 test in 0.000s

FAILED (errors=1)

--
nosy: +Anthony Sottile

___
Python tracker 

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

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

[Stefan Krah]

Changes by Stefan Krah :


--
assignee:  -> skrah
components: +Build -Cross-Build
nosy: +skrah
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.6 -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

[issue22747] Interpreter fails in initialize on systems where HAVE_LANGINFO_H is undefined

[Stefan Krah]

Stefan Krah added the comment:

We don't support Android officially yet, but I think until #8610
is resolved something must be done here.

--

___
Python tracker 

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

[issue22747] Interpreter fails in initialize on systems where HAVE_LANGINFO_H is undefined

[Roundup Robot]

Roundup Robot added the comment:

New changeset ad6be34ce8c9 by Stefan Krah in branch 'default':
Issue #22747: Workaround for systems without langinfo.h.
https://hg.python.org/cpython/rev/ad6be34ce8c9

--
nosy: +python-dev

___
Python tracker 

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

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

[Roundup Robot]

Roundup Robot added the comment:

New changeset 0d74d4937ab9 by Stefan Krah in branch 'default':
Issue #20306: The pw_gecos and pw_passwd fields are not required by POSIX.
https://hg.python.org/cpython/rev/0d74d4937ab9

--
nosy: +python-dev

___
Python tracker 

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

[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions

[Martin Dengler]

Changes by Martin Dengler :


___
Python tracker 

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

[issue26846] Workaround for non-standard stdlib.h on Android

[Stefan Krah]

Changes by Stefan Krah :


--
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

[issue26846] Workaround for non-standard stdlib.h on Android

[Roundup Robot]

Roundup Robot added the comment:

New changeset fae01d14dd4e by Stefan Krah in branch 'default':
Issue #26846: Workaround for non-standard stdlib.h on Android.
https://hg.python.org/cpython/rev/fae01d14dd4e

--
nosy: +python-dev

___
Python tracker 

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

[issue26846] Workaround for non-standard stdlib.h on Android

[Stefan Krah]

New submission from Stefan Krah:

Android's stdlib.h pollutes the namespace by including a memory.h header.

--
assignee: skrah
components: Build
messages: 264199
nosy: skrah, xdegaye
priority: normal
severity: normal
status: open
title: Workaround for non-standard stdlib.h on Android
type: enhancement
versions: Python 3.6

___
Python tracker 

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

[issue26833] returning ctypes._SimpleCData objects from callbacks

[SilentGhost]

Changes by SilentGhost :


--
components: +ctypes
nosy: +amaury.forgeotdarc, belopolsky, meador.inge

___
Python tracker 

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

[issue26845] Misleading variable name in exception handling

[ProgVal]

New submission from ProgVal:

In Python/errors.c, PyErr_Restore is defined this way:

void
PyErr_Restore(PyObject *type, PyObject *value, PyObject *traceback)


In Python/ceval.c, in the END_FINALLY case, it is called like this:

PyErr_Restore(status, exc, tb);


I believe “exc” should be renamed to “val”.


Indeed, END_FINALLY pops values from the stack like this:

PyObject *status = POP();
// ...
else if (PyExceptionClass_Check(status)) {
 PyObject *exc = POP();
 PyObject *tb = POP();
 PyErr_Restore(status, exc, tb);


And, they are pushed like this, in fast_block_end:

PUSH(tb);
PUSH(val);
PUSH(exc);

--
components: Interpreter Core
messages: 264198
nosy: Valentin.Lorentz
priority: normal
severity: normal
status: open
title: Misleading variable name in exception handling
versions: Python 3.6

___
Python tracker 

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

[issue17905] Add check for locale.h

[Stefan Krah]

Stefan Krah added the comment:

I think all locale includes are unguarded now.

--

___
Python tracker 

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

[issue17905] Add check for locale.h

[Roundup Robot]

Roundup Robot added the comment:

New changeset cc501d439239 by Stefan Krah in branch 'default':
Issue #17905: Do not guard locale include with HAVE_LANGINFO_H.
https://hg.python.org/cpython/rev/cc501d439239

--
nosy: +python-dev

___
Python tracker 

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

[issue17905] Add check for locale.h

[Stefan Krah]

Stefan Krah added the comment:

Okay, closing as a duplicate (the second patch here that checks for
locale.h seems too broad to me since it's a standard header).

--
nosy: +skrah
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Interpreter fails in initialize on systems where 
HAVE_LANGINFO_H is undefined
versions: +Python 3.6 -Python 3.4

___
Python tracker 

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

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

[Stefan Krah]

Stefan Krah added the comment:

Thank you, closing this.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed
versions: +Python 3.6 -Python 3.4

___
Python tracker 

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

[issue25788] fileinput.hook_encoded has no way to pass arguments to codecs

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Added comments on Rietveld (follow the "review" link beside the patch link).

--
assignee:  -> serhiy.storchaka

___
Python tracker 

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

[issue19251] bitwise ops for bytes of equal length

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> If yes, maybe we should start with a module on PyPI. Is there a volunteer to 
> try this option?

bitsets – ordered subsets over a predefined domain
bitarray – efficient boolean array implemented as C extension
bitstring – pure-Python bit string based on bytearray
BitVector – pure-Python bit array based on unsigned short array
Bitsets – Cython interface to fast bitsets in Sage
bitfield – Cython positive integer sets
intbitset – integer bit sets as C extension

Is it enough? Ah, and NumPy.

--

___
Python tracker 

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

[issue9998] ctypes find_library should search LD_LIBRARY_PATH on linux

[Vinay Sajip]

Vinay Sajip added the comment:

> Does anyone have any valid use cases where they want to use a shared library 
> on LD_LIBRARY_PATH or similar

I presume that would include this issue's creator and other people who have 
commented here about what they see as a drawback in find_library's current 
behaviour.

Pau Tallada's point about wanting to use a cross-platform invocation also seems 
reasonable. Remember, if you know the exact library you want to use, you don't 
*need* find_library: and this issue is about making find_library useful in a 
wider set of cases than it currently is.

> The problem I see with using find_library() to blindly load a library

Nobody is saying that the result of find_library() has to be used to blindly 
load a library. The point you make about the code in the uuid module is 
orthogonal to the proposal in this issue - even the behaviour of find_library 
never changed, that code could break for the reasons you give. For that, it's 
not unreasonable to raise a separate issue about possible fragility of the code 
in uuid.

I asked a question which I think is relevant to this enhancement request - "is 
emulating a build-time linker the most useful thing? In the context of Python 
binding to external libraries, why is build-time linking behaviour better than 
run-time linking behaviour?"

Do you have an answer to that?

--

___
Python tracker 

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

[issue19251] bitwise ops for bytes of equal length

[Gregory P. Smith]

Gregory P. Smith added the comment:

I have wanted bytes/bytearray bit operations (be sure to include the in place 
operators for bytearray) when using micropython where it is normal to be 
operating on binary data.

that said, i'd need someone from micropython to chime in as to if they can 
magically detect
 # Equivalent of:  c = b ^ a
 c = bytes(x ^ y for x, y in zip(a, b))
and make it run fast.

what is a similar expression for an in place bytearray modification?
 # Equivalent of:  a ^= b
 assert len(a) == len(b)
 for i, b_i in enumerate(b): a[i] ^= b_i  ?

Why both of the above are slow is obvious: tons of work looping within python 
itself, creating and destroying small integers and/or tuples the entire time 
instead of deferring to the optimal loop in C.

Neither of the above "look as nice" as a simple operator would.
But they are at least both understandable and frankly about the same as what 
you would naively write in C for the task.

Security claims?  Nonsense. This has nothing to do with security.  It is 
*fundamentally impossible* to write constant time side channel attack resistant 
algorithms in a high level garbage collected language. Do not attempt it.  
Leave that stuff to assembler or _very_ carefully crafted C/C++ that the 
compiler cannot undo constant time enforcing tricks in.  Where it belongs.  
Python will never make such guarantees.

NumPy?  No.  That is a huge bloated dependency.  It is not relevant to this as 
we are not doing scientific computing.  It is not available everywhere.

The int.from_bytes(...) variant optimizations?  Those are hacks that might be 
useful to people in CPython today, but they are much less readable.  Do not 
write that in polite code, hide it behind a function with a comment explaining 
why it's so ugly to anyone who dares look inside please.

So as much as I'd love this feature to exist on bytes & bytearray, it is not a 
big deal that it does not.

Starting with a PyPI module for fast bit operations on bytes & bytearray 
objects makes more sense (include both pure python and a C extension 
implementation).  Use of that will give an idea of how often anyone actually 
wants to do this.

--

___
Python tracker 

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

[issue26842] Python Tutorial 4.7.1: Need to explain default parameter lifetime

[Edward Segall]

Edward Segall added the comment:

I agree with most of your points: A tutorial should be brief and should not go 
down rabbit holes. Expanded discussion of default parameter behavior would 
probably fit better with the other facets of parameter speceification and 
parameter passing, perhaps as a FAQ. 

But I also believe a change to the current presentation is needed. Perhaps it 
would be best to introduce default arguments using simple numerical types, and 
refer to a separate explanation (perhaps as a FAQ) of the complexities 
associated with using mutable objects as defaults. 

> Also, I don't really like the provided explanation, "there are two cases 
> ...".  The actual execution model has one case (default arguments are 
> evaluated once when the function is defined) and there are many ways to use 
> it.

The distinction between the two cases lies in storage of the result, not in 
argument evaluation. In the non-default case, the result is stored in a 
caller-provided object, while in the default case, the result is stored in a 
callee-provided object. This results in different behaviors (as the example 
makes clear); hence the two cases are not the same. 

This distinction is important to new users because it's necessary to think of 
them differently, and because (to me, at least) one of them is very 
non-intuitive. In both cases, the change made to the object is a side effect of 
the function. In the non-default case, this side effect is directly visible to 
the caller, but in the default case, it is only indirectly visible. 

Details like this are probably obvious to people who are very familiar with 
both call by object reference and to Python's persistent lifetime of default 
argument objects, but I don't think that group fits the target audience for a 
tutorial.

--

___
Python tracker 

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

[issue26844] Wrong error message during import

[Brett Cannon]

Changes by Brett Cannon :


--
assignee:  -> brett.cannon

___
Python tracker 

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

[issue19251] bitwise ops for bytes of equal length

[Guido van Rossum]

Guido van Rossum added the comment:

Can you point to some examples of existing code that would become more
readable and faster when this feature exists? Separately, how is it more
secure?

On Mon, Apr 25, 2016 at 9:17 AM, cowlicks  wrote:

>
> cowlicks added the comment:
>
> To reiterate, this issue would make more readable, secure, and speed up a
> lot of code.
>
> The concerns about this being a numpy-like vector operation are confusing
> to me. The current implementation is already vector-like, but lacks size
> checking. Isn't "int ^ int" really just the xor of two arbitrarily long
> arrays of binary data? At least with "bytes ^ bytes" we can enforce the
> arrays be the same size.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue19251] bitwise ops for bytes of equal length

[STINNER Victor]

STINNER Victor added the comment:

> I like to add the bitwise protocol between byte objects of equal length

Would it make sense to add such operators in a new module like the existing 
(but deprecated) audioop module?

If yes, maybe we should start with a module on PyPI. Is there a volunteer to 
try this option?

--

___
Python tracker 

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

[issue26804] Prioritize lowercase proxy variables in urllib.request

[Senthil Kumaran]

Senthil Kumaran added the comment:

This is fixed in all versions of Python.

Thank you for your contribution, Hans-Peter Jansen.

--
resolution:  -> fixed
stage: commit review -> 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

[issue26804] Prioritize lowercase proxy variables in urllib.request

[Roundup Robot]

Roundup Robot added the comment:

New changeset c502deb19cb0 by Senthil Kumaran in branch '2.7':
backport fix for Issue #26804.
https://hg.python.org/cpython/rev/c502deb19cb0

--

___
Python tracker 

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

[issue19251] bitwise ops for bytes of equal length

[cowlicks]

cowlicks added the comment:

To reiterate, this issue would make more readable, secure, and speed up a lot 
of code.

The concerns about this being a numpy-like vector operation are confusing to 
me. The current implementation is already vector-like, but lacks size checking. 
Isn't "int ^ int" really just the xor of two arbitrarily long arrays of binary 
data? At least with "bytes ^ bytes" we can enforce the arrays be the same size.

--

___
Python tracker 

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

[issue26807] mock_open()().readline() fails at EOF

[Robert Collins]

Robert Collins added the comment:

You're changing _mock_call but readline is actually implemented in 
_readline_side_effect - just changing that should be all thats needed (to deal 
with StopIteration). You will however need to fixup the return values since the 
test I added is a bit wider than just the single defect you uncovered.

--

___
Python tracker 

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

[issue26807] mock_open()().readline() fails at EOF

[Yolanda]

Yolanda added the comment:

So... the failures are because i'm capturing the StopIteration exception in 
that case. then it's normal that it's not raised. How should you solve that 
problem instead?

--

___
Python tracker 

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

[issue26807] mock_open()().readline() fails at EOF

[Robert Collins]

Robert Collins added the comment:

Thanks Yolanda. I've touched up the test a little and run a full test run (make 
test) - sadly it fails: there is an explicit test that StopIteration gets 
raised if you set it as a side effect.


==
FAIL: test_mock_open_after_eof (unittest.test.testmock.testmock.MockTest)
--
Traceback (most recent call last):
  File "/home/robertc/work/cpython-3.5.hg/Lib/unittest/test/testmock/test   
   mock.py", line 1428, in test_mock_open_after_eof
self.assertEqual('', h.readline())
AssertionError: '' != None

==
FAIL: test_side_effect_iterator (unittest.test.testmock.testmock.MockTest   
   )
--
Traceback (most recent call last):
  File "/home/robertc/work/cpython-3.5.hg/Lib/unittest/test/testmock/test   
   mock.py", line 980, in test_side_effect_iterator
self.assertRaises(StopIteration, mock)
AssertionError: StopIteration not raised by 

==
FAIL: test_side_effect_setting_iterator (unittest.test.testmock.testmock.   
   MockTest)
--
Traceback (most recent call last):
  File "/home/robertc/work/cpython-3.5.hg/Lib/unittest/test/testmock/test   
   mock.py", line 1015, in 
test_side_effect_setting_iterator
self.assertRaises(StopIteration, mock)
AssertionError: StopIteration not raised by 

--
Ran 705 tests in 1.251s

FAILED (failures=3, skipped=3)

Of those, I think the first failure is a bug in the patch; the second and third 
are genuine failures - you'll need to make your change in mock_open itself, not 
in 'mock'.

I've attached an updated patch which has ACKS, NEWS filled out and tweaked your 
test to be more comprehensive.

--
keywords: +patch
Added file: http://bugs.python.org/file42590/issue26807.diff

___
Python tracker 

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

[issue26804] Prioritize lowercase proxy variables in urllib.request

[Roundup Robot]

Roundup Robot added the comment:

New changeset 49b975122022 by Senthil Kumaran in branch '3.5':
Issue #26804: urllib.request will prefer lower_case proxy environment variables
https://hg.python.org/cpython/rev/49b975122022

New changeset 316593f5bf73 by Senthil Kumaran in branch 'default':
merge 3.5
https://hg.python.org/cpython/rev/316593f5bf73

--
nosy: +python-dev

___
Python tracker 

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

[issue25788] fileinput.hook_encoded has no way to pass arguments to codecs

[Joseph Hackman]

Joseph Hackman added the comment:

Ping.

Just wondering if anyone on the nosy list would be willing to help review my 
patch. :)

--

___
Python tracker 

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

[issue26154] Add private _PyThreadState_UncheckedGet() to get the current thread state

[Wenzel Jakob]

Wenzel Jakob added the comment:

I've also run into this regression. FWIW this is what I've ended up using to 
work around it (it's a mess, but what are we to do..)

#if PY_VERSION_HEX >= 0x0305 && PY_VERSION_HEX < 0x03050200
extern "C" {
/* Manually import _PyThreadState_Current symbol */
struct _Py_atomic_address { void *value; };
PyAPI_DATA(_Py_atomic_address) _PyThreadState_Current;
};
#endif

PyThreadState *get_thread_state_unchecked() {
#if   PY_VERSION_HEX < 0x0300
return _PyThreadState_Current;
#elif PY_VERSION_HEX < 0x0305
return (PyThreadState*) _Py_atomic_load_relaxed(&_PyThreadState_Current);
#elif PY_VERSION_HEX < 0x03050200
return (PyThreadState*) _PyThreadState_Current.value;
#else
return _PyThreadState_UncheckedGet();
#endif
}

--
nosy: +wenzel

___
Python tracker 

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

[issue26807] mock_open()().readline() fails at EOF

[Yolanda]

Yolanda added the comment:

diff --git a/Lib/unittest/test/testmock/testwith.py 
b/Lib/unittest/test/testmock/testwith.py
index a7bee73..efe6391 100644
--- a/Lib/unittest/test/testmock/testwith.py
+++ b/Lib/unittest/test/testmock/testwith.py
@@ -297,5 +297,16 @@ class TestMockOpen(unittest.TestCase):
 self.assertEqual(handle.readline(), 'bar')
 
 
+def test_readlines_after_eof(self):
+# Check that readlines does not fail after the end of file
+mock = mock_open(read_data='foo')
+with patch('%s.open' % __name__, mock, create=True):
+h = open('bar')
+h.read()
+h.read()
+data = h.readlines()
+self.assertEqual(data, [])
+
+
 if __name__ == '__main__':
 unittest.main()

--

___
Python tracker 

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

[issue23496] Steps for Android Native Build of Python 3.4.2

[Eric Snow]

Eric Snow added the comment:

FYI: https://mail.python.org/pipermail/python-dev/2016-April/144320.html

--
nosy: +eric.snow

___
Python tracker 

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

[issue26804] Prioritize lowercase proxy variables in urllib.request

[Martin Panter]

Martin Panter added the comment:

V7 looks good to me

--
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

[issue26249] Change PyMem_Malloc to use pymalloc allocator

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

68b2a43d8653 introduced memory leak.

$ ./python -m test.regrtest -uall -R : test_format
Run tests sequentially
0:00:00 [1/1] test_format
beginning 9 repetitions
123456789
.
test_format leaked [6, 7, 7, 7] memory blocks, sum=27
1 test failed:
test_format
Total duration: 0:00:01

--
status: closed -> open

___
Python tracker 

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

[issue26739] idle: Errno 10035 a non-blocking socket operation could not be completed immediately

[Kristján Valur Jónsson]

Kristján Valur Jónsson added the comment:

I think that the select.select calls there are a red herring, since I see no 
evidence that the rpc socket is ever put in non-blocking mode.
But the line
self.rpcclt.listening_sock.settimeout(10)
indicates that the socket is in timeout mode, and so, the error could be 
expected if it weren't for the backported fix for issue #9090

I'll have another look at that code and see if thera are any loopholes.

Also, Micahel could try commenting out this line in 
C:\Python27\Lib\idlelib\PyShell.py:
 self.rpcclt.listening_sock.settimeout(10)

and see if the problem goes away.

--

___
Python tracker 

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

[issue991266] Cookie.py does not correctly quote Morsels

[Berker Peksag]

Berker Peksag added the comment:

Here is a patch for Python 3.

--
nosy: +berker.peksag
versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2
Added file: http://bugs.python.org/file42589/issue991266.diff

___
Python tracker 

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

[issue7504] Same name cookies

[Berker Peksag]

Changes by Berker Peksag :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Improper handling of duplicate cookies

___
Python tracker 

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

[issue23662] Cookie.domain is undocumented

[Berker Peksag]

Berker Peksag added the comment:

Actually, it's already documented at 
https://docs.python.org/3.5/library/http.cookies.html#http.cookies.Morsel. I 
just added a note about the default value of domain.

--
nosy: +berker.peksag
resolution:  -> fixed
stage: needs patch -> 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

[issue23662] Cookie.domain is undocumented

[Roundup Robot]

Roundup Robot added the comment:

New changeset 1fdaa71d47f5 by Berker Peksag in branch '3.5':
Issue #23662: Document default value of RFC 2109 attributes
https://hg.python.org/cpython/rev/1fdaa71d47f5

New changeset b3ad9c002bb8 by Berker Peksag in branch 'default':
Issue #23662: Document default value of RFC 2109 attributes
https://hg.python.org/cpython/rev/b3ad9c002bb8

--
nosy: +python-dev

___
Python tracker 

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

[issue9456] Apparent memory leak in PC/bdist_wininst/install.c

[Mark Lawrence]

Changes by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

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

[issue26039] More flexibility in zipfile write interface

[Thomas Kluyver]

Thomas Kluyver added the comment:

It wasn't as bad as I thought (hopefully that doesn't mean I've missed 
something). zipfile-open-w6.patch allows interleaved reads and writes so long 
as the underlying file object is seekable.

You still can't have multiple write handles open (it wouldn't know where to 
start the second file), or read & write handles on a non-seekable stream (I 
don't think a non-seekable read-write file ever makes sense, except perhaps for 
a pty, which is really two separate streams on one file descriptor).

Tests are passing again.

--
Added file: http://bugs.python.org/file42588/zipfile-open-w6.patch

___
Python tracker 

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

[issue9456] Apparent memory leak in PC/bdist_wininst/install.c

[Berker Peksag]

Berker Peksag added the comment:

install_c.diff looks good to me. Attaching a fresh version of it. There is a 
comment in PC/bdist_wininst/install.c saying

IMPORTANT NOTE: IF THIS FILE IS CHANGED, PCBUILD\BDIST_WININST.VCXPROJ MUST 
BE REBUILT AS WELL.

I don't have Windows so I can't build VS project files myself. I'm adding Steve 
and Zachary to review/commit the patch (if they have time to take a look at it).

--
nosy: +berker.peksag, steve.dower, zach.ware
stage:  -> patch review
type:  -> behavior
versions: +Python 3.6 -Python 3.4
Added file: http://bugs.python.org/file42587/issue9456.diff

___
Python tracker 

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

[issue26826] Expose new copy_file_range() syscal in os module and use it to improve shutils.copy()

[STINNER Victor]

STINNER Victor added the comment:

If we add a new private function to the os module (ex:
os._copy_file_range), it can be used in shutil if available. But it
would be a temporary solution until we declare the API stable. Maybe
it's ok to add the API as public today.

--

___
Python tracker 

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

[issue26826] Expose new copy_file_range() syscal in os module and use it to improve shutils.copy()

[Marcos Dione]

Marcos Dione added the comment:

Then I don't know. My only worry is whether having the method local to os would 
allow shutils.copy() to use it or not.

I will start by looking at other similar functions there to see to do it. 
urandom() looks like a good starting point.

--

___
Python tracker 

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

[issue26804] Prioritize lowercase proxy variables in urllib.request

[Hans-Peter Jansen]

Hans-Peter Jansen added the comment:

v7:
 - reorder test code in order to improve edibility

--
Added file: 
http://bugs.python.org/file42586/python-urllib-prefer-lowercase-proxies-v7.diff

___
Python tracker 

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

[issue9998] ctypes find_library should search LD_LIBRARY_PATH on linux

[Pau Tallada]

Pau Tallada added the comment:

> Pau: What is wrong with the more direct CDLL("libspatialindex_c.so") proposal 
> that bypasses find_library()?

I don't know much about library loading, but from what I understand at 
https://github.com/Toblerity/rtree/issues/56 , if they hardcode 
"libspatialindex_c.so" in CDLL call, then it breaks in OSX, because its uses 
.dylib extension. And they don't want to reimplement find_library to choose the 
right extension for each platform.

--

___
Python tracker 

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

[issue26842] Python Tutorial 4.7.1: Need to explain default parameter lifetime

[Raymond Hettinger]

Raymond Hettinger added the comment:

> I hope this is useful. I realize it is much longer than the original.

There lies the difficultly.  The purpose of the tutorial is to quickly 
introduce the language, not to take someone deeply down a rabbit hole.  The 
docs tend to be worded in an affirmative manner showing cases of the language 
being used properly, giving a brief warning where necessary.  Further 
explorations should be left as FAQs.  

I think we could add a FAQ link or somesuch to the existing warning but the 
main flow shouldn't be interrupted (many on the topics in the tutorial could 
warrant entire blog posts and scores of StackOverflow entries, but the tutorial 
itself aspires to be a "short and sweet" quick tour around the language.  

The utility and approachability of the tutorial would be undermined by 
overexpanding each new topic.  This is especially important in the early 
sections of the tutorial (i.e. section 4).  

Also, I don't really like the provided explanation, "there are two cases ...".  
The actual execution model has one case (default arguments are evaluated once 
when the function is defined) and there are many ways to use it.

Lastly, this is only one facet of parameter specification and parameter 
passing.  Other facets include, variable length argument lists, keyword-only 
arguments, annotations, etc.   Any expanded coverage should occur later in the 
tutorial and cover all the facets collectively.

--
nosy: +rhettinger
priority: normal -> low

___
Python tracker 

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

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

[Xavier de Gaye]

Xavier de Gaye added the comment:

This error:
_curses.error: setupterm: could not find terminfo database

does not occur for me after removing the '--disable-database 
--disable-home-terminfo' options from the configure options used to 
cross-compile ncurses, and after setting the TERMINFO environment variable to a 
location where the the compiled description of the vt100 terminal is set. See 
https://bitbucket.org/xdegaye/pyona.

Also, with API level 21 (Android 5.0), the build of python3 with the official 
android toolchains (that is, without resorting to external libraries for wide 
character support) runs correctly and the python test suite is run with few 
errors, so IMHO this issue may be closed.

--
nosy: +xdegaye

___
Python tracker 

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

[issue26843] tokenize does not include Other_ID_Start or Other_ID_Continue in identifier

[Joshua Landau]

Joshua Landau added the comment:

Sorry, I'd stumbled on my old comment on the closed issue and completely forgot 
about the *last* time I did the same thing.

--

___
Python tracker 

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

[issue22747] Interpreter fails in initialize on systems where HAVE_LANGINFO_H is undefined

[Xavier de Gaye]

Xavier de Gaye added the comment:

Android default system encoding is UTF-8 as specified at 
http://developer.android.com/reference/java/nio/charset/Charset.html

The platform's default charset is UTF-8. (This is in contrast to some 
older implementations, where the default charset depended on the user's 
locale.) 

> If the platform doesn't provide anything, we can maybe adopt the same
> approach than Mac OS X: force the encoding to UTF-8 and just don't use
> the C library.

The attached patch does the same thing as proposed by Victor but emphasizes 
that Android does not HAVE_LANGINFO_H and does not have CODESET.  And the fact 
that HAVE_LANGINFO_H and CODESET are not defined causes other problems (maybe 
as well in Mac OS X). In that case, PyCursesWindow_New() in _cursesmodule.c 
falls back nicely to "utf-8", but _Py_device_encoding() in fileutils.c instead 
does a Py_RETURN_NONE. It seems that this impacts 
_io_TextIOWrapper___init___impl() in textio.c and os_device_encoding_impl() in 
posixmodule.c. And indeed, os.device_encoding(0) returns None on android.

--
nosy: +xdegaye
Added file: http://bugs.python.org/file42585/locale.patch

___
Python tracker 

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

[issue17905] Add check for locale.h

[Xavier de Gaye]

Xavier de Gaye added the comment:

Android API level 21 has a full fledged locale.h now.
There is still no langinfo.h, this issue is a duplicate of issue #22747.

--
nosy: +xdegaye

___
Python tracker 

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

[issue23662] Cookie.domain is undocumented

[Berker Peksag]

Changes by Berker Peksag :


--
keywords: +easy
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.6 -Python 3.2, Python 3.3, Python 3.4

___
Python tracker 

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

[issue26844] Wrong error message during import

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

LGTM.

But while we are here, it would be nice to replace type(path) with 
type(path).__name__ (and the same for type(name)).

--
nosy: +eric.snow, ncoghlan, serhiy.storchaka
stage: patch review -> commit review
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

[issue26844] Wrong error message during import

[SilentGhost]

Changes by SilentGhost :


--
nosy: +brett.cannon
priority: normal -> low
stage:  -> patch review
versions:  -Python 3.2, Python 3.3, Python 3.4

___
Python tracker 

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

[issue26844] Wrong error message during import

[Lev Maximov]

New submission from Lev Maximov:

Error message was supposedly copy-pasted without change.
Makes it pretty unintuinive to debug.
Fix attached.

--
components: Library (Lib)
files: error.diff
keywords: patch
messages: 264157
nosy: Lev Maximov
priority: normal
severity: normal
status: open
title: Wrong error message during import
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file42584/error.diff

___
Python tracker 

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

[issue24194] tokenize yield an ERRORTOKEN if an identifier uses Other_ID_Start or Other_ID_Continue

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
dependencies: +Request for property support in Python re lib, python lib re 
uses obsolete sense of \w in full violation of UTS#18 RL1.2a

___
Python tracker 

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

[issue24194] tokenize yield an ERRORTOKEN if an identifier uses Other_ID_Start or Other_ID_Continue

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
stage:  -> needs patch
versions: +Python 3.5, Python 3.6 -Python 3.4

___
Python tracker 

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

[issue26843] tokenize does not include Other_ID_Start or Other_ID_Continue in identifier

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

This is a duplicate of issue24194. Yes, there is no progress still.

--
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> tokenize yield an ERRORTOKEN if an identifier uses 
Other_ID_Start or Other_ID_Continue

___
Python tracker 

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

[issue26837] assertSequenceEqual() raises BytesWarning when format message

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you for your helpful review Martin!

--
assignee:  -> serhiy.storchaka
resolution:  -> fixed
stage: patch review -> 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

[issue26837] assertSequenceEqual() raises BytesWarning when format message

[Roundup Robot]

Roundup Robot added the comment:

New changeset ae5cc8ab664a by Serhiy Storchaka in branch '3.5':
Issue #26837: assertSequenceEqual() now correctly outputs non-stringified
https://hg.python.org/cpython/rev/ae5cc8ab664a

New changeset d0d541c2afb7 by Serhiy Storchaka in branch '2.7':
Issue #26837: assertSequenceEqual() now correctly outputs non-stringified
https://hg.python.org/cpython/rev/d0d541c2afb7

--
nosy: +python-dev

___
Python tracker 

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