3 ms·
The guy should set up a Github organization and use one repo for every project. Organizations can have members also, and one project is not cluttered with anoth
by Walkman 12y ago
The guy should set up a Github organization and use one repo for every project. Organizations can have members also, and one project is not cluttered with another one's issues.
- pyre 12y agoI'm not sure you understand. This repository is just a directory containing metadata; basically just a listing of Flask extensions, and their stewardship / author information. There is no intention to pull all Flask extensions into a single monolithic repository. Think of it as CTAN / CPAN / PyPI / etc specifically for Flask extensions, minus the distribution angle.
- collyw 12y agoCan I assume they play nicely together if they are listed, or should I stick with Django for that sort of thing?
- iurisilvio 12y agoMost extensions play nicely together and even help you to combine them. Flask doesn't have an equivalent to Django Apps. An extension is not an independent app, you have to integrate it with your Flask app. This is probably the only thing I miss in Flask.
- bobbyi_settv 12y agoBlueprints are Flask's version of Django Apps.