-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add setuptools and package Cylc as a Python module #2989
Comments
Note to self: need a section for the documentation dependencies. We need |
Group added, |
Looking at some tests failing in Travis, and noticed a warning that appears but without failing the test from what I could tell.
So actually |
A quick way to analyze project import dependencies and check what's used is using pydeps. $ PYTHONPATH=./lib pydeps --externals lib/cylc
[
"collections",
"colorama",
"isodatetime",
"jose",
"logging",
"mock",
"parsec",
"pytest",
"sqlite3",
"testfixtures",
"zmq"
]
['collections', 'colorama', 'isodatetime', 'jose', 'logging', 'mock', 'parsec', 'pytest', 'sqlite3', 'testfixtures', 'zmq'] This can be useful to check against |
Finally! It was Then, changed to actually `export CYLC_DIR="${TRAVIS_BUILD_DIR}", and now it worked. I've added tasks (bullet items) to the issue description. The next one that needs further work is documentation (hopefully easier). It appears to be broken in virtual environments too. I'm getting the same error message as Travis right now (even though it says success, the last state of the build for documentation actually failed!):
|
And once docs are working, I'm planning on creating a separate ticket for |
Phew, well done solving that. |
Alright, had to fix make-docs, but now I think the basics are working. Will sleep now and review once again tomorrow. Hoooopefully ready to be reviewed on Monday. Travis CI is happy too \o/ |
This way we will be able to use Cylc as a dependency in other projects such as part of larger systems, Jupyter Notebooks, or even in experiments to extend Cylc.
This is also useful to create packages for PYPI, Conda, and RPM (see #1337). Will serve as basis for #2802 too, in order to have script commands as code, with tests, and even re-using in components such as Cylc UI Server to run a workflow for instance.
Things to consider when confirming this issue can be closed:
pip
from cylc import ...
in a terminal, but also in Python code, and Jupyter NotebooksCYLC_DIR
usage (moved to Revisit CYLC_DIR use #3080)CYLC_VERSION
works. (moved to Revisit the CYLC_VERSION use prior to setup.py #3081)The text was updated successfully, but these errors were encountered: