Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Better releases #593
In the process of making a release, thought I'd add some better documentation (rather than just following a hodgepodge of notebook and ipython release docs, and also wanted to add explicit checks for the version number to avoid nonvalid version numbers that have caused problems in the past.
@Carreau I figure you'll care the most of everyone about this.
Just want to get this settled and then I'll make the next release. I have these thoughts every time I want to make a release and this time I just wanted to deal with some of the loose ends that are always left dangling before making the actual release.
Also, technically we weren't using a pep440 compliant version number before I don't know why it wasn't causing a problem but hey, no harm in doing so just briefly before releasing.
Since I know you like to understand things, I took a quick look at what was going on. Having
If you give exec just one namespace, it defines things in globals, which is more predictable - functions keep a reference to the globals dict where they were defined, and use that when looking up variables.