Skip to content

Python entry point doesn't work if package is installed in a non-default directory #8

@Rob-Welch

Description

@Rob-Welch

For example, if you use the system version of python on the HPC, you can't install into the site-packages directory, you have to install into some user PREFIX directory. This causes the ctools entry point to fail with the following error:

  File "/home/rw690/site-packages/bin/ctools", line 11, in <module>
    load_entry_point('chromatin==0.1.0', 'console_scripts', 'ctools')()
  File "/usr/local/software/anaconda/3.2019-10/lib/python3.7/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/local/software/anaconda/3.2019-10/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2851, in load_entry_point
    raise ImportError("Entry point %r not found" % ((group, name),))
ImportError: Entry point ('console_scripts', 'ctools') not found

Strangely, opening the python console and doing import chromatin.ctools works just fine. So clearly there is some other issue here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions