Re:Metaflask - A repository to organize the Flask ecosystem
by frakkingcylons on Thursday July 03, 2014 @10:35AM
(#7983266)
This is a very welcome development in the Flask world. It seems that Armin Ronacher (mitsuhiko) found himself in a situation where things outside of open-source projects started demanding more of his time [0] while issues and PRs started accumulating on Flask, Flask-SQLAlchemy etc. You can't really blame him for being overwhelmed by it, and thankfully, in the past day some progress has been made [1] and maintainers are being selected.
Re:Metaflask - A repository to organize the Flask ecosystem
by pekk on Thursday July 03, 2014 @12:33PM
(#7984062)
It's only a polite fiction that things outside of open-source projects overwhelmed him. Your link itself says that he doesn't want to work on his open source Python projects because of Python 3 taking his motivation.
Re:Metaflask - A repository to organize the Flask ecosystem
by pyre on Thursday July 03, 2014 @11:11AM
(#7983527)
> Whether you are accepted as member or not is arbitrary and the decision is made in an even more arbitrary process by the members of Metaflask. Rejections can be challenged by flamewars on the closed issue.
Re:Metaflask - A repository to organize the Flask ecosystem
by Walkman on Thursday July 03, 2014 @01:44PM
(#7984536)
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.
Re:Metaflask - A repository to organize the Flask ecosystem
by pyre on Thursday July 03, 2014 @03:25PM
(#7985106)
I'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.
Re:Metaflask - A repository to organize the Flask ecosystem
by iurisilvio on Thursday July 03, 2014 @06:20PM
(#7986211)
Most 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.
[0]: http://lucumr.pocoo.org/2013/11/28/emotional-programming/
[1]: https://github.com/mitsuhiko/flask-sqlalchemy/issues/197#iss...
Think of it as CTAN / CPAN / PyPI / etc specifically for Flask extensions, minus the distribution angle.
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.