On 29/10/13 10:08 +0530, Sharoon Thomas wrote: > > On Oct 29, 2013, at 4:35 AM, Cédric Krier <[email protected]> wrote: > > > I'm thinking about how we could publish on PyPI (or a custom Tryton > > index) development packages. After the doc, it seems there is a "==dev" > > keyword for that but I did not find how to register such «version» nor > > how to make it fetch the source from the mercurial repository. > > So I'm wondering if anyone has such knowledge? > > AFAIK you have to publish (upload) the dev packages also to PyPI. > > The dev packages are identified by the trailing dev [1] and pre releases > by alpha, beta or candidate [2] releases as specified by PEP440. > > Since pip version 1.4.1 `pip install package` installs the most recent > final release [3] while the `--pre` flag [4] will install the pre release > versions including the development ones. > > However, if installing from a repository is the requirement, pip supports > that too [5].
Yes but how to you publish that on PyPI? I guess using the download_url? > I don’t think the Tryton versioning model (odd and even) is compliant > with PEP440 (and hence PEP426). I was thinking about tunning setup.py to append ".dev" on odd number, probably something like: 3.1.dev -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpz9sTrswzS7.pgp
Description: PGP signature
