On 12/10/16 09:26, Dima Pasechnik wrote:
On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
Right, Sage's Python is broken. Try deleting sage/local/bin/python
and python2, and also sage/local/lib/python2.7 and
sage/local/lib/libpython2.7.dylib. Then the build process should use
the system's Python until Sage builds a working one.
hmm, I don't understand. I think I tried starting from 'make distclean'
and still got stuck at that No module named _scproxy thing.
I know there are safe guards in sage-env but nonetheless once the broken
python is installed it has to be cleaned manually. It is my experience
too. It is an OS X (mainly Sierra right now) thing only.
Francois
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
