Re: [Biopython] Biopython 1.73 release plans
Peter Cock <[email protected]>
| Newsgroups | gmane.comp.python.bio.general |
|---|---|
| Message-ID | <CAKVJ-_4WxwDZr7YHOXjBbHBbOK94vup=4-quCRxannks5M04sw@mail.gmail.com> |
So far so good, release tagged and tar-ball on PyPI, along with Mac and Linux wheels: https://pypi.org/project/biopython/1.73/ Windows wheels underway, will need some tweaking for Python 3.7 which we didn't have last time round. This time no last minute surprises from epydoc, just from latex - currently neither of these steps is under continuous integration. Both tools are a bit of a pain to install on a modern system, and would add to the TravisCI load. Peter On Tue, Dec 18, 2018 at 11:39 AM Peter Cock <[email protected]> wrote: > > Hello all, > > I'm going to start the release process now, fingers crossed > this goes smoothly. > > Peter > > On Thu, Nov 15, 2018 at 2:29 PM Peter Cock <[email protected]> wrote: > > > > Dear Biopythoneers, > > > > Typo in title fixed: It is time for Biopython 1.73 > > > > I have merged the Sphinx API branch, and we've > > fixed a regression on Python 3.7 (currently only > > tested on AppVeyor, but there has been recent > > progress from TravisCI about offering this), and > > filled out the NEWS.rst file a bit. > > > > I have logged a couple of online-only test issues with > > Entrez which we would ideally fix first: > > > > https://github.com/biopython/biopython/issues/1848 > > https://github.com/biopython/biopython/issues/1849 > > > > Once again, are there any other outstanding issues > > or pull requests worth waiting for? > > > > If not I hope to do the release as soon as I can > > find a clear (or nearly clear) day to do so. (It does > > not usually take that long, but there can still be > > surprises) > > > > Thanks all, > > > > Peter > > > > On Wed, Oct 24, 2018 at 9:31 AM Peter Cock <[email protected]> wrote: > > > > > > Dear Biopythoneers, > > > > > > I think it is time to roll out our next release, Biopython 1.73. > > > Are there any outstanding issues or pull requests worth > > > waiting for? > > > > > > Personally, I would like to merge my Sphinx API work, > > > https://github.com/biopython/biopython/pull/1803 - and > > > then as part of doing the release, make this version of > > > the documentation available along side our traditional > > > epydoc based API documentation. See also: > > > > > > http://mailman.open-bio.org/pipermail/biopython/2018-October/016549.html > > > > > > Regards, > > > > > > Peter _______________________________________________ Biopython mailing list - [email protected] http://mailman.open-bio.org/mailman/listinfo/biopython