`import cornish` fails when installed from `pip` or source
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hello - I was hoping to try out cornish at the recommendation of Eric Huff. I can install successfully from either pip or source on a fresh conda env, but in either case I get the following:
python -c "import cornish"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/Users/sweveret/miniconda3/envs/astro/lib/python3.9/site-packages/cornish/__init__.py", line 7, in <module>
from .channel.ast_channel import ASTChannel
ModuleNotFoundError: No module named 'cornish.channel'
I asked Eric what version he has installed on a previously used env and it was v1.1. I made a new env that built from source on the v1.1 tag and have the same outcome. I can do some more digging later in case I missed something obvious, but I thought I would flag it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the import command and inspect cornish/init.py, especially its import of cornish.channel.ast_channel. Compare the package contents installed from pip with the source checkout and the v1.1 tag. Done means a fresh conda environment can install the project from pip or source and complete python -c "import cornish" without ModuleNotFoundError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100