Bug#827740: Re #827740: isympy start fails: No module named sympy.interactive

[Drew Parsons]

On Mon, 20 Jun 2016 14:06:11 +0200 Alberto Luaces <aluaces at udc.es>
wrote:
> > Maybe another binary package could be added (named isympy3),
> including
> > an appropriate isympy3 script...
> > At that point isympy would depend on python-sympy (without
> > python3-sympy as an alternative dependency) and isympy3 would
> depend on
> > python3-sympy.
> 
> I guess a good solution could be one along the lines you are posting:
> having two packages with no intermixed dependencies, with some aid of
> the dpkg alternative system (that is used, for example, to set the
> default version of gcc).  Unfortunately, I currently do not know
> enough
> of that system in order to send a patch right now.


Alternatives won't provide a clean fix, although we should be able to
make some kind of isympy3 work.

Because of the shebang,  calling isympy directly (rather than via
python isympy or python3 isympy) will always load python2.

Luke's patch removes the option of using isympy with python3, but we
shouldn't need to do that.

Seems to me the best option is to create as separate isympy3 script
(with a separate isympy3 package) which does nothing other than call
python3 isympy.

I'll load a patch to git.

Drew