librelist archives

Flask Principal not happy in app engine

Flask Principal not happy in app engine by Charlie Evett
- Re: [flask] Flask Principal not happy in app engine by Ron DuPlain
  - Re: [flask] Flask Principal not happy in app engine by Charlie Evett
    - Re: [flask] Flask Principal not happy in app engine by Ron DuPlain

Flask Principal not happy in app engine

From:: Charlie Evett
Date:: 2011-04-12 @ 20:40

I've started to use Flask for an app engine project, and I've stumbled onto
the fact that the Flask Principal extension won't work on it because it
needs Python 2.6 to work.

The two things I've run into so far are that it used with... without
the "from __future__ import with_statement" and it used the namedtuple
collection, which is new in 2.6.

Python 2.7 support is on the 'roadmap' for app engine, so it may arrive in
some number of months.

The status of Flask Principal is kind of confusing, since there was an item
for it during the PyCon 2011 Sprints, but it wasn't really clear what was
planned for that.

Re: [flask] Flask Principal not happy in app engine

From:: Ron DuPlain
Date:: 2011-04-12 @ 20:49

On Tue, Apr 12, 2011 at 4:40 PM, Charlie Evett <charlieevett@litl.com> wrote:
> I've started to use Flask for an app engine project, and I've stumbled onto
> the fact that the Flask Principal extension won't work on it because it
> needs Python 2.6 to work.

This is one reason why Flask-Principal is not ready yet as an approved
extension.
"10. An extension currently has to support Python 2.5, 2.6 as well as
Python 2.7"
http://flask.pocoo.org/docs/extensiondev/#approved-extensions

> The status of Flask Principal is kind of confusing, since there was an item
> for it during the PyCon 2011 Sprints, but it wasn't really clear what was
> planned for that.

Not sure what the plan is, but I can speak for PyCon 2011, where
Flask-Principal didn't get a lot of specific attention.  We mostly
addressed extensions and overhauling the approval workflow, a
replacement for flask.Module, Flask-SQLAlchemy, and documentation.

-Ron

Re: [flask] Flask Principal not happy in app engine

From:: Charlie Evett
Date:: 2011-04-12 @ 21:00

Aha! You know, I didn't even notice it wasn't approved. I somehow thought
everything on the extensions page was.

Thanks for the clarification.

On Tue, Apr 12, 2011 at 4:49 PM, Ron DuPlain <ron.duplain@gmail.com> wrote:

> On Tue, Apr 12, 2011 at 4:40 PM, Charlie Evett <charlieevett@litl.com>
> wrote:
> > I've started to use Flask for an app engine project, and I've stumbled
> onto
> > the fact that the Flask Principal extension won't work on it because it
> > needs Python 2.6 to work.
>
> This is one reason why Flask-Principal is not ready yet as an approved
> extension.
> "10. An extension currently has to support Python 2.5, 2.6 as well as
> Python 2.7"
> http://flask.pocoo.org/docs/extensiondev/#approved-extensions
>
>
> > The status of Flask Principal is kind of confusing, since there was an
> item
> > for it during the PyCon 2011 Sprints, but it wasn't really clear what was
> > planned for that.
>
> Not sure what the plan is, but I can speak for PyCon 2011, where
> Flask-Principal didn't get a lot of specific attention.  We mostly
> addressed extensions and overhauling the approval workflow, a
> replacement for flask.Module, Flask-SQLAlchemy, and documentation.
>
> -Ron
>

Re: [flask] Flask Principal not happy in app engine

From:: Ron DuPlain
Date:: 2011-04-12 @ 21:04

On Tue, Apr 12, 2011 at 5:00 PM, Charlie Evett <charlieevett@litl.com> wrote:
> Aha! You know, I didn't even notice it wasn't approved. I somehow thought
> everything on the extensions page was.
> Thanks for the clarification.

I don't use Flask-Principal, but afaik it's ready for use even though
it's not yet an approved extension.  See the mailing list discussion
here:

http://flask.pocoo.org/mailinglist/archive/2011/4/8/flask-principal-question/

Maybe others can speak up on the topic of Flask-Principal on App Engine.

-Ron