On Sat, Nov 6, 2010 at 11:19 AM, miniwark <[email protected]> wrote: > But the fear of "how easy will it be to convert well my application to Pyramid".
I don't know yet. Wait till more people have made experimental apps and reported their results, and then it will be clearer. I'm working on a Pyramid version of the QuickWiki tutorial right now. That'll show form usage and database access. I'm not sure if it'll use a form library. > I have already made the 0.9.7 -> 1.0 move (and that was easy thanks to > http://pylonshq.com/docs/en/1.0/upgrading/). Pyramid won't understand 0.9.7-isms, so you'd have to upgrade to 1.0 anyway. (Or run the 0.9.7 app as-is under Pyramid.) > 1) I do not have seen in the Pyramid docs lines about logging. I do > not see either in the default pylons_sqla template. > I think than it was a great default idea in the Pylons1 templates. Copy the logging stanazas into the INI file and it should work. I'm pretty sure the logging is set up by "paster serve", and it's the same in Pyramids.If it doesn't work, you'll have to to insert a "logging.config.fileConfig(filename)" call in the initialization module. I've opened a bug to add the logging stanzas in the application templates. https://github.com/Pylons/pyramid/issues#issue/18 > 2) If i have understand, Beaker is not set up by default but > pyramid_beaker is available, and will > probably be used by the majority of us. In my Pylons project i do not > have to even think about it > because the default template do it for me so : > - is it planed to add it by default in a pyramid templates or will it > be > only a "do it yourself" ? (it's seems anyway than it's easy to do > thanks to pyramid_beaker) Included in the bug report. > 3) Pyramid is furnished with his own Auth&Auth mecanism. Actualy i am > using repoze.what-pylons > mainly because he have a database backend and a good user base (also > TG2 give me an alredy done model for it). > Actualy i can do what i want with it even if he give me too much (i > use only users and permissions, but not groups). > But it's working (even if it was a bit painful to setup) > > Francky i have find the Auth&Auth doc part of Pyramid dificult to > understand for me. It's probably > because i have use a someone else recipe for now and did not do it > myself so : > - Could we have a steep-by-steep of the Pyramid Auth&Auth working > example in the doc (preferabily database oriented) I'm planning to put it in one of the tutorials. I also added it to the bug report for the application templates. Maybe it would be possible to write a standalone version of the auth system for Pylons 1, to provide a smooth upgrade path for Pyramid. Does anyone want to look into this? > - What are the advantage or limitations of the pyramid Auth&Autho over > others ? (repoze.who/what, AuthKit etc...) Supposedly it requires less boilerplate code because it's not middleware. I haven't looked at it closely yet. > 4) Pyramid have herited the ZCML thing... I sure than you are already > aware of the basic Pylons developer fear about it. > My problem is not the Zope backgroun it's just than i don't like > writing XML. I already know than i can use the > Configurator to be pythonic and even do not think about XML. But it's > well explained in the doc than if i want my > project to be Expendable i will have to take the ZCML road so : > - Is there any futures plan to allow apps to be expandable even if the > are writed imperatively ? When the Pyramid manual says "extendable" it means extendable in a specific way. There are many ways to make code extensible without doing it that way. For instance, entry points, or a registry dict in the application, etc. Pyramid's extension mechanism is an advanced topic, so you may want to wait until you've written a few Pyramid applications before using it. If you think you might need it in your current application, you can start a new mailing-list thread about that and see what the experts advise. > - if not could we have an ZCML example for each imperative example in > the doc ? Every single example would be a lot. The previous version of the manual did have a ZCML example for every imperative example, but they were all moved to one chapter so as not to confuse people coming from Pylons. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
