librelist archives

[ANN] Werkzeug 0.7 Released

From:

Armin Ronacher

Date:

2011-07-24 @ 15:57

Hi,

Finally Werkzeug 0.7 is released.  While it's a huge update in terms of
new features and internally stuff cleaned up, the real great step
forward here is the new release cycle.

Werkzeug and Flask will now attempt a two to four month release cycle
and release side-by-side.  We also want to clean up internal API
mistakes that make porting to Python 3 harder than necessary.  We will
be very careful with deprecations and provide scripts that generate
diffs for necessary updates we cannot workaround (similar to how the
import rewriting with Werkzeug 0.7 already works and how blueprint
updates worked in Flask 0.7).

For the full list of what is new check out the changelog in the
documentation and the tarball.

Most important improvements:

- greatly improved routing system (better ordering, default handling
  and support for multiple domains)
- Very basic Range/IfRange/ContentRange support
- improved multipart parser
- some changes that should aid an upgrade to Python 3


Regards,
Armin

Thanks Armin! Very useful stuff. I also noticed that the Werkzeug
tutorial<http://werkzeug.pocoo.org/docs/tutorial/>is a new app called
Shortly <https://github.com/mitsuhiko/werkzeug/tree/master/examples/shortly>.
I think the new tutorial is a better introductory guide. It's simpler and
really well written. The old one was good too in that it taught software
engineering priciples. I'm learning a lot from reading your code.

Chris

On Sun, Jul 24, 2011 at 5:57 AM, Armin Ronacher <armin.ronacher@active-4.com
> wrote:

> Hi,
>
> Finally Werkzeug 0.7 is released.  While it's a huge update in terms of
> new features and internally stuff cleaned up, the real great step
> forward here is the new release cycle.
>
> Werkzeug and Flask will now attempt a two to four month release cycle
> and release side-by-side.  We also want to clean up internal API
> mistakes that make porting to Python 3 harder than necessary.  We will
> be very careful with deprecations and provide scripts that generate
> diffs for necessary updates we cannot workaround (similar to how the
> import rewriting with Werkzeug 0.7 already works and how blueprint
> updates worked in Flask 0.7).
>
> For the full list of what is new check out the changelog in the
> documentation and the tarball.
>
> Most important improvements:
>
> - greatly improved routing system (better ordering, default handling
>  and support for multiple domains)
> - Very basic Range/IfRange/ContentRange support
> - improved multipart parser
> - some changes that should aid an upgrade to Python 3
>
>
> Regards,
> Armin
>

Quick noob question.

is Flask 0.7 compatible with Werkzeug 0.7?

Thanks,

~Jonathan C.


On Sun, Jul 24, 2011 at 1:11 PM, Chris Aliipule <guitarift@gmail.com> wrote:

> Thanks Armin! Very useful stuff. I also noticed that the Werkzeug 
tutorial<http://werkzeug.pocoo.org/docs/tutorial/>is a new app called
> Shortly<https://github.com/mitsuhiko/werkzeug/tree/master/examples/shortly>.
> I think the new tutorial is a better introductory guide. It's simpler and
> really well written. The old one was good too in that it taught software
> engineering priciples. I'm learning a lot from reading your code.
>
> Chris
>
>
> On Sun, Jul 24, 2011 at 5:57 AM, Armin Ronacher <
> armin.ronacher@active-4.com> wrote:
>
>> Hi,
>>
>> Finally Werkzeug 0.7 is released.  While it's a huge update in terms of
>> new features and internally stuff cleaned up, the real great step
>> forward here is the new release cycle.
>>
>> Werkzeug and Flask will now attempt a two to four month release cycle
>> and release side-by-side.  We also want to clean up internal API
>> mistakes that make porting to Python 3 harder than necessary.  We will
>> be very careful with deprecations and provide scripts that generate
>> diffs for necessary updates we cannot workaround (similar to how the
>> import rewriting with Werkzeug 0.7 already works and how blueprint
>> updates worked in Flask 0.7).
>>
>> For the full list of what is new check out the changelog in the
>> documentation and the tarball.
>>
>> Most important improvements:
>>
>> - greatly improved routing system (better ordering, default handling
>>  and support for multiple domains)
>> - Very basic Range/IfRange/ContentRange support
>> - improved multipart parser
>> - some changes that should aid an upgrade to Python 3
>>
>>
>> Regards,
>> Armin
>>
>
>

On 25 July 2011 06:45, Jonathan Chen <tamasiaina@gmail.com> wrote:

> Quick noob question.
>
> is Flask 0.7 compatible with Werkzeug 0.7?
>
>
Yes.  This from Armin:
http://twitter.com/#!/mitsuhiko/status/95158969961680896

Great news Armin!  I've just recently begun using Flask/Werkzeug for my
latest App Engine projects and have loved what I've used of them so far.  I
really enjoy the through and well written documentation.

As my experience with the framework improves, I'm going to work on improving
the App Engine compatibility of Flask, especially now that Tipfy (based on
Werkzeug) has taken a back seat to webapp2 (WebOb based).  The new Range
support in Werkzeug should help, and I'm going to look at Tipfy's code base
to port over some of the work Rodrigo had done in Tipfy for supporting App
Engine services (deferred, blobstore, etc).  Some of the trickier pieces are
outlined here:
http://stackoverflow.com/questions/6774371/flask-vs-webapp2-for-google-app-engine
.

I'll also work on writing some snippets for running webapp2 side by side
with Flask using application dispatching for the times is makes it easier
(and until I can get around to porting/writing the missing pieces).

My contributions will be slow for a while until I finish up some pending
projects and most of my contributions will come from me scratching my own
itch.  For instance, I have a Flask extension to support jqGrid easy
(pagination/search/etc).  I need to clean it up some, and decide the best
way to expose the json serializer that it currently uses in the package (not
the best place for it, and it's just a slightly modified version of what's
available here -

http://code.google.com/p/google-app-engine-samples/source/browse/trunk/geochat/json.py
)

Once again, great work as always.

-Sean

On Sun, Jul 24, 2011 at 11:57 AM, Armin Ronacher <
armin.ronacher@active-4.com> wrote:

> Hi,
>
> Finally Werkzeug 0.7 is released.  While it's a huge update in terms of
> new features and internally stuff cleaned up, the real great step
> forward here is the new release cycle.
>
> Werkzeug and Flask will now attempt a two to four month release cycle
> and release side-by-side.  We also want to clean up internal API
> mistakes that make porting to Python 3 harder than necessary.  We will
> be very careful with deprecations and provide scripts that generate
> diffs for necessary updates we cannot workaround (similar to how the
> import rewriting with Werkzeug 0.7 already works and how blueprint
> updates worked in Flask 0.7).
>
> For the full list of what is new check out the changelog in the
> documentation and the tarball.
>
> Most important improvements:
>
> - greatly improved routing system (better ordering, default handling
>  and support for multiple domains)
> - Very basic Range/IfRange/ContentRange support
> - improved multipart parser
> - some changes that should aid an upgrade to Python 3
>
>
> Regards,
> Armin
>

Hi,

On 7/24/11 6:31 PM, Sean Lynch wrote:
> As my experience with the framework improves, I'm going to work on
> improving the App Engine compatibility of Flask, especially now that
> Tipfy (based on Werkzeug) has taken a back seat to webapp2 (WebOb
> based).  The new Range support in Werkzeug should help, and I'm going to
> look at Tipfy's code base to port over some of the work Rodrigo had done
> in Tipfy for supporting App Engine services (deferred, blobstore, etc).
>  Some of the trickier pieces are outlined
Helpers to make one's life easier on GAE can only be good :)  The range
support is very basic so far but I think one can base something useful
on there.


Regards,
Armin