pcdshub / pcdshub/pcds-python-migration-tools
Raise if scripts are used instead of entrypoints
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I ran into this in the elog migration too, though there it was a raw python file being referenced instead of an entrypoint. As a result the conversion didn't work, but that's somewhat out of scope here.
In my case this error helped alert me to the error, and with this the script would have
just disappeared. I'm not sure there's a good way around this and I don't think it's a common case.
Originally posted by @tangkong in https://github.com/pcdshub/pcds-python-migration-tools/pull/11#pullrequestreview-1312021495
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the migration behavior discussed in pull request #11, focusing on how raw Python files are handled when they are referenced instead of entrypoints. Clarify with maintainers whether such references should raise an error, then define regression coverage for the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100