On Nov 17, 2012, at 7:39 PM, Matthew Brett <[email protected]> wrote:
> Hi, > > I've been running into trouble installing sympy with easy_install and > pip on python 2.7 and Python 3.3. What issues with pip are you having? I thought we fixed pip to do the right thing. > > The fact that easy_install / pip is unlikely to work means that sympy > is a considerably heavier burden for our (nipy.org/nipy) users to > install, and I'd very much like to help fix that. > > This led me to start editing the sympy setup.py to do the standard > thing of running 2to3 during setu.py install : (e.g numpy, scipy, > matplotlib, our projects). > > I immediately found why you haven't done this: you depend on running > > python setup.py run_tests > > and > > python setup.py run_benchkmarks > > in the source tree. So, there's no way of running these for python 2 > and python 3 in the same source tree (unless you go for python 3 > compatibility in source - a bit much). > > So - I'm writing to ask if you'd consider looking at a refactor that > would change these calls above to: > > python setup.py install --user (or whatever) > cd /somewhere > python -c 'import sympy; sympy.test()' The problem is that setup.py test runs tests that aren't included in an install, namely the Sphinx doctests. > > or > > python setup.py install --user (or whatever) > cd /somewhere > python -c 'import sympy; sympy.bench()' Benchmarks from setup.py aren't very important. We can remove them if they are a hinderance. Aaron Meurer > > This has three advantages: > > 1) You can run 2to3 in your install. This is generally very quick > after the first pass. E.g for our project nipy: > > time python setup.py install > -> > real 2m7.466s > user 1m51.458s > sys 0m6.254s > > time python setup.py install # a second time, only processing modified files > -> > real 0m3.428s > user 0m2.614s > sys 0m0.712s > > 2) You can use the workflow above to develop and test in python3 : > > python setup.py install # some longish time say 2 minutes > <edit> > python setup.py install # A few seconds > <test> > etc > > 2) You can have compiled code in your project without breaking the > tests / benchmarks > > 3) easy_install / pip will work :) > > So - would you consider this change? If so, I will write a pull > request for it. > > Best, > > Matthew > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
