[issue29551] unittest: TestSuite.debug() does not like subTest()

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +ezio.melotti, michael.foord, pitrou, rbcollins
type: crash -> behavior
versions: +Python 3.6, Python 3.7

___
Python tracker 

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

[issue29540] Add compact=True flag to json.dump/dumps

[Raymond Hettinger]

Raymond Hettinger added the comment:

I concur with Serhiy and think this API change would be a net increase in 
complexity.

FWIW, network transmission size issues can already be handled more effectively 
"Accept-Encoding: gzip, deflate".

Bob, do you have any thoughts?

--
assignee:  -> bob.ippolito
nosy: +bob.ippolito, rhettinger

___
Python tracker 

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

[issue29551] unittest: TestSuite.debug() does not like subTest()

[Wolfgang Rohdewald]

New submission from Wolfgang Rohdewald:

the main code is appended in main.py

if a test uses with self.subTest(), subTest() fails right in its first 
statement "if not self._outcome ..." because _outcome is None.

In main.py, the commented runner.run(suite) would work correctly.

If this is not meant to work, please mention it in the documentation and  
improve unittest's reaction.

what I would find more logical from the users's point of view is something like

runner.debug(suite)

--
components: Library (Lib)
files: main.py
messages: 287738
nosy: wrohdewald
priority: normal
severity: normal
status: open
title: unittest: TestSuite.debug() does not like subTest()
type: crash
versions: Python 3.5
Added file: http://bugs.python.org/file46637/main.py

___
Python tracker 

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

[issue29339] Interactive: Move to same indentation level as previousline

[Matthias Bussonnier]

Matthias Bussonnier added the comment:

> IPython3 solved this issue by adding special magic functions, but this is not 
> a way for CPython.

IPython 5 improve on that with prompt toolkit. It does not break paste, as 
prompt_toolkit has a bracketed-past mode, that most terminal emulator support  
(control chars sent by terminal "hey I'm pasting", "hey I'm done pasting"). So 
it works nicely. IPython 6 even will remove the need for magics to activate 
paste mode.

Though it's far from trivial to implement and to get it "right".

Once you start giving indentation to user, they start to be demanding, like 
indenting 1 more on `:`, and one less on `return`, `pass`... , multiple line 
string. etc...

See https://github.com/ipython/ipython/issues/9283 for some of the issues and 
limitation you can hit.

If you decide to implement this kind of things, there are likely a lot you can 
borrow from IPython, the InputSplitter class has likely the sate needed to give 
you the indent level to use in readline.

--
nosy: +mbussonn

___
Python tracker 

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

[issue24665] CJK support for textwrap

[Florent Gallaire]

Florent Gallaire added the comment:

After discussion with Haypo, CJK support is now implemented as and option, 
disabled by default for backward compatibility reasons.

PR on GitHub:
https://github.com/python/cpython/pull/89

--
pull_requests: +56

___
Python tracker 

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

[issue6143] IDLE - an extension to clear the shell window

[Alex]

Alex added the comment:

The ClearWindow.py extension works well with the specified shortcut, How can i 
invoke it in my source code to clear the window ? Thanks in advance.

--
nosy: +Alex
type: enhancement -> resource usage
versions: +Python 2.7 -Python 3.6

___
Python tracker 

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

[issue29548] deprecate PyEval_Call*() functions.

[INADA Naoki]

INADA Naoki added the comment:

PR 87 fixes the regression in 3.6 branch

--
pull_requests: +55

___
Python tracker 

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

[issue29438] use after free in key sharing dict

[INADA Naoki]

INADA Naoki added the comment:

All pull requests are merged.
https://github.com/python/cpython/pull/17 (master)
https://github.com/python/cpython/pull/39 (3.6)
https://github.com/python/cpython/pull/40 (3.5)

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

[issue29548] deprecate PyEval_Call*() functions.

[INADA Naoki]

Changes by INADA Naoki :


--
nosy: +haypo

___
Python tracker 

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

[issue29548] deprecate PyEval_Call*() functions.

[INADA Naoki]

INADA Naoki added the comment:

Thanks, Lemburg to pointing it out.
Here is detail of the difference.

## PyEval_CallFunction(), PyEval_CallMethod()

They are very similar to PyObject_CallFunction() and PyObject_CallMethod().  
difference are:

* PyEval_Call...() doesn't respect Py_SSIZE_T_CLEAN
* PyObject_Call... has following special case.  PyEval_CallFunction(callable, 
"i", (int)i) will raise TypeError("keyword list must be a tuple") and 
PyObject_CallFunction(callable, "i", (int)i) calls `callable(i)`

if (nargs == 1 && PyTuple_Check(stack[0])) {
/* Special cases for backward compatibility:
   - PyObject_CallFunction(func, "O", tuple) calls func(*tuple)
   - PyObject_CallFunction(func, "(OOO)", arg1, arg2, arg3) calls
 func(*(arg1, arg2, arg3)): func(arg1, arg2, arg3) */
PyObject *args = stack[0];
result = _PyObject_FastCall(callable,
_GET_ITEM(args, 0),
PyTuple_GET_SIZE(args));
}

PyEval_CallFunction is not called from Python source tree.
PyEval_CallMethod has only one caller in tree and format string is "(Oi)".  It 
can be replaced with PyObject_CallMethod safely.


## PyEval_CallObject(), PyEval_CallObjectWithKeywords()

PyEval_CallObject() is a just macro calling PyEval_CallObjectWithKeywords() 
(call it COWK later).
PyEval_CallObject() is identical to PyObject_CallObject().  Only difference is 
it's a macro or function.

COWK is similar to PyObject_Call(), but COWK raise TypeError when args is not a 
tuple or kwds is not a dictionary and PyObject_Call() uses assert.

There are only two caller of PyEval_CallObjectWithKeywords() other than 
PyEval_CallObject and PyObject_CallObject.
One is tp_call of weakcallableproxy.  Type of kwargs is checked before calling 
tp_call.
Another is in threading (boot->keyw).  The threading module checks it's a dict.
So replacing them to PyObject_CallObject() is safe.



While they are complex API, there are few (or no) callers in Python tree.
It's too hard to maintain.  Actually, I found regression of COWK in Python 3.6.

https://github.com/python/cpython/commit/155ea65e5c88d250a752ee5321860ef11ede4085

It calls _PyObject_FastCallDict() when args is NULL.  If kwargs is not dict, it 
can crash instead of raising TypeError.

--

___
Python tracker 

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

[issue24241] webbrowser default browser detection and/or public API for _trylist.

[David Steele]

David Steele added the comment:

See https://github.com/python/cpython/pull/85

--

___
Python tracker 

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

[issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque

[Raymond Hettinger]

Raymond Hettinger added the comment:

Yes, we should put versionadded in the docs to augment the MISC/NEWS entries.

Mariatta, do you want to take a crack at the patch?  It should hit both 3.5 and 
3.6 docs.

--
nosy: +Mariatta

___
Python tracker 

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

[issue11339] annotation for class being defined

[Ivan Levkivskyi]

Changes by Ivan Levkivskyi :


--
nosy: +levkivskyi

___
Python tracker 

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

[issue28941] Update the link to Source Code in Python Docs from hg to github

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

This was addressed in the very first pull request on CPython GitHub (Thanks, 
Brett ) 

Backported to 2.7, 3.5, and 3.6

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

[issue26752] Mock(2.0.0).assert_has_calls() raise AssertionError in two same calls

[John W.]

John W. added the comment:

This also seems to apply to unittest.mock in Python3.4.

I described my similar issue on SO: 
http://stackoverflow.com/questions/42212433/what-is-wrong-with-this-simple-py-test-use-case

It seems like it may be the same issue described here.

For reference, this is my repro case:

from unittest.mock import patch, call

class Foo:
def __init__(self):
pass
def my_method(self, value):
pass

def test_foo():
with patch('test.Foo', autospec=True) as MockFoo:
m = MockFoo()
m.my_method(123)
MockFoo.assert_has_calls([call(), call().my_method(123)])

It fails with:

...
E   AssertionError: Calls not found.
E   Expected: [call(), call().my_method(123)]
E   Actual:   [call(), call().my_method(123)]

Which seems nonsensical to me.

Removing the `value` parameter and the `123` arguments in the test makes it 
pass(!)

--
nosy: +jwdevel
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

[issue29550] Mac build-installer touch step fails after github conversion

[Ned Deily]

Ned Deily added the comment:

Thanks, I'll take a look.

--
assignee:  -> ned.deily
nosy: +larry
priority: normal -> release blocker

___
Python tracker 

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

[issue29550] Mac build-installer touch step fails after github conversion

[David Bolen]

New submission from David Bolen:

The "make touch" step during the Mac installer builds on the bolen-dmg build 
slave no longer works after the conversion to github, which breaks the daily 
builds on the 3.* branches.

It looks like in issue 23404 Zachary disabled the touch step for the buildbots 
for now to avoid the issue in general builds, so perhaps the same thing should 
be done in build-installer pending a more general replacement of that step.

--
components: Build
messages: 287726
nosy: db3l, ned.deily, zach.ware
priority: normal
severity: normal
status: open
title: Mac build-installer touch step fails after github conversion
type: compile error
versions: Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue27593] Deprecate sys._mercurial and create sys._git

[Ned Deily]

Ned Deily added the comment:

Yeah, I'll get to the non-Windows parts shortly.  I'd been waiting for the 
transition to happen.

--

___
Python tracker 

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

[issue29549] Improve docstring for str.index

[Raymond Hettinger]

New submission from Raymond Hettinger:

The docstring for str.index() needs to be synced with the main documentation 
rather than presuming knowledge of str.find().

Currently it reads:

>>> help(str.index)
Help on method_descriptor:

index(...)
S.index(sub[, start[, end]]) -> int

Like S.find() but raise ValueError when the substring is not found.

And it should read more like str.find:

help(str.find)
Help on method_descriptor:

find(...)
S.find(sub[, start[, end]]) -> int

Return the lowest index in S where substring sub is found,
such that sub is contained within S[start:end].  Optional
arguments start and end are interpreted as in slice notation.

Return -1 on failure.

Lisa, it would be great if you could draft-up a patch.

--
assignee: lisroach
components: Documentation
messages: 287724
nosy: lisroach, rhettinger
priority: normal
severity: normal
stage: needs patch
status: open
title: Improve docstring for str.index
versions: Python 2.7, Python 3.6, Python 3.7

___
Python tracker 

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

[issue29403] mock's autospec's behavior on method-bound builtin functions is broken

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +berker.peksag, michael.foord
stage:  -> patch review
versions:  -Python 2.7, 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

[issue29541] Python3 error while building on Alt-F

[Honza Skýpala]

Honza Skýpala added the comment:

1. What's the result of ```./python -E```?

Python 3.6.0 (default, Feb 13 2017, 08:16:44)
[GCC 4.5.4 20120202 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.

2. Does `import crypt` run fine in ./python?

No, gives the error
./python: can't resolve symbol 'crypt'

3. Are there pre-installed Python on Alt-F? Uninstall them first may help

No, there is no python preinstalled (no python3, not even python2)

4. Is there a symbol called crypt in `nm ./python`?

No, `nm ./python | grep crypt` gives no results

--

___
Python tracker 

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

[issue29544] Allow login to bugs.python.org with Google account

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report. Feature requests about bugs.python.org should be 
reported to http://psf.upfronthosting.co.za/roundup/meta/

--
nosy: +berker.peksag
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

[issue29543] Allow login to bugs.python.org with email address

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report. Feature requests about bugs.python.org should be 
reported to http://psf.upfronthosting.co.za/roundup/meta/

--
nosy: +berker.peksag
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

[issue26213] Document BUILD_*_UNPACK opcodes

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +berker.peksag

___
Python tracker 

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

[issue29520] Documentation uses deprecated "defindex.html" Sphinx template

[Berker Peksag]

Changes by Berker Peksag :


--
stage:  -> needs patch
type: compile error -> enhancement
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

[issue29547] Add c code coverage to codecov

[Brett Cannon]

Brett Cannon added the comment:

I have https://github.com/python/core-workflow/issues/2 sitting open for this 
specific idea. :) If Codecov will do the appropriate merging between 
coverage.py and lcov then I think it's worth a PR to set it up.

--
nosy: +brett.cannon

___
Python tracker 

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

[issue29546] A more helpful ImportError message

[Brett Cannon]

Changes by Brett Cannon :


--
type:  -> enhancement

___
Python tracker 

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

[issue29546] A more helpful ImportError message

[Brett Cannon]

Brett Cannon added the comment:

So 'path' already exists on ImportError so tweaking the message when the path 
is known wouldn't be difficult 
(https://docs.python.org/3/library/exceptions.html?highlight=importerror#ImportError).

--
nosy: +brett.cannon

___
Python tracker 

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

[issue29518] 'for' loop not automatically breaking (index error on line of loop header)

[Brett Cannon]

Brett Cannon added the comment:

Since Justin can't provide the original email, it could have been his setup, 
and the chances that range() is broken on Python 2.7 is extremely small, I'm 
closing this as not a bug.

--
nosy: +brett.cannon
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

[issue29540] Add compact=True flag to json.dump/dumps

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I'm -1. This adds the maintenance and learning burden and doesn't make the user 
code more clear. The reader needs to search what json.COMPACT means.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue29548] deprecate PyEval_Call*() functions.

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

Please note that the two sets of APIs are not identical, e.g. you cannot simply 
replace PyEval_CallObject() with PyObject_Call(), since the former applies a 
few extra checks and defaults, which the latter doesn't.

--
nosy: +lemburg

___
Python tracker 

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

[issue27593] Deprecate sys._mercurial and create sys._git

[Steve Dower]

Steve Dower added the comment:

This is now blocking all releases for all versions.

I'll try and make some time to update the Windows build scripts and project 
files, but if someone else gets there first feel free to post a PR.

--
nosy: +benjamin.peterson, larry, steve.dower
priority: deferred blocker -> release blocker
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

[issue29548] deprecate PyEval_Call*() functions.

[INADA Naoki]

Changes by INADA Naoki :


--
pull_requests: +54

___
Python tracker 

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

[issue29548] deprecate PyEval_Call*() functions.

[INADA Naoki]

New submission from INADA Naoki:

As reading call.c, PyEval_Call* APIs are mostly duplicate of PyObject_Call* 
APIs.

While they are not documented, they seems part of limited APIs.
So we can't remove them easily.  Let's deprecate them for now.

--
components: Interpreter Core
messages: 287714
nosy: inada.naoki
priority: normal
severity: normal
status: open
title: deprecate PyEval_Call*() functions.
versions: Python 3.7

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Eric Snow]

Eric Snow added the comment:

> These files *do not* belong to the CPython package, they belong to the
> individual Python modules that depend on CPython, so messing with them
> when installing a new version of CPython would be a significant breach
> of distro policies.

Thanks for clarifying, Nick.  This was the piece I'd missed.

--

___
Python tracker 

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

[issue19675] Pool dies with excessive workers, but does not cleanup

[Davin Potts]

Davin Potts added the comment:

For triggering the exception, supplying a Process target that deliberately 
fails sounds right.

As for tests for the various start methods (fork/forkserver/spawn), if you are 
looking at the 3.x branches you'll find this was been consolidated so that one 
test could conceivably be written to handle multiple variants (see 
Lib/test/_test_multiprocessing.py).

--

___
Python tracker 

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

[issue19675] Pool dies with excessive workers, but does not cleanup

[Dustin Oprea]

Dustin Oprea added the comment:

Okay. Thanks for weighing-in.

I'm trying to figure out how to write the tests. The existing set of tests
for multiprocessing is a near nightmare. It seems like I might have to use
one of the existing "source code" definitions to test for the no-cleanup
(traditional) scenario but then have to define a new one to define the pool
with an initializer that fails. However, then, I'll have to define three
new TestCase-based classes to test for the various start-methods.

Any suggestions?

On Mon, Feb 13, 2017 at 11:50 AM, Davin Potts 
wrote:

>
> Changes by Davin Potts :
>
>
> --
> versions: +Python 2.7, Python 3.7
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue29547] Add c code coverage to codecov

[Alexander Belopolsky]

New submission from Alexander Belopolsky:

I had it done in my fork of cpython-mirror: 
https://github.com/abalkin/cpython/tree/ci

--
assignee: belopolsky
components: Tests
messages: 287710
nosy: belopolsky
priority: normal
severity: normal
status: open
title: Add c code coverage to codecov
versions: Python 3.7

___
Python tracker 

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

[issue19675] Pool dies with excessive workers, but does not cleanup

[Davin Potts]

Davin Potts added the comment:

@Winterflower: Thank you for encouraging @dsoprea to create the new PR and 
working to convert the previous patch.

@dsoprea: Thank you for taking the time to create the PR especially after this 
has been sitting unloved for so long.

Though the new workflow using PR's is still in a bit of a state of flux, my 
understanding is that we will want to have one PR per feature branch (i.e. one 
for each of 2.7, 3.6, 3.7) that we want to target.

Now that we seem to have spawned two parallel discussion tracks (one here and 
one in the PR https://github.com/python/cpython/pull/57), I'm not sure how best 
to resolve that but for the time being I'll offer code-related comments here as 
they're much more likely to be preserved (and thus discoverable) for posterity: 
 we do need some sort of tests around this to complete the patch -- something 
that would exercise both the non-exception and exception paths (and thus would 
detect that intended call to util.debug()).

--

___
Python tracker 

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

[issue19675] Pool dies with excessive workers, but does not cleanup

[Davin Potts]

Changes by Davin Potts :


--
versions: +Python 2.7, Python 3.7

___
Python tracker 

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

[issue29546] A more helpful ImportError message

[Barry A. Warsaw]

New submission from Barry A. Warsaw:

I haven't really thought about this deeply but I've observed that there are 
lots of cases where a user will report getting an ImportError trying to import 
a name from a module, where it turns out that the problem is that the module is 
coming from an unexpected location.  Examples include pip installed packages 
overriding system packages, or unexpected vendorized wheels.

The standard first response is typically, "can you please run this to tell us 
where the foo library is coming from?"  E.g.

```
^^ this is indicative of an old version of urllib3. Can you please double 
check whether you have an old urllib3 installed e.g. in /usr/local or ~/.

Testing:

$ python3 -c 'import urllib3; print(urllib3.__file__)'

should return:

/usr/lib/python3/dist-packages/urllib3/__init__.py

and might tell you where else a locally installed urllib3 is to be found if it 
doesn't return that value.
```

It would be kind of useful if the original ImportError showed you where the 
module came from (i.e. its __file__), if such information can be discerned.  
E.g.:

```
>>> import requests; requests.__version__.split('.')  
Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 
61, in 
 from .packages.urllib3.exceptions import DependencyWarning
ImportError: cannot import name DependencyWarning from 
requests.packages.urllib3.exceptions 
(/usr/local/lib/python3.5/site-packages/requests/packages/urllib3.py)
```

If you saw that in a bug report, you'd almost immediately know that the user 
has some local override that's potentially causing the problem.

--
components: Interpreter Core
messages: 287708
nosy: barry
priority: normal
severity: normal
status: open
title: A more helpful ImportError message
versions: Python 3.7

___
Python tracker 

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

[issue29545] Python behavioral difference between Linux and AIX

[Eric N. Vander Weele]

Changes by Eric N. Vander Weele :


--
nosy: +ericvw

___
Python tracker 

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

[issue29540] Add compact=True flag to json.dump/dumps

[Andrew Nester]

Andrew Nester added the comment:

I've just added PR implementing alternative version provided by R. David Murray 
as more simple and straight-forward one.

--
nosy: +andrewnester
pull_requests: +53

___
Python tracker 

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

[issue29545] Python behavioral difference between Linux and AIX

[Gireesh]

New submission from Gireesh:

Here is my python code (parent):

#!/usr/bin/env python
import errno
import os
import pty
from subprocess import Popen, STDOUT

master_fd, slave_fd = pty.openpty()
proc = Popen(['./a.out'],stdout=slave_fd, close_fds=True)
os.close(slave_fd)
data = os.read(master_fd, 512)
print('got ' + repr(data))

Child(C++):
#include 
#include 
#include 

int main()
{
printf("hello world\n");
exit(0);
}

behavior: 
Linux:
got 'hello world\r\r\n'
AIX: Hangs.

versions:
Linux:
Linux 2.6.32-131.12.1.el6.x86_64 #1 SMP Sun Jul 31 16:44:56 EDT 2011 
x86_64 x86_64 x86_64 GNU/Linux
AIX: 1 6 00F460A94C00
Python: 2.7.10

--
messages: 287706
nosy: gireeshpunathil
priority: normal
severity: normal
status: open
title: Python behavioral difference between Linux and AIX

___
Python tracker 

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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

You're right. argparse has indirect dependency on dynamic modules so it can't 
be used in setup.py. Cross builds use prebuilt Python binaries so there's no 
problem. Sorry for those noises.

I still think it's a dirty hack as it limits scalability and brings lots of 
problems when adding new features, but I can't find a good way to remove it :(

--

___
Python tracker 

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

[issue21056] csv documentation is incorrect

[Sanket Dasgupta]

Sanket Dasgupta added the comment:

Hi, I am looking to fix this bug.

So as per the discussion, should I remove the documentation of __next__() ?

--
nosy: +sanketdg

___
Python tracker 

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

[issue29538] bugs.python.org does not redirect to HTTPS

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

>From CPython's developer guide [1]:

"Issues about the tracker should be reported to the meta tracker."

> which doesn't support HTTPS at all

I don't know where I should go for issues about the meta tracker. Maybe a 
meta-meta tracker? :D

[1] http://cpython-devguide.readthedocs.io/tracker.html

--

___
Python tracker 

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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Stefan Krah]

Stefan Krah added the comment:

On Mon, Feb 13, 2017 at 03:04:09PM +, Chi Hsuan Yen wrote:
> 
> Chi Hsuan Yen added the comment:
> 
> I have used my old patch several days on Android, and it seems quite fine. 
> Anyway that's not important anymore.

I find that very surprising:

./python -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
echo "generate-posix-vars failed" ; \
rm -f ./pybuilddir.txt ; \
exit 1 ; \
fi
Traceback (most recent call last):
  File "./setup.py", line 4, in 
import sys, os, importlib.machinery, re, argparse
  File "/home/stefan/althome/pydev/commit-master-LATEST/Lib/argparse.py", line 
93, in 
from gettext import gettext as _, ngettext
  File "/home/stefan/althome/pydev/commit-master-LATEST/Lib/gettext.py", line 
49, in 
import locale, copy, io, os, re, struct, sys
  File "/home/stefan/althome/pydev/commit-master-LATEST/Lib/struct.py", line 
13, in 
from _struct import *
ModuleNotFoundError: No module named '_struct'

Yes, it is important, because you called the original a "dirty hack", which
some core devs do not appreciate.

--

___
Python tracker 

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

[issue29544] Allow login to bugs.python.org with Google account

[Paul Schreiber]

New submission from Paul Schreiber:

I created a standard account on bugs.python.org with username paulschreiber and 
email address paulschreiber at gmail.com.

Later, I attempted to log in to bugs.python.org using Google and was shown an 
error message:
There is already an account for paulschrei...@gmail.com

Instead of showing me the error message, I should have been logged in.

--
messages: 287701
nosy: paulschreiber
priority: normal
severity: normal
status: open
title: Allow login to bugs.python.org with Google account
type: enhancement

___
Python tracker 

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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

I have used my old patch several days on Android, and it seems quite fine. 
Anyway that's not important anymore.

--

___
Python tracker 

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

[issue29543] Allow login to bugs.python.org with email address

[Paul Schreiber]

New submission from Paul Schreiber:

Allow users to log in to bugs.python.org with the email address in the username 
field.

--
messages: 287699
nosy: paulschreiber
priority: normal
severity: normal
status: open
title: Allow login to bugs.python.org with email address
type: enhancement

___
Python tracker 

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

[issue29538] bugs.python.org does not redirect to HTTPS

[Paul Schreiber]

Paul Schreiber added the comment:

The issue you linked to:
http://psf.upfronthosting.co.za/roundup/meta/issue463

covers psf.upfronthosting.co.za (which doesn't support HTTPS at all) and not 
bugs.python.org (which supports, but does not enforce HTTPS).

--

___
Python tracker 

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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Stefan Krah]

Changes by Stefan Krah :


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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Stefan Krah]

Stefan Krah added the comment:

It's not a matter of *necessary*, you simply cannot use argparse in setup.py.  
Try to build with your patch and you'll see.

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Barry A. Warsaw]

Barry A. Warsaw added the comment:

On Feb 12, 2017, at 05:42 PM, Brett Cannon wrote:

>That comment is poorly worded.

Pretty sure at one time it was accurately worded, but things have changed
since PEP 3147 so the comment could use an update.

--

___
Python tracker 

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

[issue29521] Minor warning messages when compiling documentation

[STINNER Victor]

STINNER Victor added the comment:

The commit 3d707be950b387552585451071928e7b39cdfa53 broke the Docs buildbot 
slave. I proposed https://github.com/python/cpython/pull/68 to run the 
rstlint.py check on Travis as well, and to fix the 2 warnings.

http://buildbot.python.org/all/builders/Docs%203.x/builds/399/steps/lint/logs/stdio


python3 tools/rstlint.py -i tools -i venv
[1] faq/windows.rst:303: trailing whitespace
[1] faq/windows.rst:305: trailing whitespace
2 problems with severity 1 found.
Makefile:156: recipe for target 'check' failed

--
nosy: +haypo
pull_requests: +52

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Petr Viktorin]

Petr Viktorin added the comment:

In Fedora also want to stay close to upstream: every downstream patch is like 
an open issue, something we'd like to merge given enough time and people. But, 
for a problem that:
- is fixed in the latest version (3.6)
- is getting a test to not happen again
- only affects downstream distributions
I'm fine with a downstream patch.

I'd also be happy to work on making the patch acceptable upstream, but I need 
to hear some core devs' expectations on that. Where on the spectrum from 
throwaway hack to full-scale mechanism for accepting ranges of magic numbers 
should such a patch patch be?

--

___
Python tracker 

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

[issue29387] Tabs vs spaces FAQ out of date

[Brian Curtin]

Brian Curtin added the comment:


New changeset 3d707be950b387552585451071928e7b39cdfa53 by Brian Curtin in 
branch 'master':
bpo-29521 Fix two minor documentation build warnings (#41)
https://github.com/python/cpython/commit/3d707be950b387552585451071928e7b39cdfa53


--
nosy: +brian.curtin

___
Python tracker 

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

[issue29523] latest setuptools breaks virtualenvs due to unbundling dependencies

[Charalampos Stratakis]

Charalampos Stratakis added the comment:

Pull Request has been sent: https://github.com/python/cpython/pull/67

--

___
Python tracker 

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

[issue29442] Use argparse and drop dirty optparse hacks in setup.py

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

I've found a simpler patch set for supporting Android builds, so I don't need 
this patch anymore. If you don't think it's necessary, just close it.

> usage of os.system() in some places

I'm indeed sick with them :D

--

___
Python tracker 

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

[issue29541] Python3 error while building on Alt-F

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

That's super strange. crypt() is used in _crypt module only, and this modules 
is not used elsewhere in Python. A few more tests may help diagnostics

1. What's the result of ```./python -E```?
2. Does `import crypt` run fine in ./python?
3. Are there pre-installed Python on Alt-F? Uninstall them first may help
4. Is there a symbol called crypt in `nm ./python`?

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Andrew Nester]

Andrew Nester added the comment:

thanks for your notes, it's absolutely fine and I agree with you :)

--

___
Python tracker 

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

[issue29410] Moving to SipHash-1-3

[Christian Heimes]

Christian Heimes added the comment:

The old repos has a different name, https://github.com/tiran/cpython-mirror

I'm busy with work at the moment. I'll get to the patch later.

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Mark Dickinson]

Mark Dickinson added the comment:

[Andrew]

> it's better to fix it as other issue

No, it's better not to "fix" it at all. :-) It's one of those many behaviour 
changes where the answer to "Should we have done this differently in the first 
place" might possibly be "Yes" (and might also be "No"), but the answer to 
"Should we *change* it now" is a definite "No" (especially given that the 
"from_float" method is there almost entirely for backwards compatibility). I 
shouldn't have brought it up. Apologies.

--

___
Python tracker 

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

[issue29410] Moving to SipHash-1-3

[INADA Naoki]

INADA Naoki added the comment:

Christian Heimes: Could you create pull request?

https://github.com/tiran/cpython/tree/siphash13 is 404 now.

--

___
Python tracker 

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

[issue29540] Add compact=True flag to json.dump/dumps

[R. David Murray]

R. David Murray added the comment:

An alternative would be to define a COMPACT constant in the json module equal 
to (',', ':').

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

[issue29537] Alternative fix for BUILD_MAP_UNPACK_WITH_CALL opcode in 3.5

[Mark Dickinson]

Changes by Mark Dickinson :


--
nosy: +mark.dickinson

___
Python tracker 

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

[issue27286] str object got multiple values for keyword argument

[Iryna]

Changes by Iryna :


--
nosy: +ishcherb

___
Python tracker 

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

[issue29537] Alternative fix for BUILD_MAP_UNPACK_WITH_CALL opcode in 3.5

[Iryna]

Changes by Iryna :


--
nosy: +ishcherb

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Iryna]

Changes by Iryna :


--
nosy: +ishcherb

___
Python tracker 

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

[issue29525] Python 2.7.13 for Windows broken (from prompt)

[Frak N]

Frak N added the comment:

Excellent analysis guys! Thank you!

The -X faulthandler option didn't work.
The -S -v, however, did. 
Finally, renaming and deleting the readline entries fixed it such that I can 
now launch the REPL. 
Question. What does " disables the site module" for the -S option mean?

Now, what do I do about the (py)readline issue? Do I need to reinstall 
something?

Logs below:


c:\Python27>python
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit 
(Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

c:\Python27>python -X faulthandler -S -v
-X is reserved for implementation-specific arguments
usage: python [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.

c:\Python27>python -X
-X is reserved for implementation-specific arguments
usage: python [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.

c:\Python27>python -X -faulthandler -S -v
-X is reserved for implementation-specific arguments
usage: python [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.

c:\Python27>python  -S -v
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit 
(Intel)] on win32
>>> ^Z

# clear __builtin__._
# clear sys.path
# clear sys.argv
# clear sys.ps1
# clear sys.ps2
# clear sys.exitfunc
# clear sys.exc_type
# clear sys.exc_value
# clear sys.exc_traceback
# clear sys.last_type
# clear sys.last_value
# clear sys.last_traceback
# clear sys.path_hooks
# clear sys.path_importer_cache
# clear sys.meta_path
# clear sys.flags
# clear sys.float_info
# restore sys.stdin
# restore sys.stdout
# restore sys.stderr
# cleanup __main__
# cleanup[1] zipimport
# cleanup[1] signal
# cleanup[1] exceptions
# cleanup[1] _warnings
# cleanup sys
# cleanup __builtin__
# cleanup ints: 6 unfreed ints
# cleanup floats

c:\Python27>python
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit 
(Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

c:\Python27>ren C:\Python27\Lib\site-packages\readline.py readline.py.bak

c:\Python27>del C:\Python27\Lib\site-packages\readline.pyc

c:\Python27>python
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit 
(Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Andrew Nester]

Andrew Nester added the comment:

Agree about surprising behaviour but I guess it's better to fix it as other 
issue because it could break BC in some cases. At least it needs to be 
investigated.

For now I would like to stick with same behaviour for _decimal and _pydecimal

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Andrew Nester]

Andrew Nester added the comment:

actually, it's more related to subclassing, because the problem comes from the 
fact that before the fix __init__ method receives value as int not Decimal if 
int passed to from_float call. 
That's why only subclasses of Decimal can see difference in arguments received 
by __init__

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Mark Dickinson]

Mark Dickinson added the comment:

BTW, as a user, I'd expect `Decimal.from_float` to simply coerce its input to 
float if given an input that isn't actually a float in the first place; the 
fact that it has special handling in place for int inputs (and that that 
special handling takes the form of an isinstance check, rather than something 
more duck-typed) is surprising.

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Mark Dickinson]

Mark Dickinson added the comment:

Is there an observable difference in user behaviour if no subclassing of 
Decimal is involved? Or does this just affect Decimal subclasses?

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Mark Dickinson]

Mark Dickinson added the comment:

> it's a one-time hack intended to be removed and forgotten at the end of 3.5's 
> lifetime.

Fair enough. If necessary, one of our options is to apply that patch or 
something like it to the Python executables that we distribute for Canopy. But 
in general, staying as close as possible to the upstream Python is desirable, 
so if there were a possibility for it to go into upstream Python, that would be 
helpful.

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Petr Viktorin]

Petr Viktorin added the comment:

> perhaps Petr's patch to accept both magic numbers should be submitted 
> upstream so it's the default in 3.5.4+?

I don't think it can be submitted in the current state; it's a one-time hack 
intended to be removed and forgotten at the end of 3.5's lifetime.

I could write a patch with proper support for accepting a range of magic 
numbers, but such a feature probably won't be needed again.

--

___
Python tracker 

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

[issue29534] _decimal difference with _pydecimal

[Andrew Nester]

Andrew Nester added the comment:

I've just added PR for this issue.

--
nosy: +andrewnester
pull_requests: +51

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Mark Dickinson]

Mark Dickinson added the comment:

[Nick]
> perhaps Petr's patch to accept both magic numbers should be submitted 
> upstream so it's the default in 3.5.4+? [...]

Enthought's primary buildsystem maintainer is unfortunately out of contact for 
the week, so I can't speak with any authority on this, but I believe that we'd 
find this helpful.

--

___
Python tracker 

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

[issue29542] python -m spacy.en.download undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report, but spacy is not part of the Python standard library. 
Please report your problem to spacy developers.

--
nosy: +berker.peksag
resolution:  -> third party
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

[issue29542] python -m spacy.en.download undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

[Vladimir Shebunyaev]

New submission from Vladimir Shebunyaev:

I have  (python 2.7.13 Anaconda 4.3.0 64bit Ubuntu 16 )
tried

python -m spacy.en.download

and got

/home/vshebuniayeu/anaconda2/bin/python: 
/home/vshebuniayeu/anaconda2/lib/python2.7/site-packages/spacy/serialize/huffman.so:
 undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

--
messages: 287674
nosy: Vladimir Shebunyaev
priority: normal
severity: normal
status: open
title: python -m spacy.en.download undefined symbol: 
_ZSt24__throw_out_of_range_fmtPKcz
type: compile error
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

[issue29532] functools.partial is not compatible between 2.7 and 3.5

[INADA Naoki]

INADA Naoki added the comment:

patch LGTM.

--
nosy: +inada.naoki

___
Python tracker 

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

[issue29538] bugs.python.org does not redirect to HTTPS

[Berker Peksag]

Changes by Berker Peksag :


--
resolution:  -> duplicate
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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Nick Coghlan]

Nick Coghlan added the comment:

Given some of the other folks encountering problems, perhaps Petr's patch
to accept both magic numbers should be submitted upstream so it's the
default in 3.5.4+? And then we ask Larry and the other release management
folks nicely for an early 3.5.4 release?

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Nick Coghlan]

Nick Coghlan added the comment:

On 12 Feb 2017 11:54 pm, "Serhiy Storchaka"  wrote:

Serhiy Storchaka added the comment:

I don't understand how the table can make maintaining easier. You need to
support multiple values in every branch even if the only one value is used.
I'm sure unused values will became outdated pretty fast.

"alpha" and "beta" stages are not related here. The test should be skipped
at these stages (I recommend to use skipTest() or the skipUnless()
decorator rather than just make test always success). Magic number can be
changed multiple times at "alpha" and "beta" stages. Release manager needs
to update the test only when forming the first release candidate. And his
should not do anything if the magic number was not changed in this feature
release.

Serhiy's argument here & the fact we've switched to a cherrypick model for
maintenance branches has persuaded me we just want a single "expected magic
number" in the test case rather than the full table that covers multiple
releases.

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Mark Dickinson]

Mark Dickinson added the comment:

[Nick]
> "Requires a mass rebuild of all the Python packages in the distro to get 
> things working properly again" is again a major concern for what's nominally 
> a low impact maintenance update.

With my Enthought developer hat on, I'd like to second this comment. We'll 
shortly be shipping Python 3.5.2 in Enthought Canopy, and this bytecode change 
presents us with a major issue to resolve (internal discussion about how to do 
so is ongoing). If/when we make 3.5.3 available, and the user upgrades their 
core Python, all user-installed 3rd party packages become semi-broken, and we 
potentially need to ask the user to upgrade many hundreds of packages. (We also 
need to rebuild and re-test all those packages for our own repository, which is 
a time-consuming process.)

[Łukasz]
> I'd be very careful about ever bumping magic numbers in minor releases again, 
> and definitely communicate loudly if doing so.

Also seconded.

--

___
Python tracker 

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

[issue29541] Python3 error while building on Alt-F

[Honza Skýpala]

Honza Skýpala added the comment:

Hi Chi Hsuan Yen, thanks for trying to help, unfortunately no change, still 
getting the same error.

--

___
Python tracker 

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

[issue29514] Add a test case that prevents magic number changes in minor releases

[Mark Dickinson]

Changes by Mark Dickinson :


--
nosy: +mark.dickinson

___
Python tracker 

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

[issue29538] bugs.python.org does not redirect to HTTPS

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

Duplicate of http://psf.upfronthosting.co.za/roundup/meta/issue463

--
nosy: +Chi Hsuan Yen

___
Python tracker 

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

[issue29541] Python3 error while building on Alt-F

[Chi Hsuan Yen]

Chi Hsuan Yen added the comment:

My patch at https://hg.python.org/cpython/rev/ca2f024ce7cb may help. It points 
out missing symbols earlier.

--
nosy: +Chi Hsuan Yen

___
Python tracker 

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