Fix pip install bug when jupyter lab version restricted to 3.0.* #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@timcera There was a change in some prior version of
environment.yml
, which is called bysetup.py
. When the jupyterlab=3.0.* is used,pip install .
fails with a cryptic warning of:It appears that this
- jupyterlab =3.0.*
was not good syntax(?), so:jupyterlab >=3.0.14
. installed just fine.- jupyterlab ==3.0.*
(note extra '=' sign), which is the format used by other modules, and it also installed just fine.Presuming that the extra '=' was what was intended, I kept the
3.0.*
version, though wondered if the>=
syntax might be preferable as it would then be compatible with3.1+
? I dunno. But if someone thinks we should use a>=
syntax, I can go back and do a new PR with that fix.Also in this PR - some cleaned up code to add stubs for special actions.