On May 13, 2009, at 7:17 PM, Istvan Albert wrote:
> > > On May 13, 9:04 pm, Marek Szuba <mare...@gmail.com> wrote: > >> I am happy to say that the second option works just fine! Just >> download >> and install setuptools-git (http://pypi.python.org/pypi/setuptools-git >> ). >> Beats adding and maintaining a manifest file if your ask me... >> However, > > You only need to create a manifest template, a so called MANIFEST.in. > This template supports file patterns for inclusion and exclusion, such > as tests/*.py etc. so it is not as complicated as one might think. It > is also conceivable to have data packaged that is not tracked in git. I tend to agree with Istvan. What is the idea of setuptools-git? Just to take every file that's checked into git, and automatically add it to the manifest for the package? That seems like overkill... With appropriate wildcards, keeping a MANIFEST.in updated should not be hard, and seems like an appropriate conscious step whenever we cut a release (i.e. to consider what files we actually want going into the package... not necessarily all the files in git, and quite possibly including files that aren't in git (classic example: the pyrex generated C files which allow people to build pygr even if they don't have pyrex installed...) -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
