Re: [Repoze-dev] new to bfg

Hi, Elliot, Elliot Gage wrote: > Good morning, > > > > I’ve been looking at bfg for some time. I am primarily a dotnet > developer and have a few web projects I am looking at migrating over to > a python framework. > > I am aware of a few frameworks already out there including django, > tu

Re: [Repoze-dev] Jython Support on 1.2

renderer='templates/mytemplate.pt') config.add_static_view(name='static', path='templates/static') config.end() return config.make_wsgi_app() Diaz, Eduardo wrote: > Yes, it does > > :P > > On Mon, Jan 4, 2010

Re: [Repoze-dev] Jython Support on 1.2

Diaz, Eduardo wrote: > Ok, I think I know why this is happening, > > the exception raises in the _validate method of the Orderable class, > this is where it happends: > > if self.max is not None and value > self.max: > raise TooBig(value, self.max) > > Here, max is a ValidatedProperty it ha

[Repoze-dev] repoze.bfg 1.2a10 released...

repoze.bfg 1.2a10 has been released. The documentation at http://docs.repoze.org/bfg/1.2 has been updated. It is installable via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. The changelog follows. 1.2a10 (2010-01-04) === Features

Re: [Repoze-dev] [bfg 1.29a] render_template_to_response returning the view class?

I'm not sure which version of bfg you're contrasting this against, but if the view is a class, constructing the class just constructs the class. It's not until the class' __call__ is invoked that a response is potentially generated. If a previous BFG version worked differently, it was a bug.

Re: [Repoze-dev] BFG documentation stuff

a/b/c -> {’baz’:abc, ’bar’:*2*, ’traverse’:(’a’, ’b’, ’c’)} > + foo/abc/def/a/b/c -> {’baz’:abc, ’bar’:*def*, ’traverse’:(’a’, ’b’, ’c’)} > > peace, > Ricardo Mendes Thank you! Fixed in SVN... - C > > 2009/12/27 Chris McDonough mailto:chr...@plope.com>> > &g

Re: [Repoze-dev] repoze.vhm and repoze.zope2 odd behavior

Martin Aspeli wrote: >> >> I assumed it was just acquisition trickery. Looking more closely, >> z2bob.py uses the repoze.vhm.virtual_root via the getVirtualRoot in the >> repoze.vhm.utils package to get the virtual root and it seems to create >> the correct path for traversal regardless of the issu

[Repoze-dev] BFG documentation stuff

The most recent release (1.2a9) of repoze.bfg contains a documentation licensing modification. Previous releases of the documentation stated no explicit license. The most recent release of repoze.bfg asserts that the documentation has the Creative Commons Attribution-Noncommercial-No Derivativ

[Repoze-dev] repoze.bfg 1.2a9 released

repoze.bfg 1.2a9 has been released. Install it via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. The documentation at http://docs.repoze.org/docs/bfg/1.2 have been updated. This is a release without any software changes; just documentation changes. The cha

[Repoze-dev] repoze.bfg 1.2a8 released

repoze.bfg 1.2a8 has been released. Install it via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. The docs at http://docs.repoze.org/bfg/1.2 have been updated. The changelog follows: 1.2a8 (2009-12-24) == Features - Add a ``**kw``

[Repoze-dev] repoze.bfg 1.2a7 released

repoze.bfg 1.2a7 has been released Install via: easy_install -U http://dist.repoze.org/bfg/1.2/simple repoze.bfg The docs at http://docs.repoze.org/bfg/1.2 have been updated. The changelog follows: 1.2a7 (2009-12-20) == Features - Add four new testing-related API

Re: [Repoze-dev] IRC Questions

Steve Schmechel wrote: > Sorry, if some of these questions are inane, but I am try to > get proficient at participating in IRC again after many years > away. (There is apparently more activity on the Repoze IRC channel > than on this list, so I guess I better learn if I want to participate.) >

[Repoze-dev] repoze.bfg 1.2a6 released

repoze.bfg 1.2a6 has been released Install via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. The docs at http://docs.repoze.org/bfg/1.2 have been updated. The changelog follows: 1.2a6 (2009-12-18) == Features - The ``Configurator`

[Repoze-dev] repoze.bfg 1.2a5 released

repoze.bfg 1.2a5 has been released. Install via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. The changelog follows. 1.2a5 (2009-12-10) == Features - When the ``repoze.bfg.exceptions.NotFound`` or ``repoze.bfg.exceptions.Forbid

[Repoze-dev] repoze.bfg 1.1.5 and 1.2a4 released

repoze.bfg 1.1.5 and 1.2a4 have been released. Install 1.2a4 via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Install 1.1.5 via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg 1.1.5 is a backport bugfix release. 1.2a4 is a bigfix and minor featu

[Repoze-dev] [issue112] Only getting registry over get_current_registry() in view (bfg 1.2X)

Chris McDonough added the comment: This is by design. In 1.2, if you don't use "repoze.bfg.router.make_app" to create your BFG WSGI application (instead using a Configurator and config.make_wsgi_app) and you need to use the ZCA "thread local API" (getUtiility, g

Re: [Repoze-dev] Running repoze.bfg on Google’s A pp Engine

t; On Thu, Dec 3, 2009 at 8:11 PM, Chris McDonough wrote: >> Darryl Cousins wrote: >>> Hi All, >>> >>> I found that the recipe [1] to run repoze.bfg on gae **almost** works. >> Thanks for the analysis! >> >> I think the best solution would be to mak

Re: [Repoze-dev] Running repoze.bfg on Google’s A pp Engine

Darryl Cousins wrote: > Hi All, > > I found that the recipe [1] to run repoze.bfg on gae **almost** works. Thanks for the analysis! I think the best solution would be to make all imports of Chameleon conditional.This actually *used* to be the case; something must have broken it since 1.0

[Repoze-dev] repoze.bfg 1.1.4 and 1.2a3 released

Two new releases of repoze.bfg are out. Install 1.1.4 via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg Install 1.2a3 via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or either is available via PyPI. These are bugfix releases. No release noti

Re: [Repoze-dev] authorization debug problem

Wichert Akkerman wrote: > I use a custom authorization problem, but noticed that when I enable > BFG_DEBUG_AUTHORIZATION it always reports "no authorization policy in > use". I am guessing this happens because the authorization policy is > registered after the routes are setup, so the queryUtili

Re: [Repoze-dev] fun benchmarks.

And in the spirit of a Chameleon hello world benchmark, rendering a template from a view that calls "repoze.bfg.chameleon_zpt.render_template_to_response" filling a slot in a macro fro

[Repoze-dev] fun benchmarks.

We just got a new box in and I did some benchmarks on it just to see how it worked. It's an Intel i5 (dual core, hyperthreading enabled, so it appears to have four cores to the OS) running 64-bit Ubuntu 9.10. Each core reports something like this from /proc/cpuinfo: processor: 3 ven

[Repoze-dev] [issue110] unexpected keyword argument 'level' repoze.bfg.jinja2 (bfg 1.2a2)

Chris McDonough added the comment: Thanks; I've fixed this in the 0.6 release, now on PyPI. -- status: unread -> resolved __ Repoze Bugs <http://bugs.repoze.o

[Repoze-dev] repoze.bfg 1.2a2 released

repoze.bfg 1.2a2 is out. Install via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. This is a pure bugfix release. The changelog follows. 1.2a2 (2009-11-29) == Bug Fixes - - The the long description of this package (as shown on PyPI

Re: [Repoze-dev] [bfg 1.2a1] Required specification must be a specification or class.

Andreas Jung wrote: > Tried to get zopyx.smartprintng.server working w/ BFG 1.2a1. This fails > badly. > Anything I am missing? Thanks for trying it. I have fixed this on the trunk and your server now starts. For maximum forward compatibility, you'll probably eventually want to change: @bfg_vi

[Repoze-dev] repoze.bfg 1.2a1 released

repoze.bfg 1.2a1 is now released. It can be installed via: easy_install -i http://dist.repoze.org/bfg/1.2/simple repoze.bfg Or via PyPI. Documentation for this release exists at: http://docs.repoze.org/bfg/1.2/ This is a major feature release. The new features of the release are deta

Re: [Repoze-dev] 1.2a1 imminent...

Tim Hoffman wrote: > Hi Chris > > I think this is a good direction to go in. I am already starting to > do something similair this with repoze (I am still on 1.0.1) but plan > to upgrade in the next few weeks,. > > The advantage of this style of configuration really comes into its own > when yo

[Repoze-dev] 1.2a1 imminent...

Hi folks, I've been working on the next minor revision to repoze.bfg, which will be 1.2. 1.2 will be a slightly more important release than the previous 1.1 release, because it involves exposing an "imperative" API for configuration (adding routes/views, etc). In particular, it means that the

[Repoze-dev] repoze.bfg 1.1.2 released

Happy Thanksgiving folks. repoze.bfg 1.1.2 has been released. Install it via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg Or via PyPI. It is a pure bugfix release. The changelog follows: 1.1.2 (2009-11-26) == Bug Fixes - - When two views wer

Re: [Repoze-dev] Possible "accept" view-predicate enhancement?

Alberto Valverde wrote: > Hello, > > I'm trying to make use of the new-in-1.1 "accept" view predicate to > register several views with the same name for the same context object to > render a response in the content-type requested by the user but the > result is not quite what I expect. The zcml

Re: [Repoze-dev] Possible "accept" view-predicate enhancement?

Alberto Valverde wrote: > Chris McDonough wrote: >> Alberto Valverde wrote: >>> Hello, >>> >>> I'm trying to make use of the new-in-1.1 "accept" view predicate to >>> register several views with the same name for the same context objec

Re: [Repoze-dev] would like to registerViews in python but not via decorator

Tim Hoffman wrote: > Hi Chris > > I am trying to register some views directly through python and not > using the view decorator, > I have tried using code very similiar to repoze.bfg.testing. > > However after doing so, whilst I can look the view up by doing > a zope.component.queryMultiAdapter((

Re: [Repoze-dev] Possible "accept" view-predicate enhancement?

Alberto Valverde wrote: > Hello, > > I'm trying to make use of the new-in-1.1 "accept" view predicate to > register several views with the same name for the same context object to > render a response in the content-type requested by the user but the > result is not quite what I expect. The zcml

Re: [Repoze-dev] starter request

Iain Duncan wrote: > Wondering if it would be possible to add a paster starter template for > bgf_routes ( no sqlalchemy )? Seems to be a missing piece. Instead of adding another a paster template, we could just answer whatever concrete questions you have about routing? Each paster template we a

Re: [Repoze-dev] doc question

Iain Duncan wrote: > Am I missing something terribly obvious, or is that not just a regular > instance method in the example? Or am I misunderstanding the point? > Perhaps this part could be clearer, it's confused me at any rate. I'm not really clear how to make changes to make it clearer. What a

Re: [Repoze-dev] using the pylons/weberror interfactive debugger in bfg apps?

Iain Duncan wrote: > Hey all, one thing I miss in Pylons is the out of the box integration > with the interactive debugger in your browser. I'll confess ignorance as > to how this is hooked up, but it's *really* helpful to people learning > pylons. Wondering if it would be a good plan to put this '

Re: [Repoze-dev] repoze.bfg future plans?

Iain Duncan wrote: > Hey Chris et. al, I'm seriously considering switching my main platform > for our inhouse framework to mostly repoze.bfg with auxillary pylons > bits from the other way around, but have a few concerns that mostly > relate to making sure that clients buy into our platform of choi

[Repoze-dev] repoze.bfg 1.1.1 released

repoze.bfg 1.1.1 has been released Install via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg The docs at http://docs.repoze.org/bfg/1.1 have been updated. This is a pure bugfix release. The changelog follows: 1.1.1 (2009-11-21) == Bug Fixes -

[Repoze-dev] repoze.bfg 1.1 final released

repoze.bfg 1.1 has been released. You can install it via: easy_install -i http://dist.repoze.org/bfg/current/simple repoze.bfg Or via PyPI. The "What's New In repoze.bfg 1.1" document details the changes made since the 1.0 release: http://docs.repoze.org/bfg/1.1/whatsnew-1.1.html The do

Re: [Repoze-dev] About location-aware object in Traversal

Hey Tim, You'll want to subscribe your gmail.com address to the list if you want these emails to make it to the list. Forwarding this one for you. - C Tim Hoffman wrote: > HI George > > Glad you found it, I didn't know if what I was saying was particularly > of interest so didn't bother with

Re: [Repoze-dev] About location-aware object in Traversal

Resending this because it was discarded by Mailman (sent from an unsubscribed address, apparently). - C Tim Hoffman wrote: > HI George > > You can really have a number of ways of supporting traversal and > __name__, __parent__ > > I am running repoze.bfg on app engine to implement a simple cms

Re: [Repoze-dev] About location-aware object in Traversal

george hu wrote: > As BFG document stated, all the object instances of model graph in > Traversal must have __name__ and __parent__ attribute, and they should > be hierarchically "linked". As the traversal wiki example reveals, page > objects are implementing this rule. But when I look at the so

[Repoze-dev] repoze.bfg 1.1b4 released

repoze.bfg 1.1b4 has been released. You can install it via: easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg Or via PyPI. The docs at http://docs.repoze.org/bfg/1.1 have been updated. The changelog follows: 1.1b4 (2009-11-12) == Bug Fixes - - Use

[Repoze-dev] [issue31] New blog backend

Chris McDonough added the comment: We rolled our own finally. -- status: done-cbb -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue31> __ ___ Repoze-dev mai

[Repoze-dev] [issue9] repoze.grok: create 'addgrokapp' script

Chris McDonough added the comment: dead. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue9> __ ___ Repoze-dev mailing list R

[Repoze-dev] [issue8] repoze.grok: create 'addgrokuser' script

Chris McDonough added the comment: Dead. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue8> __ ___ Repoze-dev mailing list R

[Repoze-dev] [issue98] repoze.who Identifier Issue

Chris McDonough added the comment: For the record, in repoze.who 1.1, the userid string gets base64 encoded in the cookie so this should not be a problem. Old cookies continue to work via a b/c shim. I'm going to close this issue as a result. -- status: chatting ->

[Repoze-dev] [issue102] PluggableAuthenticationMiddleware throws exception on challenge()

Chris McDonough added the comment: This is fixed in the trunk and will be available in the 1.1 release; thanks for the report! -- status: unread -> resolved __ Repoze Bugs <http://bugs.repoze.org/is

[Repoze-dev] [issue104] AuthTktCookiePlugin deconnection doesn't work with Opera

Chris McDonough added the comment: Closing. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue104> __ ___ Repoze-dev mailing list R

Re: [Repoze-dev] object graph traversal question

F. Oliver Gathmann wrote: > I am really impressed by the number and quality of the comments I got on > my little newbie question! Seems we made the right choice by basing our > new server framework on repoze.bfg ;-) Sure, it was a great question that isn't really covered by the docs. Hopefully

Re: [Repoze-dev] object graph traversal question

F. Oliver Gathmann wrote: > > On 11/12/09 1:00 PM, Tim Hoffman wrote: >> Hi >> >> I have done some fairly extensive projects using traversal over a >> relational model and we did use intermediate container classes alot. >> Mainly because each major entity could have about 6 different classes >> of

Re: [Repoze-dev] object graph traversal question

F. Oliver Gathmann wrote: > Hello! > > Coming from Pylons, I'm a newbie to the object graph traversal world, so > this question might be slightly misplaced (but hopefully a no-brainer > for the bfg gurus...). > > I very much like the concept of looking up my model object before > dispatching t

[Repoze-dev] [issue36] editing a file in ZMI fails

Chris McDonough added the comment: Long dead. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue36> __ ___ Repoze-dev mailing list R

[Repoze-dev] [issue20] Word-wrapping in roundup is awful

Chris McDonough added the comment: Filed under "replace bugtracker at some point". ;-) -- status: chatting -> resolved __ Repoze Bugs <http://bugs.re

[Repoze-dev] [issue26] traceback attempting to edit an image in plone

Chris McDonough added the comment: Long dead. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue26> __ ___ Repoze-dev mailing list R

[Repoze-dev] [issue93] bfg_alchemy tests broken

Chris McDonough added the comment: Get this off the open bugs list. -- status: done-cbb -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue93> __ ___ Repoze-de

[Repoze-dev] [issue97] Macro support for repoze.bfg.jinja2

Chris McDonough added the comment: In the meantime, we've made repoze.bfg.jinja2 0.5 (available from pypi) provide macro support in a slightly different way. Thanks for the patches, however! -- status: chatting -> resolved __ Repoze Bug

[Repoze-dev] [issue94] Can't start shell in bfg_alchemy or bfg_routesalchemy projects

Chris McDonough added the comment: Get this off the open bugs list. -- status: done-cbb -> resolved __ Repoze Bugs <http://bugs.repoze.org/issue94> __ ___ Repoze-de

[Repoze-dev] [issue105] View resolution ordering differences between BFG 1.1a8 and 1.1b3

Chris McDonough added the comment: This turned out to be an application issue, not a framework issue. -- status: in-progress -> resolved __ Repoze Bugs <http://bugs.repoze.org/is

[Repoze-dev] [issue105] View resolution ordering differences between BFG 1.1a8 and 1.1b3

Chris McDonough added the comment: I cant replicate this with the following configuration on 1.1b3: In views.py: --- from webob import Response def my_view(context, request): return {'project':'starter'} def one(context, request): return Response(&#x

[Repoze-dev] [issue105] View resolution ordering differences between BFG 1.1a8 and 1.1b3

New submission from Chris McDonough : mcdonc: so malthe wrt this difference between 1.1a8 and 1.1b3, can you send me some sample view config zcml so i can figure out wtf happened because i cant see anything obvious in the changelong [5:00pm] malthe: mcdonc: http://pastie.org/692761 [5:00pm

Re: [Repoze-dev] Question about repoze.bfg.formish

george hu wrote: > Where should I put the css for the formish widgets? To be honest, I dont really have a good answer. I ported all that stuf more or less mechanically from mako. I guess just make them resolve using a directive in ZCML. Basically, wherever the CSS is used, it specifies a URL

Re: [Repoze-dev] Using bfgshell with a ZODB based project.

Steve Schmechel wrote: I caught that from advice you gave on another post and that was exactly the command from the second example in my original post. Unfortunately, that does not work either. (Ref: http://www.mail-archive.com/repoze-dev@lists.repoze.org/msg01422.html It may have worked for G

Re: [Repoze-dev] Using bfgshell with a ZODB based project.

Steve Schmechel wrote: > Is there a proper way to invoke bfgshell in a ZODB project? > (The code and configuration I am using is exactly from the tutorial > and everything else works fine.) The last argument you pass, "main" needs to change.. it needs to match the name of the "app" section in th

Re: [Repoze-dev] Package naming

Graham Dumpleton wrote: > > On Nov 3, 8:33 am, Malthe Borch wrote: >> 2009/11/2 Martin Aspeli : >> >>> I think it's better to use top-level namespaces to indicate ownership, >>> if nothing else to avoid the chance of things clashing. For the repoze >>> project to "claim" the wsgi.* namespace seem

Re: [Repoze-dev] Package naming

Nathan Van Gheem wrote: > Hello all, > > I realize my opinion may not matter very much, but as one who uses many > of the repoze packages often, I often wondered why the repoze namespace > was used for many of the packages. Because we're lazy and unoriginal. And we like being able to name a pa

[Repoze-dev] repoze.bfg 1.1b2 released

repoze.bfg 1.1b2 has been released. Yes, I know the releases have been coming at an unreasonable pace, sorry. You can install it via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg *or*, now that I've worked out a niggling bug that made installing it from PyPI a bit pa

Re: [Repoze-dev] repoze.bfg 1.1b1 released

Graham Dumpleton wrote: > > On Nov 2, 9:17 am, Chris McDonough wrote: >> repoze.bfg 1.1b1 has been released. >> >> ... >> >> - If a BFG app that had a route matching the root URL was mounted >>under a path in modwsgi, ala ``WSGIScriptAlias /myap

[Repoze-dev] repoze.bfg 1.1b1 released

repoze.bfg 1.1b1 has been released. It may be installed via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg The docs at http://docs.repoze.org/bfg/1.1 have been updated. This is the first beta release in the 1.1 series. It is only bugfixes. The changelog is as follows: 1

Re: [Repoze-dev] SQLAlchemy and Traversal

It looks ok to me, at least to the extent that I don't know if there one way of implementing __getitem__ is better than any other for purposes of traversal, as long as it returns the right answer. - C Nikos Papagrigoriou wrote: > Hi everyone, > > I used the bfg_alchemy paster template to creat

[Repoze-dev] BFG 1.1 / 2.X roadmap

Here's what's going to happen with BFG in the next few months: - BFG 1.1 will be released. This will happen fairly soon, hopefully within the next two weeks or so. - After BFG 1.1 is released, work will begin on BFG 2.0. - A small amount of backwards compatibility shedding will occur in BFG

[Repoze-dev] repoze.bfg 1.1a9 released

repoze.bfg 1.1a9 has been released It may be installed via: easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg The documentation at http://docs.repoze.org/bfg/1.1/ have been updated. This release is hopefully the last alpha release in the 1.1 series (hopefully only betas and

Re: [Repoze-dev] Question about using repoze.bfg.formish in url dispatch

georgehu wrote: > Chris McDonough wrote: >> You need something like >> > Regarding to the request.form(), I've tried to find document explaining > the usage but no luck. Can you give it more explaination? > There's probably nothing in the docs about it (the

Re: [Repoze-dev] bfg + logging

Andreas Reuleaux wrote: > Yes, I can have a look (not immediately though). > Should I just provide some patches or do you > want to give me svn write access (should I sign > some contributor agreement)? Either is fine, really. The contributor agreement page at http://repoze.org/contributing.html

Re: [Repoze-dev] bfg + logging

Andreas Reuleaux wrote: > > Maybe it would be good to have this in the bfg docs ? > - I mean: just a basic example to get something running > and a link to this tutorial - no details of how to make > a more complicated configuration - or is it just me, > that didn't know of this "hidden feature"

Re: [Repoze-dev] bfg + logging

A "hidden feature" of PasteDeploy (the package which defines the .ini format for a BFG .ini file) is that you can just inject something in the .ini format found at e.g. http://www.red-dove.com/python_logging.html#config into the BFG app .ini file (literally just paste it in to the BFG app .ini f

Re: [Repoze-dev] Question about using repoze.bfg.formish in url dispatch

Chris McDonough wrote: > The contract for what the __call__ may return a webob Response object or a > dictionary. This is the same contract as required of "views with renderers". > See > http://docs.repoze.org/bfg/1.1/narr/views.html#writing-views-which-use-a-renderer

Re: [Repoze-dev] Question about using repoze.bfg.formish in url dispatch

'AForm':Additem(self.context,self.request)} but it doesn't work. The contract for what the __call__ may return a webob Response object or a dictionary. This is the same contract as required of "views with renderers". See http://docs.repoze.org/bfg/1.1/narr/views.html#

[Repoze-dev] repoze.bfg 1.1a8 released

repoze.bfg web framework 1.1a8 has been released You can install it via: easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg The 1.1-series docs have been updated and are available at: http://docs.repoze.org/bfg/1.1/ This release is a general mishmash of bufgixes, features

Re: [Repoze-dev] Question about using repoze.bfg.formish in url dispatch

Something like this might work: george hu wrote: > I'm trying to use the repoze.bfg.formish by checking out the code from > svn. I have configured the configure.zcml successfully and using > formish:form directive in the file. According to the document, the > formish:form is kind of mirror

[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Chris McDonough added the comment: I mean that I personally don't know how to change the software based on your suggestions so far in a way that adds significant value, and that if WSGI2 will handle the encoding and decoding issues, maybe this should just do something better with r.who

[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Chris McDonough added the comment: I don't think this is actionable on any realistic level within our current implementation. This should be solved at lower layers. -- status: chatting -> resolved __ Repoze Bugs <http://bugs.repoze.o

[Repoze-dev] [issue101] AuthTktCookie should not try to decode userid based on value types

Chris McDonough added the comment: Apologies, I see no reason that the way the current authtkt plugin encodes userids needs to change. Given that this is a plugin, if you need alternate behavior, you can of course copy and change the implementation and distribute the modified version

[Repoze-dev] [issue101] AuthTktCookie should not try to decode userid based on value types

Chris McDonough added the comment: I need to take back the assumption of "monstrous, disastrous security hole" wrt. using the pickle module (or eval, as you suggest) because in this particular case, the cookie content is hashed and compared against a digest that includes a secre

[Repoze-dev] [issue101] AuthTktCookie should not try to decode userid based on value types

Chris McDonough added the comment: The plugin does too much. But it doesn't do so entirely stupidly: it does too much because people *wanted* it to do too much, and the casting magic is useful. People wanted the value of environ['repoze.who.identity']['repoze.who.user

[Repoze-dev] [issue101] AuthTktCookie should not try to decode userid based on value types

Chris McDonough added the comment: There is support in the plugin right now for the userid as an integer, as a long, as a unicode type, and as a string; if another type should become necessary to use as a user id, the plugin allows for it. The mechanism that turns the userid into bytes is

[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Chris McDonough added the comment: I believe this. On the other hand, I'm not sure that a 'charset' setting dedicated "to repoze.who" or "to repoze.what" is really sufficient. Who will set the charset? What will it be set to? What does it mean to i

[Repoze-dev] [issue101] AuthTktCookie should not try to decode userid based on value types

Chris McDonough added the comment: Thanks for the report. So to be honest, I can't find an issue with the current strategy. The mod_auth_tkt README actually contradicts itself here, saying in one section that it checks "user_data" for internal data, then in another se

Re: [Repoze-dev] Predicates on routes vs views

Malthe Borch wrote: > 2009/10/22 Chris McDonough : >> Do we just need to change the path matching syntax instead to get your >> *.html case to work? Is there another case for predicates? > > I think that in general, predicates make sense without the view on > s. Is ther

Re: [Repoze-dev] Predicates on routes vs views

Malthe Borch wrote: > 2009/10/22 Tres Seaver : >> The view predicates are there to allow selecting a particular view among >> several registered for the route or context: e.g., to dispatch to >> different views for GET versus POST for the same route / context and >> view name. > > It makes perfec

[Repoze-dev] repoze.bfg 1.1a7 released

repoze.bfg 1.1a7 has been released. Install via: easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg The documentation at http://docs.repoze.org/bfg has been updated. This release is a pure feature release, there are no backwards incompatibilities or deprecations: "bfg_view" d

[Repoze-dev] repoze.bfg 1.1a6 released

Hi, The repoze.bfg web framework version 1.1a6 has been released. You can install it via: easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg Highlights: new "xhr", "accept", and "header" predicates in view directives, internal changes to supports the Python dictionary API aga

Re: [Repoze-dev] trying to apply "row-level" security in SQLAlchemy + URL Dispatch

george hu wrote: > Okay, now I tried to change the RootFactory class as this: > > def __init__(self,environ): > matchdict = environ['bfg.routes.matchdict'] > page = matchdict.get('pagename',None) > if page == "APage": > self.__acl__=[(Allow,Everyone,'view'),(Allow,'e

Re: [Repoze-dev] trying to apply "row-level" security in SQLAlchemy + URL Dispatch

Chris McDonough wrote: > > Hi George, > > Have you read > http://docs.repoze.org/bfg/1.1/narr/urldispatch.html#using-repoze-bfg-security-with-url-dispatch > > ? Never mind, I see that you have. The model object is not the context in this situation. The context is

Re: [Repoze-dev] trying to apply "row-level" security in SQLAlchemy + URL Dispatch

george hu wrote: > According to the document, "A common thing to want to do is to attach an > __acl__ to the context object dynamically for declarative security > purposes", I moved __acl__ statement from RootFactory class to the Page > class, as in the following code: > > class Page(Base): >

[Repoze-dev] repoze.bfg 1.1a5 released

repoze.bfg 1.1a5 has been released. You may install it using the following command: easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg It is also on PyPI. This release is mostly a documentation improvement and speed improvement release. The changelog follows: 1.1a5 (2009-10-

Re: [Repoze-dev] zope.schema, zope.formlib in bfg? or help a newb understand zca coolness

Martin Aspeli wrote: > Thomas G. Willis wrote: > >> I was kind of expecting that the book would have some gaps as far as bfg >> goes. I was hoping that going through the exercise of struggling through >> those gaps would help me arrive at a better understanding of all things >> zope(a lofty goa

Re: [Repoze-dev] zope.schema, zope.formlib in bfg? or help a newb understand zca coolness

ze.org/repoze.bfg.formish/trunk/ I hope to have a release of this out within the next few weeks. Martin Aspeli wrote: > Chris McDonough wrote: >> +1 to what Martin wrote, with something else that can only add to the >> confusion: recently I have been using Formish (http://is

Re: [Repoze-dev] zope.schema, zope.formlib in bfg? or help a newb understand zca coolness

+1 to what Martin wrote, with something else that can only add to the confusion: recently I have been using Formish (http://ish.io) to do autogenerated forms. I think both zope.formlib and z3c.form try to paint forms based on "model" objects; formish doesn't even try. It just lets you create

Re: [Repoze-dev] Minor Typo in xml-rpc docs

Thanks Kevin. This was actually already fixed in SVN but the docs rendering hadn't been updated for a while. I just updated it. - C Kevin J. Kalupson wrote: > Hi, > I spotted a minor typo on http://docs.repoze.org/xmlrpc/ . > > near the top - > easy_install -i http://dist.repoze.org/bfgs

<    1   2   3   4   5   6   7   8   >