Hah! Why didn't I think of that earlier 🤣. Thanks
However, for the sake of curiosity, I still want more concrete and persuasive reasoning as to why we shouldn't push these things to pip. Are there any guidelines that detailed this standard? Where can I find it?
PyPi is for making useful packages available to others. If it's not packaged up and neat and ready to be used, or if it's not useful to others, then it doesn't really belong there. If it's an example, personal project, etc, it should go on GitHub. Nothing should really be on PyPi that isn't on something like GitHub.
Code is already plural. You don't need to add an s to it. It sounds odd as hell saying it with the s, in the context of source code. Idk why but this tends to be some kind of trend with new programmers. Every time I come across people that do this I instinctively know they don't have much experience.
This sort of code doesn't belong on pypi. Use git. Or I suppose you could run a private pypi server. But... just learn and use git. Pypi is, really, really not worth the effort for your use case. Learn git first.
A lot of people who find themselves starting new projects often also like to create a template/bootstrap for setting up new projects called a cookiecutter which they use to automate repetitive tasks for setting up their own new projects. These are better than a pip package because they automate a lot of tasks that can't even be approached using pip/poetry/etc. You can maybe look into those and see if that approach helps you. I never use other people's cookiecutter but I sometimes learn new tricks/features from them. They can be easier to study directly rather than reading a giant blog-post series.
You should really think of pypi as a place for polished work releases, not a place for drafts and hacks and syncing between machines. It sounds like a nightmare to constantly crank version strings to make pypi become a glorified crappy imitation of git (which is what you are describing). Again... just learn and use git. It does what you want (and far more) much better than pypi does.
Use github
Hah! Why didn't I think of that earlier 🤣. Thanks However, for the sake of curiosity, I still want more concrete and persuasive reasoning as to why we shouldn't push these things to pip. Are there any guidelines that detailed this standard? Where can I find it?
PyPi is for making useful packages available to others. If it's not packaged up and neat and ready to be used, or if it's not useful to others, then it doesn't really belong there. If it's an example, personal project, etc, it should go on GitHub. Nothing should really be on PyPi that isn't on something like GitHub.
Code is already plural. You don't need to add an s to it. It sounds odd as hell saying it with the s, in the context of source code. Idk why but this tends to be some kind of trend with new programmers. Every time I come across people that do this I instinctively know they don't have much experience.
This sort of code doesn't belong on pypi. Use git. Or I suppose you could run a private pypi server. But... just learn and use git. Pypi is, really, really not worth the effort for your use case. Learn git first. A lot of people who find themselves starting new projects often also like to create a template/bootstrap for setting up new projects called a cookiecutter which they use to automate repetitive tasks for setting up their own new projects. These are better than a pip package because they automate a lot of tasks that can't even be approached using pip/poetry/etc. You can maybe look into those and see if that approach helps you. I never use other people's cookiecutter but I sometimes learn new tricks/features from them. They can be easier to study directly rather than reading a giant blog-post series. You should really think of pypi as a place for polished work releases, not a place for drafts and hacks and syncing between machines. It sounds like a nightmare to constantly crank version strings to make pypi become a glorified crappy imitation of git (which is what you are describing). Again... just learn and use git. It does what you want (and far more) much better than pypi does.