Peo wrote:
Is there some other smart way to do acheive this?
Just turn them info python packages, and use buildout, pip or some other
python package management tool to create the versions.
You may, of course, just be able to svn the lot of them...
(then you don't need to worry about numberin
In message
<2cb0c88b-58ea-4704-8578-2ebd766f1...@t10g2000yqg.googlegroups.com>, Peo
wrote:
> My current plan is to call the library something like 'foo1' and
> import it into scripts like 'import foo1 as foo'. Releases that change the
> API would be installed as 'foo2', 'foo3' and so on. This wo
On Jul 24, 8:56 am, Peo wrote:
> Hi,
>
> I'm writing a library for doing sysadmin tasks at my workplace. These
> kind of
> scripts have a tendency to live for decades and I want to make sure
> that I don't break anything when I'm updating the library.
>
> My current plan is to call the library som
