On May 4, 11:45 am, michel bellis <fill.i...@9online.fr> wrote:
> The problem is reproducible. I have installed pygr on another PC and
> got exactly the same problem :
is this with pythonxy or regular python?
> If I start a new python console from the 'dos windows', import
> pygr.seqdb works well.
> But if I quit python and I run a test program (with that line inside :
> from pygr import seqdb), that
> raises the ImportError: 'cannot import name seqdb'.
> Finally if I return in a new python console I am not able to import
> seqdb anymore (same ImportError) !
this is really a head scratcher in that regardless of how pygr is
installed, you should not get a different behavior just because you
run a python program. Sounds like it is leaking/overwriting
environment variables.
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to pygr-dev@googlegroups.com
To unsubscribe from this group, send email to
pygr-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
