Re: Sharing code between different projects?

Newsgroups	comp.lang.python
Date	2012-08-15 11:07 -0700
References	<CAF_E5JZ82ar7sWi5eOWe46N2wXVAX2QYUb5F9==0dxRbYMsEhg@mail.gmail.com> <CAH1RVigtOfZ5K34WOMqDPY0LrgWqRZg3y3g1=qRZY5v-qYgPCw@mail.gmail.com> <mailman.3258.1344935429.4697.python-list@python.org>
Subject	Re: Sharing code between different projects?
From	Miki Tebeka <miki.tebeka@gmail.com>
Message-ID	<mailman.3321.1345054060.4697.python-list@python.org> (permalink)

Show all headers | View raw

> In plus I'm using perforce which doesn't have any svn:externals-like
You can probably use views to this (http://www.perforce.com/perforce/r12.1/manuals/cmdref/o.views.html).

> Second problem is that one of the two projects has a quite insane
> requirement, which is to be able to re-run itself on a specific
> version depending on a value fetched from the database.
You can probably play with PYTHONPATH to do that.

> The third problem is that from the moment is not just me using these
> things, how can I be sure that changing something will not break
> someone else code?
That's always a problem with libraries you distribute, no matter what is the mechanism for distribution.

If you go the views/link way. You can link to tags instead of trunk (or the perforce equivalent) and then client can still to know "good" version. If you go the PyPi route, you can specify package version in setup.py dependencies (foo==0.10.2)

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Sharing code between different projects? andrea crotti <andrea.crotti.0@gmail.com> - 2012-08-14 10:10 +0100
  Re: Sharing code between different projects? Miki Tebeka <miki.tebeka@gmail.com> - 2012-08-15 11:07 -0700
  Re: Sharing code between different projects? Miki Tebeka <miki.tebeka@gmail.com> - 2012-08-15 11:07 -0700

csiph-web