-
Notifications
You must be signed in to change notification settings - Fork 52
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
[UX] Explain that creating a Python package is useful even if you will never upload it to PyPI #272
Comments
Next action: Pathway for going from a script to a package. Related to https://peps.python.org/pep-0723/ |
wow @zackw another really good insightful issue!! thank you for all of the thought that you put into all of these issues. so i actually see two potential use cases here that are very much in scope for our tutorial work around code --> module or sharing code.
Do those two use cases resonate @zackw ? i can actually see two distinct tutorials here that we could work on and flesh out that would likely help a lot of people. |
The packaging tutorial should have an alternative intro that explains that creating a Python package gives you the ability to split up a program into multiple Python source files, and the ability to list your program’s dependencies so they can be automatically installed from PyPI (
pip install -r requirements.txt
, Hatch environments, etc.)This is for people who are accustomed to writing self-contained single-file
#! /usr/bin/python3
scripts that depend only on the standard library and perhaps also packages installed manually via the system package manager. It might need to be a whole new tutorial all by itself, and a new onboarding “funnel” from the top level of the website, because people with this reason to create a package probably don’t know that a package is what they need.(Some of what’s already listed under “Why create a Python package” does touch on the above, but if you don’t already know that packages are relevant to your problem, you may not realize that that’s what it’s talking about.)
The text was updated successfully, but these errors were encountered: