From c99aa7279b67350fb9175aeb4685c92d0d1ac042 Mon Sep 17 00:00:00 2001
From: Eli Uriegas <seemethere101@gmail.com>
Date: Wed, 15 Feb 2017 20:47:34 -0600
Subject: [PATCH] Moves sanic/sanic.py to sanic/app.py

Functionality wise this won't change much for most users, unless you
were directly importing from `sanic.sanic` in which case I am sorry if
you're affected by this.

Main motivation was because jedi autocompletion didn't work with this
and we were using relative imports to compensate for the fact that
having a module inside of your module with the same name creates major
namespace problems.
---
 sanic/__init__.py          | 2 +-
 sanic/{sanic.py => app.py} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename sanic/{sanic.py => app.py} (100%)

diff --git a/sanic/__init__.py b/sanic/__init__.py
index 90bb85d0..364ee715 100644
--- a/sanic/__init__.py
+++ b/sanic/__init__.py
@@ -1,4 +1,4 @@
-from .sanic import Sanic
+from .app import Sanic
 from .blueprints import Blueprint
 
 __version__ = '0.3.1'
diff --git a/sanic/sanic.py b/sanic/app.py
similarity index 100%
rename from sanic/sanic.py
rename to sanic/app.py