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
Some packages put rather important functionality behind [extras], and these are not followed up by install-minimums, which can leave a broken test state if not specified directly.
Proposed Solution
figure out how to make the spec building discover these when solving
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
In my particular case, the upstream had changed the name of the extra from [format_nongpl] to [format-nongpl], but I did find it worked after re-installing manually after the install-minimal action.
Problem
Some packages put rather important functionality behind
[extras]
, and these are not followed up byinstall-minimums
, which can leave a broken test state if not specified directly.Proposed Solution
test-sdist
'spackage_spec
Alternatives
install-minimums
users[extras]
😝[extra]
as another extraAdditional context
jsonschema[format-nongpl]
.The text was updated successfully, but these errors were encountered: