-
Notifications
You must be signed in to change notification settings - Fork 548
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
target 'rules_python_wheel_entry_point_hjson' not declared in package #602
Comments
This issue is caused by the https://github.com/hjson/hjson-py/blob/master/setup.py#L75 This could potentially be "fixed" (I'd call this more of a feature-request fulfillment) by #575 |
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
Cc @groodt |
Agreed. I think I'll create an "umbrella" tracking issue for "legacy scripts support". fwiw, it seems that perhaps hsjon will switch to entrypoints (or at least are being encouraged by conda to do so) hjson/hjson-py#29 |
This particular issue with hjson is fixed in Tested against the minimal reproduction and it works.
Closing. |
🐞 bug report
The
entry_point
for packagehjson
does not work withv0.6.0
.Is
entry_point
not fully available for use yet? I don't see any mention of it on the top levelREADME.md
.Affected Rule
entry_point
methodIs this a regression?
Not sure. First time I've tried using this feature of
rules_python
. Perhaps this package is a different case of an invalid entry points config?Description
The
rules_python_wheel_entry_point_hjson
not generated for requirementhjson==3.0.2
:🔬 Minimal Reproduction
rules_python
branch, try running any of the targets likebazel run //:hjson
.🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
The text was updated successfully, but these errors were encountered: