You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Double-check the bug hasn't already been reported on our issue tracker, they should be labelled bug or bugsnag.
Issue
As shown below, the git+https[...] package reference is interpreted as git instead of esgf-compute-api in this case.
I'm guessing the + leads to a space escape or something similar, but this is a valid method to reference/install a package.
The alternative (more traditional?) method is something like:
<package> @ <reference-url>
This invalid parsing is more problematic in cases where there are more than one git+https reference, as they are all regrouped under a common git package.
Bugs
Checks
Before submitting a bug report:
bug
orbugsnag
.Issue
As shown below, the
git+https[...]
package reference is interpreted asgit
instead ofesgf-compute-api
in this case.I'm guessing the
+
leads to a space escape or something similar, but this is a valid method to reference/install a package.The alternative (more traditional?) method is something like:
This invalid parsing is more problematic in cases where there are more than one
git+https
reference, as they are all regrouped under a commongit
package.Contents of
requirements.txt
(partial)Reported on Libraries.io
https://libraries.io/github/crim-ca/weaver
The text was updated successfully, but these errors were encountered: