setup.cfg

[pycodestyle]
max-line-length = 120
exclude = ./migrations,./venv,./venv3,./node_modules,./bower_components,./cache

[tool:pytest]
norecursedirs = node_modules bower_components
Use pycodestyle instead of PEP8 PEP8 was renamed to pycodestyle; this issue explains why: PyCQA/pycodestyle#466 This commit changes our tests to use pycodestyle instead of pep8. No changes to our code were required as a result. 2017-02-02 10:50:26 +00:00			`[pycodestyle]`
108536234: created users and roles data and domain model. You will need to run the /scripts/bootstrap.sh to create the database for test and the app. 2015-11-25 15:29:12 +00:00			`max-line-length = 120`
Exclude cache directory from pep8 2016-11-23 12:40:39 +00:00			`exclude = ./migrations,./venv,./venv3,./node_modules,./bower_components,./cache`
Use a Node-based tools for handling assets …or how to move a bunch of things from a bunch of different places into `app/static`. There are three main reasons not to use Flask Assets: - It had some strange behaviour like only - It was based on Ruby SASS, which is slower to get new features than libsass, and meant depending on Ruby, and having the SASS Gem globally installed—so you’re already out of being a ‘pure’ Python app - Martyn and I have experience of doing it this way on Marketplace, and we’ve ironed out the initial rough patches The specific technologies this introduces, all of which are Node-based: - Gulp – like a Makefile written in Javascript - NPM – package management, used for managing Gulp and its related dependencies - Bower – also package management, and the only way I can think to have GOV.UK template as a proper dependency …speaking of which, GOV.UK template is now a dependency. This means it can’t be modified at all (eg to add a global `#content` wrapper), so every page now inherits from a template that has this wrapper. But it also means that we have a clean upgrade path when the template is modified. Everything else (toolkit, elements) I’ve kept as submodules but moved them to a more logical place (`app/assets` not `app/assets/stylesheets`, because they contain more than just SASS/CSS). 2015-12-15 08:20:25 +00:00
bump test requirements to most recent 2016-09-09 16:29:30 +01:00			`[tool:pytest]`
Use a Node-based tools for handling assets …or how to move a bunch of things from a bunch of different places into `app/static`. There are three main reasons not to use Flask Assets: - It had some strange behaviour like only - It was based on Ruby SASS, which is slower to get new features than libsass, and meant depending on Ruby, and having the SASS Gem globally installed—so you’re already out of being a ‘pure’ Python app - Martyn and I have experience of doing it this way on Marketplace, and we’ve ironed out the initial rough patches The specific technologies this introduces, all of which are Node-based: - Gulp – like a Makefile written in Javascript - NPM – package management, used for managing Gulp and its related dependencies - Bower – also package management, and the only way I can think to have GOV.UK template as a proper dependency …speaking of which, GOV.UK template is now a dependency. This means it can’t be modified at all (eg to add a global `#content` wrapper), so every page now inherits from a template that has this wrapper. But it also means that we have a clean upgrade path when the template is modified. Everything else (toolkit, elements) I’ve kept as submodules but moved them to a more logical place (`app/assets` not `app/assets/stylesheets`, because they contain more than just SASS/CSS). 2015-12-15 08:20:25 +00:00			`norecursedirs = node_modules bower_components`