Bring back the PythonWheelDistributionPlugin
See original GitHub issueIt looks like the PythonWheelDistributionPlugin was removed from the latest version of Pygradle: https://github.com/linkedin/pygradle/commit/9ad8e104d8f47cd130f9ee82754a616080c714ac#diff-3150c245427f4dba770f943d6d924412L9. Can you guys bring it back? We would like to be able to publish wheel package artifacts for our projects and it used to just work by calling the packageWheel
task. This task is no longer available with version 0.7.7.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Packaging and distributing projects
Working in “development mode”. Packaging your project. Source distributions. Wheels. Pure Python Wheels. Platform Wheels. Uploading your Project to PyPI.
Read more >What Are Python Wheels and Why Should You Care?
Wheels install faster than source distributions for both pure-Python packages and extension modules. Wheels are smaller than source distributions. For example, ...
Read more >Optimize pip install with wheels - Roman Imankulov
When “pip install” can't find a wheel, it falls back to installing from source. In a large project, dependency after dependency, it slows...
Read more >Create a Python Wheel File to Package and Distribute Custom ...
Learn how to create a Python wheel file load it to Databricks and call a function within the package in a Databricks Notebook....
Read more >Python Wheels
Wheels are the new standard of Python distribution and are intended to replace eggs ... Faster installation for pure Python and native C...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Do you like the name, or do you have some other ideas for it?
Good point. I’ll add some docs too. I’m not quite ready to promote it to “prod” (should be in the next week or so when I feel ready for that). Once that happens, it will get a nice name that you can apply vs using the class name.
If you have any other classes you’re using as a FQDN let me know, and we can make them “public”.
We’ve merged this, so I’ll close this one out. Let me know if you run into anything else because of it!