Repository: sanic-org/sanic

Issue:
New release on Pypi ?
Hello,

I was looking for a tool to autoreload my code when I develop and I found this commit : https://github.com/channelcat/sanic/commit/52c2a8484e6aa5fa13aaade49e1f2597dd006e15

So it seems Sanic already integrates it since December 07, 2017. But the the latest version on Pypi dates from the day before (https://github.com/channelcat/sanic/commit/1ea3ab7fe8ab03a6ddf4d75a3de8cb719f4c584c) : https://pypi.org/project/Sanic/#history

Is-it possible to release a new version on Pypi please ? Other features (like the UUID support in routes) are also interesting :)

Thanks in advance !


Discussion:
pip install https://github.com/user/repo.git@branch


@c-goosen Yes it's what we are doing now, but I still think `pip install sanic` is more convenient than `pip install https://github.com/channelcat/sanic.git@master` :pensive:

Six months without a new release on Pypi for an awesome project like **Sanic**... People who read blog posts on this framework will just try `pip install sanic`, not the full path including the branch.
There is already another thread about requesting a new Sanic release, here:
https://github.com/channelcat/sanic/issues/1170

Well we should discuss integrating with circle CI or other tools with a scheduled release cycle. 
@c-goosen 
What is your reasoning behind that? How would a scheduled release cycle benefit the Sanic project?
I think, it would be just enough to make new release )
Guess I'll go ahead and +1 this, if only for the ipv6 support.
Who is responsible?
@seemethere seems to be the one to tag and release, not sure if that also carries the responsibility to push to pypi.
Personally, I don't like having to specially get the Sanic repo for support for something like nested Blueprints which has been a feature for a while now.
https://github.com/channelcat/sanic/commit/a10d7469cdeeaa4bdd94d508520e84255bdddb0b
I'm having issues pushing for adoption of Sanic over Flask in my organisation at the moment mostly because of the lack of releases. The lack of a release cycle undermine the confidence in the product. 

I've read the few different issues opened about the lack of releases and I still cannot find a good reasoning as to why Sanic stopped doing releases. So what's up?
@channelcat @seemethere Any ideas here?
@r0fls is one of the more active in 2018. Can you make a new release? If no one can make this, maybe we have to migrate for an organization in other repo. @yunstanford @seemethere 
I tried and I get this message 😢 :

```
HTTPError: 403 Client Error: The user 'r0fls' isn't allowed to upload to project 'Sanic'. See https://pypi.org/help/#project-name for more information. for url: https://upload.pypi.org/legacy/
```

Seems pypi is hoping to fix this eventually: https://github.com/pypa/warehouse/issues/1506

In the meantime, only @seemethere can do a release. @seemethere any chance you want to change your pypi to a password that you can share with me so that I can do a release and calm the masses?
@r0fls 
This small PR https://github.com/channelcat/sanic/pull/1286 will need to be merged before a release, because auto_reload is currently broken for all users except those on Mac OS.

@r0fls you don't need to get the password. @seemethere will just add you to collaborators on PyPI :)

Example:
![image](https://user-images.githubusercontent.com/433434/44248166-f0a99200-a223-11e8-94df-12858b52e06d.png)

Also would be good to get https://github.com/channelcat/sanic/pull/1179 and https://github.com/channelcat/sanic/pull/1278 merged before a release, but I don't want to set a precedent of everyone pleading to get their PRs merged before the release.
It'd be great if we have a team/official process for operating release.

I'd also like to see this https://github.com/channelcat/sanic/pull/1179 merged in so we could get feedbacks.
I'll be quite honest..... I've heavily adopted sanic in production, but did so in a way I could easily switch it out if I need to. The lack of release schedule has me and my team worried and I've considered the effort to remove it. I already [took it out of my gateway service](
https://github.com/channelcat/sanic/issues/1264#issuecomment-413227303). 

Seeing this move to an organization would give the project a lot. Sanic's biggest weakness (in my opinion) right now is the lack of project direction. This could give some great momentum to an otherwise great framework.

I would be happy to help whatever organizational work would need to be done to accomplish this.
@ahopkins agree, moving to an organization helps a lot.
I would be glad to help as well.
I would also be willing to assist, if needed.
Cutting a release today (@r0fls will handle the release notes), will contact @channelcat to see if we can move this to an organization so we can get more people who can help out with the project.

Resolving patch:
diff --git a/sanic/__init__.py b/sanic/__init__.py
--- a/sanic/__init__.py
+++ b/sanic/__init__.py
@@ -1,6 +1,6 @@
 from sanic.app import Sanic
 from sanic.blueprints import Blueprint
 
-__version__ = '0.7.0'
+__version__ = '0.8.0'
 
 __all__ = ['Sanic', 'Blueprint']


Test patch: