Description
It's less and less likely that developers will use the system's zypper/dnf/etc to install dependencies for their applications, but SUSE and openSUSE still put effort in supporting Python packages either for supporting their own tooling or other external apps that depend on them.
It may be useful if the Python packages that are being supported within the distribution would also be available on a PyPI, so that developers can make use of them in a more transparent way.
The advantage for the user is having (hopefully) better curated list of packages that undergo active maintenance.
Goals
- get familiar with local caches / alternative sources for PyPI
- choose a codestream to work on
- extract some packages and play with itit
- devise a simple automated way to extract them from a codestream or channels
- check whether exposing pre-built binaries for the packages is feasible
- get distracted with some bikeshedding on the way
- have fun
Resources
- 🧉
- 
-
Looking for hackers with the skills:
This project is part of:
Hack Week 24
Activity
Comments
-
about 1 month ago by barendartchuk | Reply
The exploration start earlier than expected! One important concern (raised elsewhere) is that this would not help developers that have their requirements pinned to specific versions. They would have to do some extra work to use the suse versions anyway.
-
27 days ago by barendartchuk | Reply
So I didn't move on on this project anywhere close to what could be called success. I spend most of the time exploring the options in the discussion I pointed above (a private one, unfortunately). I also reviewed the dependencies of one of the L3 tools (Django app) and tried to match with what we have available in the IBS. The AI codebase seems to provide the best codestream for that application.
Similar Projects
This project is one of its kind!