|
Hi René and others
Now after pyweek 25 I have some time to improve my libs. I would need a little help (I know, its not directly pygame related and if you want to redirect me to the python list I'll be fine with it): [1] What would be your suggestions to make the stuff more useful? [2] Any tips on (free) CI builds? [3] Any tips on packaging for pip? [4] Any tips for the documentation? [5] Would you break up libs into smaller, maybe partial parts that are pip installable so they can be installed independently? If so, should each have its own repo or not (keeping it in the same repo in sub directories)? [6] Might need some improvements, but some time ago I made this and tried to use it everywhere: https://bitbucket.org/dr0id/cookiecutter-pypackage-hg/src/default/ [7] Any hints for best-practices? [8] One thing that has bothered me along time and I have not found any good answer yet is following: pip installable packages are good for developers while coding and developing. But then, when I want to 'ship' or 'distribute' some program I'm not so sure that is the way to go. Because I think there should be a distinction between a library (that you install in site-packages) and a 'executable' which I might want to install somewhere else (otherwise I would not know hot to run it, maybe using '-m'?). [9] Also there is the trouble with versions of the libs (I know, use virtualenv, but that seems laborious) if to 'programs' need different versions of the same lib. So one way around this is to ship all the needed libs with the program (so no imports from site-packages used). [10] This trouble is visible in some of my libs because sometimes I have the lib and some 'tools' for it and it seems to me that the tools should not go into site-packages. But maybe I got it all wrong or don't know best practices for python programs. Maybe someone can point me to a tutorial or help clarify those points. ~DR0ID On 07.04.2018 10:29, René Dudfield wrote:
|