mortar_rdb 1.2.0 released!
Hi All, I'm pleased to announce a new release of mortar_rdb. This package ties together SQLAlchemy, sqlalchemy-migrate and the component architecture to make it easy to develop projects using SQLAlchemy through their complete lifecycle. Changes in this release were: - Pass None as the default for echo rather than False on the advice of Daniel Holth. - When using mortar_rdb.registerSession, allow exlicit disabling of two-phase commit. - No longer log passwords during session registration. - Specify sqlalchemy 0.6 as a requirement, until zope.sqlalchemy is ported, mortar_rdb shouldn't be used with :mod:`sqlalchemy` 0.7. If you'd like to see what mortar_rdb can do for you, please have a read of the narrative usage docs, which give a quick run through of the lifespan of a project developers using mortar_rdb: http://packages.python.org/mortar_rdb/use.html Full package details including mailing list, irc and bug tracker details can be found here: http://www.simplistix.co.uk/software/python/mortar_rdb cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Widget oriented
I'm not so familiar with web development and am currently writting a social network like app using pyramid. It seems to me that setting a renderer (inheriting a global layout) to a view and passing a few variables to modify the content of that renderer, is a little limited. I was inspired by the way deform works and thought about creating widgets (rendered html code) in the views, and pass those to the view renderer. That's not so much the design style that tutorials showed me, but seems much more object oriented. I'd like to know a little more about the techniques and patterns you are using to have good designs. Thanks, Kristian -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
deform_mako stab
Hi gang. I put up a (fork of jayd3e's) repo for deform_mako templates: https://github.com/mfeif/deform_mako I converted ALL of the templates, and attempted to stay as true to the original as possible (not implementing any style/markup changes from the .pt files). I'm sure I broke a couple of things (my understanding of Chameleon started just now) and there are probably bugs. How can I test these? And, assuming that soon we finish testing/fixing, should we release this as a package, or should we just put it in deform as another templates directory? Thanks! -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: how to call a function for evry 10 secs
It's the main() function in your application's top-level myapp/__init__.py module. On Wed, Jun 29, 2011 at 7:11 PM, jerry jerryji1...@gmail.com wrote: Hi Mike, I'm curious to know where is this main() for Pyramid you were referring to? Thanks. Jerry On Jun 30, 5:30 am, Mike Orr sluggos...@gmail.com wrote: On Wed, Jun 29, 2011 at 10:40 AM, hisan santosh.s...@gmail.com wrote: how to call a function for evry 10 secs in python I assume this is a Pylons or Pyramid application since this is pylons-discuss. The easiest way would probably be to start a thread in the initialization code (environment.py for Pylons, main() for Pyramid). The thread would run a long-running function with a loop that that records its start time, does its thing, sleeps for ``(10 seconds - (now - start_time))``, and repeats. Another way to do repeated events is with cron, possibly using paster request. But that won't work in this case because cron can't handle intervals of less than a minute. -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: deform_mako stab
On Thu, 2011-06-30 at 18:10 -0500, Michael Merickel wrote: A good test may be to fix the deformdemo to use these templates. https://github.com/Pylons/deform/tree/master/deformdemo I'd just copy the deformdemo into pyramid_mako and make sure its tests pass after changing the copy to use Mako. Rinse, lather, repeat forever as you maintain pyramid_mako. - C -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: deform_mako stab
On Thu, 2011-06-30 at 21:53 -0400, Chris McDonough wrote: On Thu, 2011-06-30 at 18:10 -0500, Michael Merickel wrote: A good test may be to fix the deformdemo to use these templates. https://github.com/Pylons/deform/tree/master/deformdemo I'd just copy the deformdemo into pyramid_mako and make sure its tests pass after changing the copy to use Mako. Rinse, lather, repeat forever as you maintain pyramid_mako. s/pyramid_mako/deform_mako - C -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Widget oriented
Hi Kristian, For UI-intensive applications I like to go the ajax route. It works well because Pyramid can focus on tasks like security, validation and processing of data, and updating the database, while only returning the minimal amount of information the client-side application needs to function. This could mean returning a json reply that everything was ok, flashing back a message that it isn't, or sending only the snippet of html needed for a form or other feature. The javascript then makes decisions about where and how those responses interact with the client. I've found that during the development phase this often keeps things much simpler (provided you're willing to learn a javascript framework and/or a lot of javascript), and makes it easy to separate out the ideas of what the client sees vs how you handle data on the server. I've been stalling for months on writing a tutorial to demonstrate how you can structure a UI-rich application with Pyramid, partly because it'd rely heavily on YUI for the client-side features, and that's not something everyone wants to learn or use. It comes down to me being most comfortable with YUI and too stubborn to use another framework, though I believe the Pyramid techniques would work well with any javascript framework. If there is a real interest in this I can try to put together a shortish demo. Take care, Eric On Thu, Jun 30, 2011 at 2:43 PM, Kristian Benoit kristian.ben...@gmail.comwrote: I'm not so familiar with web development and am currently writting a social network like app using pyramid. It seems to me that setting a renderer (inheriting a global layout) to a view and passing a few variables to modify the content of that renderer, is a little limited. I was inspired by the way deform works and thought about creating widgets (rendered html code) in the views, and pass those to the view renderer. That's not so much the design style that tutorials showed me, but seems much more object oriented. I'd like to know a little more about the techniques and patterns you are using to have good designs. Thanks, Kristian -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
