- adds `from flaskr import app` to top-level in flaskr module
- effect is that `export FLASK_APP=flaskr` works over the more verbose
`export FLASK_APP=flaskr.flask`
- see the readme for how to run
- all tests are passing with `py.test` or `python setup.py test` (in
venv)
* Update minitwit & improve testing for examples
* Related to #1945
* Re-works minitwit to be installed and run as:
pip install --editable .
export FLASK_APP=minitwit.minitwit
export FLASK_DEBUG=1
flask initdb
flask run
* added flaskr and minitwit to norecursedirs
* tests not properly run when using pytest standards
* see: http://stackoverflow.com/questions/38313171/configuring-pytest-with-installable-examples-in-a-project
* Both flaskr and minitwit now follow pytest standards.
* Tests can for them as `py.test` or `python setup.py test`
* Update minitwit readme
* updates the instructions for running
* Fixes for updating the minitwit example
- This reverts the changes to the *docs/* (I will file separate PR).
- Running the app is now: `export FLASK_APP=minitwit` & `flask run`
(After installing the app)
* Remove unnecessary comma from flaskr/setup.py
* Converts example/flaskr to have a setup.py
Makes the flaskr app easier to run, ex. workflow:
- pip install --editable .
- export FLASK_APP=flaskr.flaskr
- flask initdb
- flask run
Testing is also easier now:
- python setup.py test
* Fixed an import error in flaskr/tests
- the statement `import flaskr` caused errors in python3
- `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1
* Better project structure and updates the docs
- Re-factors *flaskr*'s project structure a bit
- Updates docs to make sense with the new structure
- Adds a new step about installing Flask apps with setuptools
- Switches first-person style writing to second-person (reads better IMO)
- Adds segments in *testing.rst* for running tests with setuptools
* Remove __init__.py from tests
- py.test recommends not using __init__.py
* Fix testing import errors