enhance release experience
"Jens W. Klein" <jens-/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Organization | Klein & Partner KG |
| Message-ID | <[email protected]> |
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 Jens -- Klein & Partner KG, member of BlueDynamics Alliance ------------------------------------------------------------------------------ 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