Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!xlned.com!feeder7.xlned.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Tue, 14 Aug 2012 16:34:23 +0200
From: Jean-Michel Pichavant <jeanmichel@sequans.com>
User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100328)
MIME-Version: 1.0
To: andrea crotti <andrea.crotti.0@gmail.com>
Subject: Re: Sharing code between different projects?
References: <CAF_E5JZ82ar7sWi5eOWe46N2wXVAX2QYUb5F9==0dxRbYMsEhg@mail.gmail.com>
In-Reply-To: <CAF_E5JZ82ar7sWi5eOWe46N2wXVAX2QYUb5F9==0dxRbYMsEhg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: python-list <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3278.1344954871.4697.python-list@python.org>
Lines: 61
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:27045

andrea crotti wrote:
> I am in the situation where I am working on different projects that
> might potentially share a lot of code.
>
> I started to work on project A, then switched completely to project B
> and in the transiction I copied over a lot of code with the
> corresponding tests, and I started to modify it.
>
> Now it's time to work again on project A, but I don't want to copy
> things over again.
>
> I would like to design a simple and nice way to share between projects,
> where the things I want to share are simple but useful things as for
> example:
>
> class TempDirectory:
>     """Create a temporary directory and cd to it on enter, cd back to
>     the original position and remove it on exit
>     """
>     def __init__(self):
>         self.oldcwd = getcwd()
>         self.temp_dir = mkdtemp()
>
>     def __enter__(self):
>         logger.debug("create and move to temp directory %s" % self.temp_dir)
>         return self.temp_dir
>
>     def __exit__(self, type, value, traceback):
>         # I first have to move out
>         chdir(self.oldcwd)
>         logger.debug("removing the temporary directory and go back to
> the original position %s" % self.temp_dir)
>         rmtree(self.temp_dir)
>
>
> The problem is that there are functions/classes from many domains, so it
> would not make much sense to create a real project, and the only name I
> could give might be "utils or utilities"..
>
> In plus the moment the code is shared I must take care of versioning and
> how to link different pieces together (we use perforce by the way).
>
> If then someone else except me will want to use these functions then of
> course I'll have to be extra careful, designing really good API's and so
> on, so I'm wondering where I should set the trade-off between ability to
> share and burden to maintain..
>
> Anyone has suggestions/real world experiences about this?
>   
I can think of logilab-common (http://www.logilab.org/848/)

Having a company-wide python module properly distributed is one to 
achieve your goal. Without distributing your module to the public, 
there's a way to have a pypi-like server runnning on your private network :

http://pypi.python.org/pypi/pypiserver/

JM

Note : looks like pypi.python.org is having some trouble, the above link is broken. Search for recent announcement about pypiserver.