I'm curious in what context that particular change is needed and why "check out the repo" isn't appropriate there.
This is *not* a rhetorical question. The answer may very well satisfy me. Making another release only takes me a few minutes -- deciding *when* to do it and what version number to use is more work. I'd actually like to have some kind of jump in the version to indicate correspondence with the Python 3.4.0 release (even though it would be the same code as 0.4.1). In the future we can then do Tulip releases that track exactly what's in future Python 3.4.x releases, from a Tulip maintenance branch. We also AFAIK haven't done any review of which Tulip changes are or aren't appropriate to merge into the Python 3.4 maintenance branch -- currently nothing has been merged into it, but I suspect that's just because we've been busy. (Everything's been merged into the CPython default branch, which will become Python 3.5.) On Mon, Mar 24, 2014 at 9:32 AM, Victor Stinner <[email protected]>wrote: > 2014-03-24 15:58 GMT+01:00 Andrew Svetlov <[email protected]>: > > Would do you like to make a new release? > > PyPI has 0.4.1 as last version, that is a quite obsolete. > > I would not call "0.4.1" obsolete, since it's the same code than > Python 3.4.0 and it was released a few weeks ago. It's still young :-) > > FYI I already merged this change in Trollius, so I'm ready for a new > Trollius release. > > Victor > -- --Guido van Rossum (python.org/~guido)
