On May 4, 2009, at 12:37 PM, Istvan Albert wrote:
> > On May 4, 11:05 am, michel bellis <fill.i...@9online.fr> wrote: > >> It does not appear that another pygr is installed : > > You can't tell that from the list below, you would need to look inside > the paths as well. Like Titus, I got the impression that Michel's problem might be connected to running Python within the pygr source directory itself. When Michel first posted, he had import statements like "import seqdb" that would only work if his current directory was the pygr/pygr/ source directory. That could cause all sorts of confusion that would look like "two different installations of Pygr" being combined inconsistently. For example, unless he compiled build_ext -i, the cnestedlist etc. compiled DLLs would be found within the Python site- packages, but not within the source directory pygr/pygr/. In short, I think Titus' recommendation that Michel make sure he is running Python *outside* of the source directory may be the route to solving the problem. -- Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
