Changes between Initial Version and Version 1 of Ticket #18955


Ignore:
Timestamp:
07/26/15 18:05:31 (5 years ago)
Author:
buck
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18955

    • Property Component changed from PLEASE CHANGE to packages: standard
    • Property Type changed from PLEASE CHANGE to defect
  • Ticket #18955 – Description

    initial v1  
     1In the current master branch (7eb8510da), when I `./sage -i setuptools` it fails with this message:
     2
     3{{{
     4****************************************************
     5patching file setuptools/command/easy_install.py
     6Hunk #1 succeeded at 1491 (offset 45 lines).
     7Hunk #2 succeeded at 1529 with fuzz 1 (offset 45 lines).
     8Hunk #3 succeeded at 1555 (offset 45 lines).
     9patching file pkg_resources/__init__.py
     10running install
     11running bdist_egg
     12running egg_info
     13writing requirements to setuptools.egg-info/requires.txt
     14writing setuptools.egg-info/PKG-INFO
     15writing top-level names to setuptools.egg-info/top_level.txt
     16writing dependency_links to setuptools.egg-info/dependency_links.txt
     17writing entry points to setuptools.egg-info/entry_points.txt
     18Searching for pip
     19Reading https://pypi.python.org/simple/pip/
     20Download error on https://pypi.python.org/simple/pip/: [Errno 110] Connection timed out -- Some packages may not be found!
     21Couldn't find index page for 'pip' (maybe misspelled?)
     22Scanning index of all packages (this may take a while)
     23Reading https://pypi.python.org/simple/
     24Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found!
     25No local packages or download links found for pip
     26error: Could not find suitable distribution for Requirement.parse('pip')
     27
     28real    4m15.474s
     29user    0m0.516s
     30sys     0m0.138s
     31}}}
     32
     33This timeout is caused by the "poison" proxy:
     34
     35{{{
     36build/bin/sage-spkg:export http_proxy=http://192.0.2.0:5187/
     37}}}
     38
     39but I don't know why the process is searching for pip. My workaround was `python -m ensurepip`, but that's only going to work for python>=2.7.9.
     40
     41I also tried `sage -i pip`, but it depends on setuptools, so that's circular.
     42
     43I'm not sure how you're going to solve this.