Thanks David!
And also (thanks mostly to Reed O'Brien) I came to a resolution for the issues
I
wrote down in the email. In short, I don't think anything needs to change from
how things are on the trunk.
In excruciating detail however:
- Both route and view statements will continue to exist.
So now that this work is done, I'm having some major problems
explaining its finer points in documentation. I'm a bit worried that
I'll not explain it satisfactorily, and that will cause support and
adoption issues later. Sorry about writing the novel below. I don't
really expect anybody to
This work has now been done and merged into the trunk. See
http://svn.repoze.org/repoze.bfg/trunk/CHANGES.txt for more info. I'll
probably
release an alpha soon into the BFG dev index, maybe numbered something like
0.9.5 or so.
- C
On 6/5/09 11:33 AM, Chris McDonough wrote:
Paul and Tres
I have solely focused on a routes-based app, so I don't know how much
changes are involved when using traversal.
But the proposed changes really clean up that part of the API.
IMHO the needed changes are mostly superficial in that one has to
change the signature of functions and maybe some ZCML.
On Mon, Jun 8, 2009 at 10:19 AM, Stephan Altmueller step...@klaravision.com
wrote:
I would also like to throw in my suggestion for a function signature
(based on Chris Rossi's):
def context_factory(request, routes_match=None):
I like that one. +1
Chris
Chris McDonough chr...@plope.com writes:
Anyway, I don't really mind changing the urldispatch stuff radically at this
point; I'll fix the docs and our code and help anyone who needs it change
their
stuff. If I can make it bwcompat, great, but I'd rather break it now than
have
to live
On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough chr...@plope.com 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
On Fri, Jun 5, 2009 at 11:44 AM, Chris Rossi ch...@archimedeanco.comwrote:
On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough chr...@plope.com 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Rossi wrote:
On Fri, Jun 5, 2009 at 11:33 AM, Chris McDonough chr...@plope.com 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.
On Fri, Jun 5, 2009 at 12:01 PM, Tres Seaver tsea...@palladion.com 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
On 6/5/09 12:37 PM, Chris Rossi wrote:
On Fri, Jun 5, 2009 at 12:01 PM, Tres Seaver tsea...@palladion.com
mailto:tsea...@palladion.com 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.::
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
Hi
On Fri, Jun 5, 2009 at 11:33 PM, Chris McDonoughchr...@plope.com 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
13 matches
Mail list logo
