Donald Stufft added the comment:
This should be fixed now as of https://hg.python.org/cpython/rev/651e1862dbed,
https://hg.python.org/cpython/rev/651e1862dbed, and
https://hg.python.org/cpython/rev/9f60d024e586.
--
resolution: - fixed
status: open - closed
Terry J. Reedy added the comment:
test_venv passed on Open Indiana in the 14:10-14:22 buildbot runs triggered by
the patch. It failed with a different error on a later default run, but that
looked like a different issue, if permanent.
--
___
Donald Stufft added the comment:
I'm not sure how to get a link to that, can you link it and I can see if I
think it's a permanent error or not?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22669
Terry J. Reedy added the comment:
http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/9012/steps/test/logs/stdio
Start with buildbot.python.org, select set of (all/stable) buildbots for
version. 'Build ' like gives commit(s) that triggered build. Test stdio
link, as
Donald Stufft added the comment:
Assigning this to myself, it'll get fixed when pip 6.0 is released and I
upgrade ensurepip to it.
--
assignee: vinay.sajip - dstufft
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22669
Terry J. Reedy added the comment:
I think this was improperly closed. #22611 was about pip. This one is about
test_venv failing today, 8 days after 22611 was closed, when optional module
_ctypes is not built. The resolution of this issue should be that either the
buildbots start using the
Ned Deily added the comment:
Issue22611 documents exactly the same failure so if this issue was improperly
closed than Issue22611 was, too. So I would think the earlier issue would be
the place to discuss this. But, in any case, I think the issue is that the
latest version of pip hasn't
Donald Stufft added the comment:
It hasn't been released yet, test_venv could be temp disabled if ctypes isn't
available though.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22669
___
Ned Deily added the comment:
As I understand it, the reason test_venv is failing is because of a defect in
the pip vendored colorama. The test has found the unexpected dependency of the
vendored package with ctypes. It's good that the test failed. The right
solution is to provide the
Donald Stufft added the comment:
More or less. You could argue whether it's a defect or not but it
unconditionally imports ctypes and apparently that is an optional module (I had
no idea it was personally, and I can't find any documentation to say that it
is). colorama doesn't really *need*
New submission from Terry J. Reedy:
For whatever reason, AMD 64 Open Indiana ('stable' buildbot #3) is not building
ctypes. test_venv fails with
FAIL: test_with_pip (test.test_venv.EnsurePipTest)
--
Traceback (most recent call
Ned Deily added the comment:
This is a duplicate of Issue22611.
--
nosy: +dstufft, ned.deily
resolution: - duplicate
stage: needs patch - resolved
status: open - closed
superseder: - pip needs ctypes
___
Python tracker rep...@bugs.python.org
12 matches
Mail list logo
