-
Notifications
You must be signed in to change notification settings - Fork 32
Proposing add_formal_parameter function #221
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
Conversation
I've found some issues with the PR:
I've applied these changes in 4ee784c to give the idea. Please add a unit test to I could not reproduce the editable mode issue, on my PC it works with pip-25.1.1. This blog post has some info. Maybe your setuptools version is too old? I've added |
Thanks @simleo for reviewing the PR, I will try adding the tests in the coming days. Regarding the If complying with the Bioschemas FormalParameter profile, the contextual entities for FormalParameter, referenced by input or output, MUST describe name. |
Yes, but neither the Workflow Run Crate profile nor the base spec require strict conformance to the Bioschemas spec. However, we are adding the |
@LauLauThom thanks for the contribution! before merging I need you to update author and copyright info. Author info is in |
Done, I am not sure I can attend the call tomorrow though, I have a training until 4 that might go overtime. |
No, the copyright info is still missing |
sorry, I had overlooked this, I mentioned the city in addition to the country, because the EMBL has different sites (well there is just one in germany but still) |
Following yesterday's call, here is a small PR proposing the addition of a function to facilitate the definition of FormalParameters in a workflow crate.
It makes use of type hints, which is available from python 3.5, support could be added for earlier version by adding the typing package to the list of dependencies, checking the version of python to only install if needed.
I am happy to write tests and documentation for this function if you think that's a valid addition.
Currently it can be tested with
Actually for testing I typically install the package in editable mode like so
pip install -e .
but I got an exception that it's not possible
DEPRECATION: Legacy editable install of rocrate==0.13.0 from file:///Users/thomasl/Documents/repos/ro-crate-py (setup.py develop) is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457
So I was wondering how you test it usually.
I also had issues with test discovery, but that's maybe something with my VScode config.
Cheers !