On Samstag, 25. Juni 2011, Algis Kabaila wrote: > On Sat, 25 Jun 2011 08:02:13 PM Algis Kabaila wrote: > > Hi, > > > > It seems that eric5 does not take account of PYTHONPATH. The path > > paradigm of Python3.x is different to that of Python2.x. When porting > > Python2 scripts to Python3 it becomes necessary to use PYTHONPATH or > > completely remake the structure of the program. Even then, PYTHONPATH > > is very useful and possibly essential. > > > > Is there a way to get eric5 to take account of PYTHONPATH? > > > > Thanks for my favourite IDE - eric! > > > > OldAl. > > I have not really explained where the PYTHONPATH becomes necessary. The > scripts often have a package that stores various modules required by the > program. Often module2,py needs to use module1.py and that in Python2 is > simply > import module1 > statement in module2, which is in the same package. In python3, AFAICS, > this import statement fails, unless the package is on the python path. In > these circumstances PYTHONPATH seems to be by far the easiest solution. > > I have tested this on a program for structural analysis where, with the > PYTHONPATH activated from CLI the import statement works fine, but not in > eric. > > If required, I could provide a small, artificially made up example. > > Thank you for the great work that you are doing! > > OldAl. > _______________________________________________ > Eric mailing list > [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/eric
It should when you enter the correct string in the environment line edit of the dialog that appears, when you run, debug, ... your script or project. Regards, Detlev -- Detlev Offenbach [email protected] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
