Post At60ZkUlLfZ2GEJBdQ by bignose@fosstodon.org
 (DIR) More posts by bignose@fosstodon.org
 (DIR) Post #At60ZkUlLfZ2GEJBdQ by bignose@fosstodon.org
       2025-04-14T22:43:02Z
       
       0 likes, 0 repeats
       
       You've got conflicting requirements here @kevin.By depending on third-party libraries, you do need an install step, which installs your Python program along with its dependencies, as a coherent whole.So I think you can't also have "the program doesn't need to be installed anywhere"; yeah, it does, otherwise it's just a file sitting on the disk. It needs to be installed before the recipient can use it as a program.
       
 (DIR) Post #At60lRjMwL1vXTiaYa by bignose@fosstodon.org
       2025-04-14T22:45:09Z
       
       0 likes, 0 repeats
       
       You've avoided this, by *manually* doing the job of an installer (getting the search path right, installing dependency modules, ensuring other dependencies are set up).The recipient of your repository can't reliably be expected to have that; all they've got is your files, somewhere arbitrary on their filesystem. You need to arrange that reliable environment, with an build-and-install step. Typically you configure that with the Package Metadata file, 'pyproject.toml'.@kevin
       
 (DIR) Post #At6283RLWBh8ojdGnA by philip@mastodon.mallegolhansen.com
       2025-04-14T23:00:24Z
       
       0 likes, 0 repeats
       
       @bignose @kevin I’m reading it as Kevin saying it’s not a requirement to create an *installable* version of the tool for third parties to use.