From dorian.hoxha at gmail.com Fri Jan 1 06:15:17 2016 From: dorian.hoxha at gmail.com (Dorian Hoxha) Date: Fri, 1 Jan 2016 12:15:17 +0100 Subject: [Flask] Persistent SSH Connection in Flask App In-Reply-To: <57379407.5283719.1451573398404.JavaMail.yahoo@mail.yahoo.com> References: <57379407.5283719.1451573398404.JavaMail.yahoo.ref@mail.yahoo.com> <57379407.5283719.1451573398404.JavaMail.yahoo@mail.yahoo.com> Message-ID: Check on stackoverflow. On Thu, Dec 31, 2015 at 3:49 PM, C.PRAMOD NAIR via Flask wrote: > Hello All, > > I am trying to create a Flask APP to run command on remote server, I am > able to connect to remote using pexpect.pxssh. Code snippet is in below > link, the issue here is that the connect_ssh is getting called for each > request. I want to know if it's possible to create persistent ssh > connection. > > http://stackoverflow.com/questions/34509746/ssh-persistent-connection-using-pxssh-in-flask > > Thanks > > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From klawlor419 at gmail.com Fri Jan 1 16:48:04 2016 From: klawlor419 at gmail.com (Kyle Lawlor) Date: Fri, 1 Jan 2016 16:48:04 -0500 Subject: [Flask] trouble adding an integer postfix or prefix to an html attribute with wtforms Message-ID: Hi, all. I have the following thing in a jinja for loop: {{ meal[item]['open-modal'].submit( **{ 'class':'btn btn-primary', 'data-toggle':'modal', 'data-target':'#myModal' } ) }} I need to have an index on the data-target: {{ meal[item]['open-modal'].submit( **{ 'class':'btn btn-primary', 'data-toggle':'modal', 'data-target':'#myModal-*item*' } ) }} Item is the index needed in this case. Is there a way to escape item out of this "ad-hoc dictionary"? So that it takes on the same values as in meal[item]? http://flask.pocoo.org/snippets/107/ -Kyle p.s. Happy New Year! -------------- next part -------------- An HTML attachment was scrubbed... URL: From klawlor419 at gmail.com Fri Jan 1 21:48:59 2016 From: klawlor419 at gmail.com (Kyle Lawlor) Date: Fri, 1 Jan 2016 21:48:59 -0500 Subject: [Flask] trouble adding an integer postfix or prefix to an html attribute with wtforms In-Reply-To: References: Message-ID: Well, I solved my problem and it was of course a dumb mistake. In case it is ever helpful for someone, what wound up solving my problem was: Keep in mind that this is nested inside of two for loops in jinja2. {% for meal in menu_dict %} {% for item in meal %} .... {% endfor %} {% endfor %} Don't ask about the data structure of menu_dict. It's too complicated and needs work. The point is summarized with this, basically: 'data-target':'#myModal-' + item|string adds the postfix. -Kyle On Fri, Jan 1, 2016 at 4:48 PM, Kyle Lawlor wrote: > Hi, all. > > I have the following thing in a jinja for loop: > > {{ meal[item]['open-modal'].submit( **{ 'class':'btn btn-primary', > 'data-toggle':'modal', 'data-target':'#myModal' } ) }} > > I need to have an index on the data-target: > > {{ meal[item]['open-modal'].submit( **{ 'class':'btn btn-primary', > 'data-toggle':'modal', 'data-target':'#myModal-*item*' } ) }} > > Item is the index needed in this case. Is there a way to escape item out > of this "ad-hoc dictionary"? So that it takes on the same values as in > meal[item]? > > http://flask.pocoo.org/snippets/107/ > > -Kyle > > p.s. Happy New Year! > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rus_patriot at inbox.ru Sun Jan 3 12:30:13 2016 From: rus_patriot at inbox.ru (=?UTF-8?B?UGF0cmlvdA==?=) Date: Sun, 03 Jan 2016 20:30:13 +0300 Subject: [Flask] =?utf-8?q?Flask-Admin_and_index=5Fview=3DMyAdminIndexView?= =?utf-8?b?KCk=?= Message-ID: <1451842213.793318935@f358.i.mail.ru> Hi all. Code no work: flask.ext.admin import Admin admin = Admin() admin.index_view = MyAdminIndexView() Code is work flask.ext.admin import Admin admin = Admin(index_view = MyAdminIndexView()) Why does not the first code? From jeff at jeffwidman.com Fri Jan 8 00:39:45 2016 From: jeff at jeffwidman.com (Jeff Widman) Date: Thu, 7 Jan 2016 21:39:45 -0800 Subject: [Flask] FYI--put up a blog post on managing PostgreSQL Materialized Views with Flask-SQLAlchemy Message-ID: PostgreSQL materialized views have been extremely useful as a caching layer for some of my projects. They're fast, easy to setup, don't require extra infrastructure, and easy to refresh. However, it took me forever to figure out how to manage the materialized views using Flask-SQLAlchemy, so I wrote it up in the hopes of saving others some time. If interested, you can see the code here: https://github.com/jeffwidman/sqlalchemy-postgresql-materialized-views And my blog post of explanatory notes here: http://www.jeffwidman.com/blog/847/using-sqlalchemy-to-create-and-manage-postgresql-materialized-views/ -- *Jeff Widman* jeffwidman.com | 740-WIDMAN-J (943-6265) <>< ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at davidbaumgold.com Fri Jan 8 09:23:47 2016 From: david at davidbaumgold.com (David Baumgold) Date: Fri, 8 Jan 2016 09:23:47 -0500 Subject: [Flask] FYI--put up a blog post on managing PostgreSQL Materialized Views with Flask-SQLAlchemy In-Reply-To: References: Message-ID: Jeff, this is really cool! Thank you for sharing! Any chance that this work can be merged back into SQLAlchemy, so that anyone using SQLAlchemy can benefit without having to write custom code? David Baumgold From:?Jeff Widman Reply:?Jeff Widman Date:?January 8, 2016 at 12:46:11 AM To:?flask at python.org Subject:? [Flask] FYI--put up a blog post on managing PostgreSQL Materialized Views with Flask-SQLAlchemy PostgreSQL materialized views have been extremely useful as a caching layer for some of my projects. They're fast, easy to setup, don't require extra infrastructure, and easy to refresh. However, it took me forever to figure out how to manage the materialized views using Flask-SQLAlchemy, so I wrote it up in the hopes of saving others some time.? If interested, you can see the code here: https://github.com/jeffwidman/sqlalchemy-postgresql-materialized-views And my blog post of explanatory notes here: http://www.jeffwidman.com/blog/847/using-sqlalchemy-to-create-and-manage-postgresql-materialized-views/ -- Jeff Widman jeffwidman.com?|?740-WIDMAN-J (943-6265)? <>< ? _______________________________________________ Flask mailing list Flask at python.org https://mail.python.org/mailman/listinfo/flask -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeff at jeffwidman.com Fri Jan 8 15:43:57 2016 From: jeff at jeffwidman.com (Jeff Widman) Date: Fri, 8 Jan 2016 12:43:57 -0800 Subject: [Flask] FYI--put up a blog post on managing PostgreSQL Materialized Views with Flask-SQLAlchemy In-Reply-To: References: Message-ID: Thanks. Mike Bayer, who leads SQLAlchemy development, helped me a lot with this recipe, so he's very aware of it. However, he's said in the past that including commands for managing views (normal or materialized) is currently out of scope for the main project. There's currently too little standardization amongst the various RDMS vendors, and the topic is advanced enough that it'd create ton of bug reports/support requests from people who aren't actually hitting bugs, they're simply mis-understanding some nuance of how views work. The support expectations from users when something is part of core are much higher vs a random recipe on a blog post. I agree with his thought process, and very impressed that he's built a flexible system supporting custom DDL, events, etc that allows us to build extra goodies on top of it like this. ? On Fri, Jan 8, 2016 at 6:23 AM, David Baumgold wrote: > Jeff, this is really cool! Thank you for sharing! Any chance that this > work can be merged back into SQLAlchemy, so that anyone using SQLAlchemy > can benefit without having to write custom code? > > David Baumgold > > > From: Jeff Widman > Reply: Jeff Widman > Date: January 8, 2016 at 12:46:11 AM > To: flask at python.org > Subject: [Flask] FYI--put up a blog post on managing PostgreSQL > Materialized Views with Flask-SQLAlchemy > > PostgreSQL materialized views have been extremely useful as a caching > layer for some of my projects. They're fast, easy to setup, don't require > extra infrastructure, and easy to refresh. > > However, it took me forever to figure out how to manage the materialized > views using Flask-SQLAlchemy, so I wrote it up in the hopes of saving > others some time. > > If interested, you can see the code here: > https://github.com/jeffwidman/sqlalchemy-postgresql-materialized-views > > And my blog post of explanatory notes here: > > http://www.jeffwidman.com/blog/847/using-sqlalchemy-to-create-and-manage-postgresql-materialized-views/ > > > -- > > * Jeff Widman* > jeffwidman.com | 740-WIDMAN-J (943-6265) > <>< > ? > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > -- *Jeff Widman* jeffwidman.com | 740-WIDMAN-J (943-6265) <>< -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank at pythonspot.com Sat Jan 9 18:07:05 2016 From: frank at pythonspot.com (Frank) Date: Sat, 9 Jan 2016 18:07:05 -0500 Subject: [Flask] FYI--put up a blog post on managing PostgreSQL Materialized Views with Flask-SQLAlchemy In-Reply-To: References:

Message-ID: Jeff, thanks for sharing! On Fri, January 8, 2016 3:43 pm, Jeff Widman wrote: > Thanks. > > > Mike Bayer, who leads SQLAlchemy development, helped me a lot with this > recipe, so he's very aware of it. However, he's said in the past that > including commands for managing views (normal or materialized) is > currently out of scope for the main project. > > There's currently too little standardization amongst the various RDMS > vendors, and the topic is advanced enough that it'd create ton of bug > reports/support requests from people who aren't actually hitting bugs, > they're simply mis-understanding some nuance of how views work. The > support expectations from users when something is part of core are much > higher vs a random recipe on a blog post. > > I agree with his thought process, and very impressed that he's built a > flexible system supporting custom DDL, events, etc that allows us to build > extra goodies on top of it like this. ??? > > On Fri, Jan 8, 2016 at 6:23 AM, David Baumgold > wrote: > > >> Jeff, this is really cool! Thank you for sharing! Any chance that this >> work can be merged back into SQLAlchemy, so that anyone using SQLAlchemy >> can benefit without having to write custom code? >> >> David Baumgold >> >> >> >> From: Jeff Widman >> Reply: Jeff Widman >> Date: January 8, 2016 at 12:46:11 AM >> To: flask at python.org >> Subject: [Flask] FYI--put up a blog post on managing PostgreSQL >> Materialized Views with Flask-SQLAlchemy >> >> >> PostgreSQL materialized views have been extremely useful as a caching >> layer for some of my projects. They're fast, easy to setup, don't >> require extra infrastructure, and easy to refresh. >> >> However, it took me forever to figure out how to manage the >> materialized views using Flask-SQLAlchemy, so I wrote it up in the hopes >> of saving others some time. >> >> If interested, you can see the code here: >> https://github.com/jeffwidman/sqlalchemy-postgresql-materialized-views >> >> >> And my blog post of explanatory notes here: >> >> >> http://www.jeffwidman.com/blog/847/using-sqlalchemy-to-create-and-manag >> e-postgresql-materialized-views/ >> >> >> -- >> >> >> * Jeff Widman* >> jeffwidman.com | 740-WIDMAN-J (943-6265) <>< >> ??? _______________________________________________ >> Flask mailing list >> Flask at python.org >> https://mail.python.org/mailman/listinfo/flask >> >> >> > > > -- > > > *Jeff Widman* > jeffwidman.com | 740-WIDMAN-J (943-6265) <>< > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > From aimanparvaiz at gmail.com Sat Jan 16 22:16:04 2016 From: aimanparvaiz at gmail.com (aiman parvaiz) Date: Sat, 16 Jan 2016 19:16:04 -0800 Subject: [Flask] flask-android maintain variable between requests Message-ID: Hi all I am new to flask and am writing API for a simple video upload android app. App uses whatsapp like one time password authentication and the user stays logged in. App has user role and every user has a uuid associated with it. For every end point app sends a uuid to the server and I use that uuid to talk to the DB to get the role of the user. I want to skip this step of going to DB and getting the user role. I wanted to know what would be the best way to get the role from DB once and store it somewhere for all the subsequent user requests till this user logs out. In my limited knowledge flask.g won?t work beyond the first request by the user(As it is valid only for one request) and browser like sessions can?t be supported in the android app(we tried making requests from the app but session['id'] is not available for usage. Same code worked fine on a browser). Should I be looking in to storing a simple key:value in redis/memcahced or is there a better way to approach this issue. Also, I would be using uwsgi and nginx to host this backend. Any help would be appreciated please. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From corralejob at gmail.com Sat Jan 16 22:26:30 2016 From: corralejob at gmail.com (Bryan Corralejo) Date: Sat, 16 Jan 2016 21:26:30 -0600 Subject: [Flask] flask-android maintain variable between requests In-Reply-To: References: Message-ID: You could store the data in a session for the user. Flask-session offers an interface into redis/memcached for server side sessions or you can store it in a session cookie and have the data sent with every request. On Jan 16, 2016 9:16 PM, "aiman parvaiz" wrote: > Hi all > I am new to flask and am writing API for a simple video upload android > app. App uses whatsapp like one time password authentication and the user > stays logged in. App has user role and every user has a uuid associated > with it. For every end point app sends a uuid to the server and I use that > uuid to talk to the DB to get the role of the user. I want to skip this > step of going to DB and getting the user role. I wanted to know what would > be the best way to get the role from DB once and store it somewhere for all > the subsequent user requests till this user logs out. In my limited > knowledge flask.g won?t work beyond the first request by the user(As it is > valid only for one request) and browser like sessions can?t be supported in > the android app(we tried making requests from the app but session['id'] is > not available for usage. Same code worked fine on a browser). Should I be > looking in to storing a simple key:value in redis/memcahced or is there a > better way to approach this issue. Also, I would be using uwsgi and nginx > to host this backend. > > Any help would be appreciated please. > Thanks > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhijeet.1989 at gmail.com Mon Jan 18 02:31:33 2016 From: abhijeet.1989 at gmail.com (Abhijeet Rastogi) Date: Mon, 18 Jan 2016 07:31:33 +0000 Subject: [Flask] Separate initialization for each worker in Flask+Gunicorn Message-ID: Hi All, My flask application views contact an API endpoint during the lifetime of requests. Each of these API request requires a token. Due to the server side limitation, I can't have two threads using the same token for initiating requests. Requirements:- - To contact this API, I need to fetch an API token. I would like to do this once per worker and then share that value among views. (just a read-only variable). - I want each "worker" that serves requests to have a separate "token". How can that be achieved in Flask? - I don't want to issue a fresh token each time a request is served as that'll be horribly slow. How do I make that possible in Flask? Any help is appreciated. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From alejoar at gmail.com Mon Jan 18 06:32:19 2016 From: alejoar at gmail.com (Alejo Arias) Date: Mon, 18 Jan 2016 12:32:19 +0100 Subject: [Flask] Separate initialization for each worker in Flask+Gunicorn In-Reply-To: References: Message-ID: Hi Abhijeet, You could store the token as an app config value: app.config['CURRENT_TOKEN'] = 'your_token_here' and then have the workers access the token from the app config. Anytime a worker finds the token is not set or needs an update, simply set/update the same config value. Regards, Alejo On 18 January 2016 at 08:31, Abhijeet Rastogi wrote: > Hi All, > > > My flask application views contact an API endpoint during the lifetime of > requests. Each of these API request requires a token. Due to the server > side limitation, I can't have two threads using the same token for > initiating requests. > > Requirements:- > > - To contact this API, I need to fetch an API token. I would like to > do this once per worker and then share that value among views. (just a > read-only variable). > - I want each "worker" that serves requests to have a separate > "token". How can that be achieved in Flask? > - I don't want to issue a fresh token each time a request is served as > that'll be horribly slow. > > How do I make that possible in Flask? Any help is appreciated. > > Thanks! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhijeet.1989 at gmail.com Mon Jan 18 06:39:59 2016 From: abhijeet.1989 at gmail.com (Abhijeet Rastogi) Date: Mon, 18 Jan 2016 11:39:59 +0000 Subject: [Flask] Separate initialization for each worker in Flask+Gunicorn In-Reply-To: References: Message-ID: Hi Alejo, Thanks for the reply. How should I set this value? After I initialize my "app" variable and just before I register blueprints? Cheers! On Mon, Jan 18, 2016 at 5:02 PM Alejo Arias wrote: > Hi Abhijeet, > > You could store the token as an app config value: > > app.config['CURRENT_TOKEN'] = 'your_token_here' > > and then have the workers access the token from the app config. Anytime a > worker finds the token is not set or needs an update, simply set/update the > same config value. > > Regards, > Alejo > > On 18 January 2016 at 08:31, Abhijeet Rastogi > wrote: > >> Hi All, >> >> >> My flask application views contact an API endpoint during the lifetime of >> requests. Each of these API request requires a token. Due to the server >> side limitation, I can't have two threads using the same token for >> initiating requests. >> >> Requirements:- >> >> - To contact this API, I need to fetch an API token. I would like to >> do this once per worker and then share that value among views. (just a >> read-only variable). >> - I want each "worker" that serves requests to have a separate >> "token". How can that be achieved in Flask? >> - I don't want to issue a fresh token each time a request is served >> as that'll be horribly slow. >> >> How do I make that possible in Flask? Any help is appreciated. >> >> Thanks! >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alejoar at gmail.com Mon Jan 18 08:33:35 2016 From: alejoar at gmail.com (Alejo Arias) Date: Mon, 18 Jan 2016 14:33:35 +0100 Subject: [Flask] Separate initialization for each worker in Flask+Gunicorn In-Reply-To: References: Message-ID: Hi Abhijeet, You can set it at any time (after app creation). To do so, import current_app from flask: from flask import current_app And then access the config parameter like so: To set: current_app.config['CURRENT_TOKEN'] = 'your_token_here' To get: my_token = current_app.config['CURRENT_TOKEN'] Hope that helps. Regards, Alejo On 18 January 2016 at 12:39, Abhijeet Rastogi wrote: > Hi Alejo, > > Thanks for the reply. How should I set this value? After I initialize my > "app" variable and just before I register blueprints? > > Cheers! > > On Mon, Jan 18, 2016 at 5:02 PM Alejo Arias wrote: > >> Hi Abhijeet, >> >> You could store the token as an app config value: >> >> app.config['CURRENT_TOKEN'] = 'your_token_here' >> >> and then have the workers access the token from the app config. Anytime a >> worker finds the token is not set or needs an update, simply set/update the >> same config value. >> >> Regards, >> Alejo >> >> On 18 January 2016 at 08:31, Abhijeet Rastogi >> wrote: >> >>> Hi All, >>> >>> >>> My flask application views contact an API endpoint during the lifetime >>> of requests. Each of these API request requires a token. Due to the server >>> side limitation, I can't have two threads using the same token for >>> initiating requests. >>> >>> Requirements:- >>> >>> - To contact this API, I need to fetch an API token. I would like to >>> do this once per worker and then share that value among views. (just a >>> read-only variable). >>> - I want each "worker" that serves requests to have a separate >>> "token". How can that be achieved in Flask? >>> - I don't want to issue a fresh token each time a request is served >>> as that'll be horribly slow. >>> >>> How do I make that possible in Flask? Any help is appreciated. >>> >>> Thanks! >>> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From klawlor419 at gmail.com Tue Jan 19 11:45:11 2016 From: klawlor419 at gmail.com (Kyle Lawlor) Date: Tue, 19 Jan 2016 11:45:11 -0500 Subject: [Flask] Example usage of Spawning server with Flask apps Message-ID: Hi, all. I hope that the new year is treating everyone well. I'm curious to know if anyone in the community has experience using the Spawning server ( https://pypi.python.org/pypi/Spawning) with Flask apps. If there are references or examples that people would be willing to share, I would appreciate it. Thanks, Kyle -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidism at gmail.com Tue Jan 19 11:52:38 2016 From: davidism at gmail.com (David Lord) Date: Tue, 19 Jan 2016 08:52:38 -0800 Subject: [Flask] Example usage of Spawning server with Flask apps In-Reply-To: References: Message-ID: <569E69D6.90902@gmail.com> Seems to follow the pattern of any other WSGI server: you call it with the path to the WSGI callable (the app in Flask's case). Was there something specific you were looking for? Note that the last commit was four years ago, and it doesn't appear to support Python 3. The modern recommended servers are uWSGI, Gunicorn, or mod_wsgi with Apache. On 01/19/2016 08:45 AM, Kyle Lawlor wrote: > Hi, all. I hope that the new year is treating everyone well. I'm > curious to know if anyone in the community has experience using the > Spawning server (https://pypi.python.org/pypi/Spawning) with Flask > apps. If there are references or examples that people would be willing > to share, I would appreciate it. > > Thanks, > Kyle > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask -------------- next part -------------- An HTML attachment was scrubbed... URL: From klawlor419 at gmail.com Tue Jan 19 12:26:09 2016 From: klawlor419 at gmail.com (Kyle Lawlor) Date: Tue, 19 Jan 2016 12:26:09 -0500 Subject: [Flask] Flask Digest, Vol 7, Issue 9 In-Reply-To: References: Message-ID: I'm not really sure what I am looking for, to be honest. I'm trying to learn about concurrency and async programming with Flask. It looks like gevent and uWSGI are probably a good place to start. ( http://sdiehl.github.io/gevent-tutorial/) ( http://uwsgi-docs.readthedocs.org/en/latest/Gevent.html) I didn't realize how old the Spawning project was until after I posted. On Tue, Jan 19, 2016 at 12:00 PM, wrote: > Send Flask mailing list submissions to > flask at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/flask > or, via email, send a message with subject or body 'help' to > flask-request at python.org > > You can reach the person managing the list at > flask-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Flask digest..." > > > Today's Topics: > > 1. Example usage of Spawning server with Flask apps (Kyle Lawlor) > 2. Re: Example usage of Spawning server with Flask apps (David Lord) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jan 2016 11:45:11 -0500 > From: Kyle Lawlor > To: flask > Subject: [Flask] Example usage of Spawning server with Flask apps > Message-ID: > y-DPrXFe8dajexqwSg at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, all. I hope that the new year is treating everyone well. I'm curious to > know if anyone in the community has experience using the Spawning server ( > https://pypi.python.org/pypi/Spawning) with Flask apps. If there are > references or examples that people would be willing to share, I would > appreciate it. > > Thanks, > Kyle > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.python.org/pipermail/flask/attachments/20160119/2a4b187a/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Jan 2016 08:52:38 -0800 > From: David Lord > To: flask at python.org > Subject: Re: [Flask] Example usage of Spawning server with Flask apps > Message-ID: <569E69D6.90902 at gmail.com> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Seems to follow the pattern of any other WSGI server: you call it with > the path to the WSGI callable (the app in Flask's case). Was there > something specific you were looking for? Note that the last commit was > four years ago, and it doesn't appear to support Python 3. The modern > recommended servers are uWSGI, Gunicorn, or mod_wsgi with Apache. > > On 01/19/2016 08:45 AM, Kyle Lawlor wrote: > > Hi, all. I hope that the new year is treating everyone well. I'm > > curious to know if anyone in the community has experience using the > > Spawning server (https://pypi.python.org/pypi/Spawning) with Flask > > apps. If there are references or examples that people would be willing > > to share, I would appreciate it. > > > > Thanks, > > Kyle > > > > > > _______________________________________________ > > Flask mailing list > > Flask at python.org > > https://mail.python.org/mailman/listinfo/flask > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.python.org/pipermail/flask/attachments/20160119/e3d94f70/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > > ------------------------------ > > End of Flask Digest, Vol 7, Issue 9 > *********************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidism at gmail.com Tue Jan 19 12:34:32 2016 From: davidism at gmail.com (David Lord) Date: Tue, 19 Jan 2016 09:34:32 -0800 Subject: [Flask] Flask Digest, Vol 7, Issue 9 In-Reply-To: References:

Message-ID: <569E73A8.1000500@gmail.com> Typically, you would use a task queue such as Celery or Rq to run background tasks from Flask. Any WSGI server can handle concurrent requests, whether using threads, processes, or eventlets. Gevent is typically used when combining Flask with websockets (or SocketIO). The performance of these different approaches will depend on your specific project. Unrelated, but replying to the digest emails breaks threaded view in the mailing list archives, which relies on the subject remaining the same for a thread. On 01/19/2016 09:26 AM, Kyle Lawlor wrote: > I'm not really sure what I am looking for, to be honest. I'm trying to > learn about concurrency and async programming with Flask. It looks > like gevent and uWSGI are probably a good place to start. > (http://sdiehl.github.io/gevent-tutorial/) > (http://uwsgi-docs.readthedocs.org/en/latest/Gevent.html) I didn't > realize how old the Spawning project was until after I posted. > > On Tue, Jan 19, 2016 at 12:00 PM,

> wrote: > > Send Flask mailing list submissions to > flask at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/flask > or, via email, send a message with subject or body 'help' to > flask-request at python.org > > You can reach the person managing the list at > flask-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Flask digest..." > > > Today's Topics: > > 1. Example usage of Spawning server with Flask apps (Kyle Lawlor) > 2. Re: Example usage of Spawning server with Flask apps (David > Lord) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jan 2016 11:45:11 -0500 > From: Kyle Lawlor > > To: flask > > Subject: [Flask] Example usage of Spawning server with Flask apps > Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > Hi, all. I hope that the new year is treating everyone well. I'm > curious to > know if anyone in the community has experience using the Spawning > server ( > https://pypi.python.org/pypi/Spawning) with Flask apps. If there are > references or examples that people would be willing to share, I would > appreciate it. > > Thanks, > Kyle > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Jan 2016 08:52:38 -0800 > From: David Lord > > To: flask at python.org > Subject: Re: [Flask] Example usage of Spawning server with Flask apps > Message-ID: <569E69D6.90902 at gmail.com > > > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Seems to follow the pattern of any other WSGI server: you call it with > the path to the WSGI callable (the app in Flask's case). Was there > something specific you were looking for? Note that the last > commit was > four years ago, and it doesn't appear to support Python 3. The modern > recommended servers are uWSGI, Gunicorn, or mod_wsgi with Apache. > > On 01/19/2016 08:45 AM, Kyle Lawlor wrote: > > Hi, all. I hope that the new year is treating everyone well. I'm > > curious to know if anyone in the community has experience using the > > Spawning server (https://pypi.python.org/pypi/Spawning) with Flask > > apps. If there are references or examples that people would be > willing > > to share, I would appreciate it. > > > > Thanks, > > Kyle > > > > > > _______________________________________________ > > Flask mailing list > > Flask at python.org > > https://mail.python.org/mailman/listinfo/flask > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > > ------------------------------ > > End of Flask Digest, Vol 7, Issue 9 > *********************************** > > > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask -------------- next part -------------- An HTML attachment was scrubbed... URL: From langslike at foxmail.com Tue Jan 19 03:00:48 2016 From: langslike at foxmail.com (=?gb18030?B?z8TM7LXEt+c=?=) Date: Tue, 19 Jan 2016 16:00:48 +0800 Subject: [Flask] need help on request.view_args Message-ID: ------------------ ???? ------------------ ???: "????";; ????: 2016?1?19?(???) ??3:47 ???: "flask-request"; ??: help on request.view_args Hi I'm reading some web application code using flask, and the variable request.view_args confuses me: the url http://**?a=1 means that the associated request.args['a'] will be 1, how about view_args? how to set view_args for a request? and what's the general purpose of using it? I read the flask documentation ,but the description is too short .I googled but found most of the usage of view_args deals with pagination: http://flask.pocoo.org/snippets/44/ def url_for_other_page(page): args = request.view_args.copy() args['page'] = page return url_for(request.endpoint, **args) app.jinja_env.globals['url_for_other_page'] = url_for_other_page -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidism at gmail.com Tue Jan 19 21:12:27 2016 From: davidism at gmail.com (David Lord) Date: Tue, 19 Jan 2016 18:12:27 -0800 Subject: [Flask] need help on request.view_args In-Reply-To: References: Message-ID: <569EED0B.8090409@gmail.com> |view_args| is the list of arguments passed to the view, either captured from the url rule or set in the url defaults. http://flask.pocoo.org/docs/0.10/api/#flask.Request.view_args |@app.route('/hello/') def hello(name): return 'Hello, {}'.format(name) | In this example, |view_args| will be |{'name': 'david'}| when you go to |/hello/david|. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From hsysinfo at gmail.com Wed Jan 20 13:49:01 2016 From: hsysinfo at gmail.com (Chukwudi Nwachukwu) Date: Wed, 20 Jan 2016 19:49:01 +0100 Subject: [Flask] Flask Digest, Vol 7, Issue 11 In-Reply-To: References: Message-ID: Found this somewhere online long time ago: In the most common cases, request.data is going to be empty, because, as stated in the docs, it's used as a fallback: request.data Contains the incoming request data as string in case it came with a mimetype Flask does not handle. request.args : If you want the parameters in the URL request.form : If you want the information in the body (as sent by a html POST form) request.values : If you want both iChux? http://bit.ly/iscrape *Behind every no entry sign, there is a door.* On 20 January 2016 at 18:00, wrote: > Send Flask mailing list submissions to > flask at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/flask > or, via email, send a message with subject or body 'help' to > flask-request at python.org > > You can reach the person managing the list at > flask-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Flask digest..." > > > Today's Topics: > > 1. need help on request.view_args (=?gb18030?B?z8TM7LXEt+c=?=) > 2. Re: need help on request.view_args (David Lord) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jan 2016 16:00:48 +0800 > From: "=?gb18030?B?z8TM7LXEt+c=?=" > To: "=?gb18030?B?Zmxhc2s=?=" > Subject: [Flask] need help on request.view_args > Message-ID: > Content-Type: text/plain; charset="gb18030" > > ------------------ ???? ------------------ > ???: "????";; > ????: 2016?1?19?(???) ??3:47 > ???: "flask-request"; > > ??: help on request.view_args > > > > Hi > I'm reading some web application code using flask, and the variable > request.view_args confuses me: the url http://**?a=1 means that the > associated request.args['a'] will be 1, how about view_args? how to set > view_args for a request? and what's the general purpose of using it? I read > the flask documentation ,but the description is too short .I googled but > found most of the usage of view_args deals with pagination: > http://flask.pocoo.org/snippets/44/ > def url_for_other_page(page): args = request.view_args.copy() > args['page'] = page return url_for(request.endpoint, **args) > app.jinja_env.globals['url_for_other_page'] = url_for_other_page > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.python.org/pipermail/flask/attachments/20160119/ab93e613/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Jan 2016 18:12:27 -0800 > From: David Lord > To: flask at python.org > Subject: Re: [Flask] need help on request.view_args > Message-ID: <569EED0B.8090409 at gmail.com> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > |view_args| is the list of arguments passed to the view, either captured > from the url rule or set in the url defaults. > http://flask.pocoo.org/docs/0.10/api/#flask.Request.view_args > > |@app.route('/hello/') def hello(name): return 'Hello, > {}'.format(name) | > > In this example, |view_args| will be |{'name': 'david'}| when you go to > |/hello/david|. > > ? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.python.org/pipermail/flask/attachments/20160119/06620ace/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > > ------------------------------ > > End of Flask Digest, Vol 7, Issue 11 > ************************************ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidism at gmail.com Wed Jan 20 13:51:56 2016 From: davidism at gmail.com (David Lord) Date: Wed, 20 Jan 2016 10:51:56 -0800 Subject: [Flask] Flask Digest, Vol 7, Issue 11 In-Reply-To: References: Message-ID: <569FD74C.2000902@gmail.com> |data|, |form|, and |args| are not related to |view_args| On 01/20/2016 10:49 AM, Chukwudi Nwachukwu wrote: > Found this somewhere online long time ago: > In the most common cases, request.data is going to be empty, because, > as stated in the docs, it's used as a fallback: > > request.data Contains the incoming request data as string in case > it came with a mimetype Flask does not handle. > > request.args : If you want the parameters in the URL > request.form : If you want the information in the body (as sent by > a html POST form) > request.values : If you want both > > > > iChux? > http://bit.ly/iscrape > *Behind every no entry sign, there is a door.* > > On 20 January 2016 at 18:00,

>; > > ??: help on request.view_args > > > > Hi > I'm reading some web application code using flask, and the > variable request.view_args confuses me: the url http://**?a=1 > means that the associated request.args['a'] will be 1, how about > view_args? how to set view_args for a request? and what's the > general purpose of using it? I read the flask documentation ,but > the description is too short .I googled but found most of the > usage of view_args deals with pagination: > http://flask.pocoo.org/snippets/44/ > def url_for_other_page(page): args = request.view_args.copy() > args['page'] = page return url_for(request.endpoint, **args) > app.jinja_env.globals['url_for_other_page'] = url_for_other_page > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Jan 2016 18:12:27 -0800 > From: David Lord > > To: flask at python.org > Subject: Re: [Flask] need help on request.view_args > Message-ID: <569EED0B.8090409 at gmail.com > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > |view_args| is the list of arguments passed to the view, either > captured > from the url rule or set in the url defaults. > http://flask.pocoo.org/docs/0.10/api/#flask.Request.view_args > > |@app.route('/hello/') def hello(name): return 'Hello, > {}'.format(name) | > > In this example, |view_args| will be |{'name': 'david'}| when you > go to > |/hello/david|. > > ? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > > ------------------------------ > > End of Flask Digest, Vol 7, Issue 11 > ************************************ > > > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From langslike at foxmail.com Wed Jan 20 04:09:54 2016 From: langslike at foxmail.com (=?gb18030?B?z8TM7LXEt+c=?=) Date: Wed, 20 Jan 2016 17:09:54 +0800 Subject: [Flask] help on context processor and Jinja filter Message-ID: Hi? When we need to do process some value, or do some text formatting, we can define a filter function, which is really handy. However when I ran into this article about Context processors,: http://flask.pocoo.org/docs/0.10/templating/ I really want to know the differences between a filter function and a context processor function. Is context processor function mainly designed for those who are not using Jinja, so that they can still implement filters in another way? I found that people tend to do more complicated things in a context processor function, say get hottest articles in a blog, list recent articles and so on. Thx. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aimanparvaiz at gmail.com Thu Jan 21 15:01:47 2016 From: aimanparvaiz at gmail.com (aiman parvaiz) Date: Thu, 21 Jan 2016 12:01:47 -0800 Subject: [Flask] flask-android maintain variable between requests In-Reply-To: References:

Message-ID: Thanks Bryan for this input. I used Flask-Session* https://pythonhosted.org/Flask-Session/ * to implement server side sessions in Redis. But I am running in to a issue (and this might very well be my mis understanding of session implementation). When I hit /activate endpoint I set the session there as follows: session[*user_id*] = 'user' user_id is sent by the app. After setting session here if I do a session.get(user_id) I get the value back but when I try to the same thing in another endpoint /someother *print session.get(user_id, 'not set')* I get 'not set'. Now in my understanding if this key was written to Redis then I should be able to retrieve it from any endpoint. Please help me figure this out if I am missing anything here. Also in redis-cli when I do a *keys ** I see several *session:700b4e35-8c5c-4efb-bc6b-1c22b8e29ede, *doing a get on this I get *(dp1\nS'_permanent'\np2\nI01\ns.* I am assuming this in some internal implementation of flask sessions but is there a easier way from the redis-cli to see if my key is getting set and retrieve its value? Thanks On Sat, Jan 16, 2016 at 7:26 PM, Bryan Corralejo wrote: > You could store the data in a session for the user. Flask-session offers > an interface into redis/memcached for server side sessions or you can > store it in a session cookie and have the data sent with every request. > On Jan 16, 2016 9:16 PM, "aiman parvaiz" wrote: > >> Hi all >> I am new to flask and am writing API for a simple video upload android >> app. App uses whatsapp like one time password authentication and the user >> stays logged in. App has user role and every user has a uuid associated >> with it. For every end point app sends a uuid to the server and I use that >> uuid to talk to the DB to get the role of the user. I want to skip this >> step of going to DB and getting the user role. I wanted to know what would >> be the best way to get the role from DB once and store it somewhere for all >> the subsequent user requests till this user logs out. In my limited >> knowledge flask.g won?t work beyond the first request by the user(As it is >> valid only for one request) and browser like sessions can?t be supported in >> the android app(we tried making requests from the app but session['id'] is >> not available for usage. Same code worked fine on a browser). Should I be >> looking in to storing a simple key:value in redis/memcahced or is there a >> better way to approach this issue. Also, I would be using uwsgi and nginx >> to host this backend. >> >> Any help would be appreciated please. >> Thanks >> >> _______________________________________________ >> Flask mailing list >> Flask at python.org >> https://mail.python.org/mailman/listinfo/flask >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From unai at sysbible.org Tue Jan 26 11:27:41 2016 From: unai at sysbible.org (Unai Rodriguez) Date: Wed, 27 Jan 2016 00:27:41 +0800 Subject: [Flask] How to handle sent data through a form (post request) Flask-{Admin, Security} Message-ID: <1453825661.970402.503069506.75DBBA4D@webmail.messagingengine.com> Dear List, I am trying to build a simple web admin interface where users will be able to register and login to see some details of their account, etc. I have started by modifying the following Flask-Security example which basically makes it easy to have all typical views: register, login, forgot password, etc... https://github.com/flask-admin/Flask-Admin/tree/master/examples/auth I am having a hard time implementing the register page since it needs to be integrated with a payment gateway that requires that the server submits some information to their servers once the user has entered the data. The idea is simple: a user enters basic information including some credit card details on the register form which all gets sent to our server through a post request. The thing is we will probably not store the credit card details on the database but use this information to create a transaction on the payment gateway. So I need a way of having access to the data sent by this post request and not to store it on the database (and perform some other actions). This is how my form class has been defined: class ExtendedRegisterForm(RegisterForm):??? # Fields??? plan = SelectField('Plan', choices=[('alpha','alpha ($6.99)'),('gamma','gamma ($14.99)'),('beta','beta ($29.99)')])??? cc_number = StringField('Card number', render_kw={'maxlength':'19'})??? cc_name = StringField('Name on card', render_kw={'maxlength':'50'})??? cc_exp_month = StringField('month', [InputRequired(), Length(min=2, max=2)], render_kw={'maxlength':'2'})??? cc_exp_year = StringField('year', render_kw={'maxlength':'4'})??? cc_cvv = StringField('cvv', render_kw={'maxlength':'4'}) How can I handle the post request? I've tried this but doesn't seem to work: @app.route('/admin/register', methods=['POST']) def register(): return render_template('thanks.html') Is it worth using this Flask-{Admin,Security} modules for what I'm trying to do or you'd rather just do it from scratch? Thank you so much -- unai -------------- next part -------------- An HTML attachment was scrubbed... URL: From arsh840 at gmail.com Tue Jan 26 23:02:31 2016 From: arsh840 at gmail.com (Arshpreet Singh) Date: Wed, 27 Jan 2016 09:32:31 +0530 Subject: [Flask] Flask Error Log on Gmail ID Message-ID: Hi I want to implement Flask Error Logging on Production server, I want all logging information on my Gmail ID, Can you please guide for starting the process? -- Thanks Arshpreet Singh I am Sikh boy, Learning by doing and Learning by teaching is my religion. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ From seandavi at gmail.com Sat Jan 30 10:12:09 2016 From: seandavi at gmail.com (Sean Davis) Date: Sat, 30 Jan 2016 10:12:09 -0500 Subject: [Flask] S3 file manager app Message-ID: <03E6313A-B68E-4345-A6FF-079B02E1DDB5@gmail.com> Hello. Our group is just getting into using S3 and object storage. We generally handle very large files (10GB+) and I want to create a lightweight web app that can store files into S3, manage metadata, and also manage auth/authen for the group. I expect this to have both a web UI and RESTful API. I have code for doing CORS-based uploads and for downloads with time-limited URLs. It doesn?t look too hard, but I have learned that the Flask community often has something to offer, so I thought I would ask for tips or code from anyone who has done this type of thing before. Any suggestions? Thanks, Sean ? http://bit.ly/seandavis https://twitter.com/seandavis12 ? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: From rahurkar at gmail.com Sat Jan 30 11:24:15 2016 From: rahurkar at gmail.com (Mandar Rahurkar) Date: Sat, 30 Jan 2016 08:24:15 -0800 Subject: [Flask] S3 file manager app In-Reply-To: <03E6313A-B68E-4345-A6FF-079B02E1DDB5@gmail.com> References: <03E6313A-B68E-4345-A6FF-079B02E1DDB5@gmail.com> Message-ID: Are you uploading files via your webapp or do you have a mobile client initiating the upload? Usually I have seen people following this process: 1. Front end or app asynchronously uploads data to S3. 2. Send URL back to your backend. If your use case dictates that you go the flask route, you might want to look at boto python library. Mandar On Sat, Jan 30, 2016 at 7:12 AM, Sean Davis wrote: > Hello. > > Our group is just getting into using S3 and object storage. We generally > handle very large files (10GB+) and I want to create a lightweight web app > that can store files into S3, manage metadata, and also manage auth/authen > for the group. I expect this to have both a web UI and RESTful API. I > have code for doing CORS-based uploads and for downloads with time-limited > URLs. It doesn?t look too hard, but I have learned that the Flask > community often has something to offer, so I thought I would ask for tips > or code from anyone who has done this type of thing before. Any > suggestions? > > Thanks, > Sean > > ? > http://bit.ly/seandavis > https://twitter.com/seandavis12 > ? > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > -- --- www.linkedin.com/in/radnam/ PhD, University of Illinois-Urbana Champaign 217-390-7950 --- -------------- next part -------------- An HTML attachment was scrubbed... URL: From seandavi at gmail.com Sat Jan 30 16:53:25 2016 From: seandavi at gmail.com (Sean Davis) Date: Sat, 30 Jan 2016 16:53:25 -0500 Subject: [Flask] S3 file manager app In-Reply-To: References: <03E6313A-B68E-4345-A6FF-079B02E1DDB5@gmail.com> Message-ID: <5033442C-A735-4478-8832-3ADEFF62E051@gmail.com> Thanks, Mandar. > On Jan 30, 2016, at 11:24 AM, Mandar Rahurkar wrote: > > Are you uploading files via your webapp or do you have a mobile client initiating the upload? No mobile client. > Usually I have seen people following this process: > 1. Front end or app asynchronously uploads data to S3. > 2. Send URL back to your backend. This is basically what I was thinking, module who generates the URL (front- or back-end). > > If your use case dictates that you go the flask route, you might want to look at boto python library. I was thinking to have the skeleton of the app be flask-based with front-end work where possible. In particular, I found the reasonably complete AWS JS SDK which simplifies some of the details. It is similar in scope to the both library but AWS-specific. > > Mandar > > > On Sat, Jan 30, 2016 at 7:12 AM, Sean Davis > wrote: > Hello. > > Our group is just getting into using S3 and object storage. We generally handle very large files (10GB+) and I want to create a lightweight web app that can store files into S3, manage metadata, and also manage auth/authen for the group. I expect this to have both a web UI and RESTful API. I have code for doing CORS-based uploads and for downloads with time-limited URLs. It doesn?t look too hard, but I have learned that the Flask community often has something to offer, so I thought I would ask for tips or code from anyone who has done this type of thing before. Any suggestions? > > Thanks, > Sean > > ? > http://bit.ly/seandavis > https://twitter.com/seandavis12 > ? > > > _______________________________________________ > Flask mailing list > Flask at python.org > https://mail.python.org/mailman/listinfo/flask > > > > > -- > --- > www.linkedin.com/in/radnam/ > PhD, University of Illinois-Urbana Champaign > 217-390-7950 --- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: