Hey Jenny, For the time being, we'll leave the Pygr dependency as one that has to be resolved by the user, i.e. we won't include it in setup.py just yet. As soon as Chris releases the 0.8 version of Pygr, we'll test your ensembl code and make sure they play nice together, then we can include Pygr_v0.8 as a dependency in setup.py.
For making code publicly available, the Cheeseshop is one option, the Sourceforge site is another. It's up to the author how they want to make their code available. I don't think we should but the ensembl code on Chris' Pygr project site since that's not really where it belongs and would almost certainly be moved later on. We can look at putting your code on the Cheeseshop after we have version 0.8 of Pygr. Until then, "publicly available" means people can email ya for the tarball. :) Cheers, Rob On Sat, Sep 6, 2008 at 11:05 PM, Jenny Qing Qian <[EMAIL PROTECTED]>wrote: > I plan to submit pyensembl-0.0.1-py2.5.egg. It does not contain any Pygr > code. But then what version of pygr should I include in the > install_requires=[ > 'setuptools', > ], > of the setup.py? I think my API is building on a pygr version between 0.7 > and 0.8... Or shall I just go ahead with Pygr 0.8 in the install_requires? > Also, can anyone tell me why Pygr is not in the Cheese Shop? > > thanks, > > jenny > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
