librelist archives

ANN: Flask 0.5, Calvados Released

From:

Armin Ronacher

Date:

2010-07-06 @ 14:31

Hi everybody,

I just released Version 0.5, codename Schnaps of Flask, the micro
webframework based on Werkzeug, Jinja2 and good intentions.

What's new:

   * fixed a bug with subdomains that was caused by the inability to
     specify the server name.  The server name can now be set with the
     SERVER_NAME config key.  This key is now also used to set the
     session cookie cross-subdomain wide.
   * autoescaping is no longer active for all templates. Instead it is
     only active for .html, .htm, .xml and .xhtml.  Inside templates
     this behaviour can be changed with the autoescape tag.
   * refactored Flask internally. It now consists of more than a single
     file.
   * flask.send_file() now emits etags and has the ability to do
     conditional responses builtin.
   * (temporarily) dropped support for zipped applications.  This was a
     rarely used feature and led to some confusing behaviour.
   * added support for per-package template and static-file directories.
   * removed support for create_jinja_loader which is no longer used in
     0.5 due to the improved module support.
   * added a helper function to expose files from any directory.


Links:

     Online Documentation: http://flask.pocoo.org/docs/
     Downloadable PDF: http://flask.pocoo.org/docs/flask-docs.pdf
     Website: http://flask.pocoo.org/
     On Github: http://github.com/mitsuhiko/flask
     PyPI Record: http://pypi.python.org/pypi/Flask


Grab it from PyPI while it's hot: http://pypi.python.org/pypi/Flask/0.5


Regards,
Armin

Hi,

And two hours later: the 0.5.1 point release.  Why that?  Because when 
you had a module named A without templates in A but the application's 
template folder in the subfolder A, Flask would have chopped of the 
leading "A/".  Fixed that now and expanded the testsuite.

Sorry for the inconveniences caused.


Regards,
Armin

Le 06/07/2010 16:31, Armin Ronacher a écrit :
> Version 0.5, codename Schnaps of Flask

Wrong codename?

Hi,

On 7/6/10 4:32 PM, Simon Sapin wrote:
> Wrong codename?
That's what happens when you recycle old announcement mails.  At least I 
got it in the subject right.


Regards,
Armin (who yet has to master the release process)

Also, shouldn’t "modules can now have their own templates and static 
files" be in What’s new?

Static files were always a pain with the Django admin (since you had to 
manually copy or symlink them). This feature plus url_for means that we 
can now have modules that come pre-packaged with their own static files 
and expect it to Just Work.

Regards,
-- 
Simon

I don't know if it will "just work" because it will break when using
something like apache or cherokee, that is unless your using
x-sendfile then it *might* work if permissions are OK. I don't see any
way around using a production web server and NOT having to simlink the
flask-ext static files.

--
Thadeus





On Tue, Jul 6, 2010 at 9:45 AM, Simon Sapin <simon.sapin@exyr.org> wrote:
> Also, shouldn’t "modules can now have their own templates and static
> files" be in What’s new?
>
> Static files were always a pain with the Django admin (since you had to
> manually copy or symlink them). This feature plus url_for means that we
> can now have modules that come pre-packaged with their own static files
> and expect it to Just Work.
>
> Regards,
> --
> Simon
>

Hi,

Le 06/07/2010 17:16, Thadeus Burgess a écrit :
> I don't know if it will "just work" because it will break when using
> something like apache or cherokee, that is unless your using
> x-sendfile then it*might*  work if permissions are OK. I don't see any
> way around using a production web server and NOT having to simlink the
> flask-ext static files.
>    

When X-Sendfile is not enabled, Flask uses wsgi.file_wrapper to send 
static files. Of course this is not as efficient as having your HTTP 
server serve these files directly (which required more configuration or 
symlinks), but if you have a server that support it (eg. mod_wsgi) this 
may be good enough.

Regards,
-- 
Simon Sapin