On Mon, Sep 3, 2012 at 3:26 PM, Matthew Brett <[email protected]> wrote: > Hi, > > On Mon, Sep 3, 2012 at 8:45 PM, Aaron Meurer <[email protected]> wrote: >> That looks like it would work. This is our .travis.yml: >> https://github.com/sympy/sympy/blob/master/.travis.yml. >> >> **Hopefully** when we release, pip install sympy and pip-3.2 install >> sympy (or whatever the Python 3 pip binary is called) should just >> work. I say hopefully because pip likes to do its own thing >> sometimes, and it's almost impossible for me as a package maintainer >> to do anything about it. > > pip makes me nervous as well. Can you upload a separate python 2 and > python 3 source package to pypi and expect pip / easy_install to get > the right one by default? > > Presumably you chose not to run the 2to3 conversion in your base > setup.py because it takes too long?
Honestly, I would like if setup.py worked for both Python 2 and Python 3. Yes, it takes long, but we can still support our current way as well. However, I think we run into some problems with trying to persuade 2to3 to only run on subset of sympy sources (in particular skipping mpmath, for which it fails and whose sources work in both python 2 and 3). Maybe it is possible to fix it. Ondrej -- 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.
