Re: [Repoze-dev] unifying url dispatch and traversal

Hi On Fri, Jun 5, 2009 at 11:33 PM, Chris McDonough wrote: > Paul and Tres recently taught a repoze.bfg tutorial at the Plone > Symposium at Penn State.  Tres mentioned to me that, by the reactions > of the tutorial attendees, he thought having two separate-but-equal > ways to do URL-to-code mappi

[Repoze-dev] Repoze auth on Python Magazine

Hello, everyone! A few months ago I wrote an article on repoze.who and repoze.what, which has just been published on Python Magazine: http://pymag.phparch.com/c/issue/view/98 I believe it's a good resource for those who are new to both frameworks (even if they aren't familiar with WSGI or auth

Re: [Repoze-dev] understanding setup of repoze.what

Hi again, Jens. Jens said: > is there already any code i can checkout, use and test already in your > VCS? Not yet, it's on my working copy. I started working on it and it's most likely that I'll check it in tomorrow. I'll let you know when it's in, so you can use it and give some feedback ;-)

Re: [Repoze-dev] unifying url dispatch and traversal

Hey, I'm with Chris here (talk about an ambivalent position). I think we could be allowed to break things a bit before 1.0. Django did that with 0.96 and I think they got a lot of benefit from that move. Carlos de la Guardia On Fri, Jun 5, 2009 at 12:42 PM, Chris Rossi wrote: > On Fri, Jun 5,

Re: [Repoze-dev] unifying url dispatch and traversal

On Fri, Jun 5, 2009 at 1:27 PM, Chris McDonough wrote: > > What I *should* have done from the very start was to pass the request > object in to both root factories and context factories. But it's too late > for that now; we'd break too many people's apps. > Just to play devil's advocate, here:

Re: [Repoze-dev] unifying url dispatch and traversal

On 6/5/09 12:37 PM, Chris Rossi wrote: > > > On Fri, Jun 5, 2009 at 12:01 PM, Tres Seaver > wrote: > >I'm assuming that we would fix anything in our repository; it > should even be possible to do so in a BBB-compatible way, e.g.:: > >def context_f

Re: [Repoze-dev] unifying url dispatch and traversal

On Fri, Jun 5, 2009 at 12:01 PM, Tres Seaver wrote: > I'm assuming that we would fix anything in our repository; it > should even be possible to do so in a BBB-compatible way, e.g.:: > > def context_factory(environ=None, **kw): > match_dict = kw.copy() > if environ is not None: #

Re: [Repoze-dev] unifying url dispatch and traversal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Rossi wrote: > On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough wrote: > >> - If a "factory" is specified on a route, it will need to point at a >> function that had the same call/response convention as a traversal >> root factory. This wi

Re: [Repoze-dev] unifying url dispatch and traversal

On Fri, Jun 5, 2009 at 11:44 AM, Chris Rossi wrote: > > > On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough wrote: > >> >> - If a "factory" is specified on a route, it will need to point at a >> function that had the same call/response convention as a traversal >> root factory. This will brea

Re: [Repoze-dev] unifying url dispatch and traversal

On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough wrote: > > - If a "factory" is specified on a route, it will need to point at a > function that had the same call/response convention as a traversal > root factory. This will break code. "Context factories" accept > key/value pairs assumed

[Repoze-dev] unifying url dispatch and traversal

Paul and Tres recently taught a repoze.bfg tutorial at the Plone Symposium at Penn State. Tres mentioned to me that, by the reactions of the tutorial attendees, he thought having two separate-but-equal ways to do URL-to-code mapping (traversal vs. url dispatch/aka routes) was too confusing. He th

Re: [Repoze-dev] understanding setup of repoze.what

Am Fri, 05 Jun 2009 13:34:16 +0200 schrieb Gustavo Narea: [...] > The ability to configure repoze.what from a .ini file will be built-in > as of repoze.what-1.1.0, which I hope to release this month, possibly > forked from and backwards-compatible with the plugin above. is there already any code i

[Repoze-dev] repoze.what.plugins.config 0.2 egg on pypi broken

subject says it all, the file VERSION.txt is not packaged in the repoze.what.plugins.config-0.2.tar.gz - and so it fails on easy_install time (i'am using python 2.6). see http://pypi.python.org/pypi/repoze.what.plugins.config/0.2 Getting distribution for 'repoze.what.plugins.config'. error: /tm

Re: [Repoze-dev] understanding setup of repoze.what

Hi, Jens! The plugin is mentioned here (repoze.what.plugins.quickstart), but you're certainly right about the missing link. I'm adding the link right now. Thanks! However, this plugin is for people who are using SQLAlch

[Repoze-dev] understanding setup of repoze.what

I have some problems with the setup of repoze.what in the docs [1] theres a 'quickstart' mentioned. Also theres written: "Warning Do not try to configure repoze.who directly – if you want authorization to work, you have to configure it through repoze.what." [1] http://what.repoze