Opened 12 years ago

Closed 6 years ago

#5961 closed defect (duplicate)

Document potential interference issues with ~/.pydistutils.cfg

Reported by: mabshoff Owned by: tba
Priority: major Milestone: sage-6.4
Component: documentation Keywords:
Cc: Merged in:
Authors: Reviewers: Karl-Dieter Crisman
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges



Dear Sage developers,

I tried to build Sage-3.4 on my intel macbook (Mac OS X 10.4.11).  I
have Xcode 2.5 installed and gcc-4.0.1. I downloaded the sage-3.4.tar,
untarred it and ran make. I have macports installed so changed the PATH
to remove anything from /opt.  I also renamed /opt to something else in
one attempt but both failed with the same error:

Sleeping for three seconds before testing python
Traceback (most recent call last):
   File "<string>", line 1, in <module>
   File "/Users/prabhu/src/build/sage-3.4/local/lib/python2.5/",
line 6, in <module>
     from hashlib import md5
"/Users/prabhu/src/build/sage-3.4/local/lib/python2.5/", line
133, in <module>
     md5 = __get_builtin_constructor('md5')
"/Users/prabhu/src/build/sage-3.4/local/lib/python2.5/", line
60, in __get_builtin_constructor
     import _md5
ImportError: No module named _md5
md5 module failed to import
sage: An error occurred while installing python-2.5.2.p9
Please email sage-devel
explaining the problem and send the relevant part of
of /Users/prabhu/src/build/sage-3.4/install.log.  Describe your
computer, operating system, etc.


Searching the lists for this gave me this:

which isn't very helpful.

After spending a little while figuring out what is wrong I realize that
I've done something a little non-standard that broke things.  I have
a default ~/.pydistutils.cfg which reads like so:

install_lib = ~/Library/Python/$py_version_short/site-packages
install_scripts = ~/usr/bin

I completely forgot about this and my install logs indicated a large
number of files being installed in the `install_lib` directory. So
moving this .pydistutils.cfg out of the way helped resolve the problem
and the build went well.

I think this should be documented somewhere so others don't fall into
the same trap.  Thanks.


Change History (7)

comment:1 Changed 8 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:2 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:3 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:4 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:5 Changed 6 years ago by kcrisman

  • Report Upstream set to N/A
  • Reviewers set to Karl-Dieter Crisman
  • Status changed from new to needs_review

This is a dup of #9536.

comment:6 Changed 6 years ago by kcrisman

  • Status changed from needs_review to positive_review

Not that that one has had much activity lately either, but it has an actual patch and some conversation.

comment:7 Changed 6 years ago by vbraun

  • Resolution set to duplicate
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.