-
Notifications
You must be signed in to change notification settings - Fork 4
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
Formula parser & alias cleanup & rich-based help #27
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the new features, especially xrun_asyncio
!
Let's remove (comment out) the scabha dependency from setup.py for now.
@@ -9,13 +9,19 @@ | |||
requirements = ["pyyaml", | |||
"nose>=1.3.7", | |||
"future-fstrings", | |||
"scabha @ git+https://github.com/caracal-pipeline/scabha2", | |||
"scabha >= 0.7.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then we should just remove the scabha dependency for now. Because scabha 0.7.0 is not on pypi, and it makes no sense to require it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or we could just merge the scabha PR and make a release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That works for me
stimela/commands/run.py
Outdated
from stimela.config import ConfigExceptionTypes | ||
import click | ||
import logging | ||
import os.path, yaml, sys | ||
import os.path, yaml, sys, asyncio |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not kosher. Unless importing from the same module/library, each import should be on a new line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PEP-8 says "Imports should usually be on separate lines", so I tend to interpret that loosely. Particularly when a large number of the usual standard library suspects are imported, like import os, os.path, sys
etc. I just find the import section gets too big.
@SpheMakh please approve and merge. |
Matched set with caracal-pipeline/scabha2#21.