Re: [pylons-devel] Pylons 1.x maintenance
Hi, On Jul 20, 2015 5:11 PM, Steve Piercy steve.piercy@gmail.com wrote: Take over implies ownership. Is that what you mean? I mean being able to react promptly to security and compatibility issues, merge and review patches, tag and upload releases. The core team of Kallithea has necessary skills and experience, so I think we can manage providing Pylons all life support it needs :) You could be added as a Core Developer so that you can manage pull requests. https://github.com/orgs/Pylons/teams/core-developers This, together with PyPI authorisation, would be useful. You are more than welcome to make contributions to the code, following the contribution guidelines. http://www.pylonsproject.org/community/how-to-contribute P.S. Please Cc me, as I'm not subscribed to the list, and for some reason topic subscription didn't work either. -- Cheers, Andrew -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
Re: [pylons-devel] Pylons 1.x maintenance
Hi, On 20 July 2015 at 22:47, Steve Piercy steve.piercy@gmail.com wrote: To proceed, please contact Ben Bangert directly, as he is the owner of Pylons the web framework, and work out any details. I don't have any say in the matter; I'm just facilitating. https://github.com/bbangert Okay, maybe I should try (again). You are shown as a subscriber with No email as your preference. Would you like me to change that? Other options are All email and Digest. If you want to change it, you must have a Google Account for the address. This is what I wanted, yes, but Google Groups also has ‘subscribe me to the topics I post to’, but it doesn't work :( -- Cheers, Andrew -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
[pylons-devel] Re: peewee ORM
Thanks for the advise I'll look into that. I was trying to figure out how best to get a db connection and make sure its closes properly. putting it an a tween seemed convienent, but I get what your saying about the unnessary load for every request especiualy if a connection to the database is not needed. Jose On Monday, July 20, 2015 at 2:48:29 PM UTC-4, Jonathan Vanasco wrote: I'm not sure what `request.peewee_dbs()[db].connect()` does, but I would probably recommend against this db setup pattern that you're using. By doing this in a tween, every request that pyramid handles will do a connect/disconnect to all the databases you defined. One of the more popular patterns to implement db connections is something like this: - `add_request_method` provides an object that either returns an database connection, or creates a new one. - if you create a new connection, it registers a 'db.close()' via `add_finished_callback` this way you only connect as needed, and disconnect to actually connected databases. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
