Why even follow the python packaging format if everything needs to be in artifactory anyway?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 603
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
What I don't understand about this plugin, is why it uses setup tools at all?
In the end everything needs to be in artifactory, so why not just store the packages in a custom format, then extract them locally when installing the build, create a virtual environment that loads this, etc.
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 plugin's use of setuptools, Artifactory, local extraction, and virtual environments as described in the issue. Clarify whether a custom package format is wanted, then define the required packaging and installation behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100