-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/06/2011 12:41 AM, Mike Orr wrote: > Here's the first draft of my Pyramid Migration Guide. It's an > introduction to Pyramid for Pylons 1 users, comparing the two > frameworks feature by feature. This is a first draft so it may have > inaccuracies people will report in the next few days. And a few > sections at the end aren't written yet. But for what it is, it can > serve as an introduction to the Pyramid manual if you're finding the > vocabulary confusing or the details overwhelmingly many. > > It focuses on the pyramid_sqla application template in the > pyramid_sqla package, which is the most Pylons-like template. > > I'll be out of town next week (Mon-Fri) and I may leave my computer at > home, so if I don't reply for a few days that's why. > > Finished sections: vocabulary, Paster, INI file, models, view > handlers, routing (and a minimal overview of traversal), request > object, templates, static files, session (flash messages and secure > forms), webhelpers, shell, deployment. > > Not yet written: testing, forms, authorization, other Pyramid features > (overview of events, hooks, extending/ZCA, ZCML). There's an > internationalization section but I don't know enough about the topic > to write it myself. > > Online version: > https://bytebucket.org/sluggo/pyramid-docs/wiki/html/migration.html > Sphinx source: https://bitbucket.org/sluggo/pyramid-docs/src > > This is part of my Pyramid Supplemental Docs project. It will > eventually be on github and in the Pyramid docs, but first I wanted to > get it written. > > Replies to pylons-devel if it's a minor bug report or comment or > Pyramid usage issue, or to pylons-discuss if you think it's important > to all Pylons users.
Mike, thanks for writing such a comprehensive survey. As a non-Pylons developer who is deeply familiar with Pyramid's precursor, it was a useful explanation of some terminological / conceptual mismatches which had caused me to misunderstand some arguments. One bit I noticed: In https://bytebucket.org/sluggo/pyramid-docs/wiki/html/migration.html#app-globals-and-cache, you state:: You can also use ordinary module globals or class attributes, provided you don’t run multiple instances of Pyramid applications in the same process. (Pyramid does not encourage multiple applications per process anyway. Instead Pyramid recommends its extensibility features such as its Zope Component Architecture, which allow you to write pieces of code to interfaces and plug them into a single application.) Pyramid actually goes out of its way to make running multiple apps in the same process work: in fact, it uses the ZCA in a way which means that registrations made in one app's configurator won't interfere with those made in another app's configurator. Perhaps the docs need to show an example of such a setup, but it is quite supported. Some of us *do* write apps that expect to be extended / reconfigured via the ZCA registry, but Pyramid itself doesn't mandate that (or even document it all that well). If such an app uses the "global" ZCA APIs, it won't benefit from Pyramid's segregated registries, but that is no different from use of any other global (module- or class-scope variables, etc.) Again, thanks for the writeup! Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1TGVYACgkQ+gerLs4ltQ5pPgCaAx7siIULmZg0amPqOeSofott 3I4An072mipWYgLt9nUdNWKp/HTYPebn =BJfA -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
