Tree: 5068ff9913

0.12-maintenance

1.0-maintenance

master

rtd

0.1

0.10

0.10.1

0.11

0.11.1

0.12

0.12.1

0.12.2

0.12.3

0.12.4

0.2

0.3

0.3.1

0.4

0.5

0.6

0.6.1

0.7

0.7.1

0.7.2

0.8

0.8.1

0.9

1.0

1.0.1

1.0.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '5068ff9913'

${ noResults }

Commit Graph

2 Commits (5068ff991362b6f4aefe86255c1886509bf672a3)

Author	SHA1	Message	Date
Kyle Lawlor	fa087c8929	Fixes import statement in flaskr (#2068) ... - `from flaskr.flaskr import app` in flaskr/__init__.py causes an import error with Python 2 - The relative import now used works for py2 and py3	8 years ago
Kyle Lawlor	17d4cb3828	Address #1902: Converts example/flaskr to have a setup.py (#1945) ... * 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	9 years ago