-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lineage installation does not build with PyPa #174
Comments
@ayush9pandey what is the lineage error? Maybe this can be fixed. |
Here's the error: https://github.com/biocircuits/bioscrape/actions/runs/9904679317/job/27362599090 you can also re-create it by setting up a py 3.12 environment and running It would be great if it could be fixed. |
@ayush9pandey I suspect this issue is to do with Python moving away from setup.py in newer versions. It looks like cython is expecting every import to be a separate file. I can look into this further in August (next couple of weeks are a swamp). It's interesting that Bioscrape core installs but Lineages doesn't. |
With new Python v3.12 compatibility in Bioscrape and changes to the Python build process for PyPi release (the recommended way is through: https://build.pypa.io/en/latest/), the command
python -m build
throws an error in lineage installation.Suggested fix: Set up such that
pip install bioscrape
only installs bioscrape core without lineage. For users who need lineage, the direct installation method would still work withpython setup.py install lineage
after cloning the repository.An alternate (ideal) fix: Set up the build process such that lineage is also built and packaged in the distribution.
The text was updated successfully, but these errors were encountered: