Re: enhance release experience
Luca Fabbri <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAGfGq=Z52uvK84We3L7PNfGgdUHYv3XW4Upz_qc1MzP3CNzhSg@mail.gmail.com> |
On Tue, Nov 18, 2014 at 12:52 AM, David Glick (Plone) <david.glick-z4DKO/[email protected]> wrote: > On 11/17/14, 3:24 PM, Jens W. Klein wrote: >> so I just wanted to ... >> >> release. >> >> and i hit a snakepit. >> >> It seems today I found two thing we NEVER ever should do in a python >> package: >> >> 1) >> use symlinks. This will fail. If not now, then in future. But it will. >> It just increases the chance of a brown bag release enormous. >> >> 2) >> use a MANIFEST.in. Seriously. It seems we just do NOT need it at all. >> Delete it. Current setuptools seems to work fine w/o, includes all >> files, given a release is done from a tag checkout (as we do with >> zestreleaser, jarn.mkrelease, ...). Just add only files meant for >> release in git, manage your .gitignore careful. Then - using >> include_package_data=True, all is in. >> see also https://twitter.com/narocz/status/534404233827983360 >> > This is true now even if you don't have setuptools-git in your Python > environment? That used to be necessary. > No, in my experience in that case it will fail. Sadly I see lot of people that not use a MANIFEST because they don't need it in their personal programming environment. We need MANIFEST.in (and check-manifest is a super useful tool). -- -- luca twitter: http://twitter.com/keul linkedin: http://linkedin.com/in/lucafbb blog: http://blog.keul.it/ ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk