Tim Hoffman wrote:
Hi Chris
You are correct, I just didn't want to see the view directive just
disappear and be left with a page implementation ;-).
I just baked all this behavior into the view directive on the trunk. There
are no backwards incompatibilities.
- C
A new alpha release of repoze.bfg 1.1 (alpha 2) was released this evening. It
contains two new features: view directives can now name a template and an
attribute. See the changelog below for descriptions of these features.
1.1a2 (2009-09-14)
==
- A ZCML ``view`` directive
on each template rendering and their results
will be jammed into the top-level namespace.
Robert Marianski wrote:
On Mon, Aug 24, 2009 at 10:11:04PM -0400, Chris McDonough wrote:
I like this.
Some variations:
- Have IOWrap be a multiadapter on context and request, so we can vary the
o-wrap
implementation=.page.MyPageView/
Seems a little clunky though, eh?
- C
T
On Sun, Sep 13, 2009 at 5:43 AM, Chris McDonough chr...@plope.com wrote:
So I've been trying to puzzle out some issues, which might or might not
be related to this topic.
In KARL, we currently write all of our views
The output of the threads debug middleware you put up at
http://pastebin.org/16704 looks more or less normal to me. You might
try a different WSGI HTTP server to see if that has any effect.
- C
simahawk wrote:
Thank you Tim!
It seems the only thing I can do is try to use twisted. Am I
the best
behaved of the bunch.
- C
On Thu, 2009-09-10 at 12:51 -0400, Chris McDonough wrote:
The output of the threads debug middleware you put up at
http://pastebin.org/16704 looks more or less normal to me. You might
try a different WSGI HTTP server to see if that has any effect.
- C
simahawk wrote:
hi list,
I created a web-service with repoze.bfg and repoze.bfg.xmlrpc with a
xmlrpx_view. This views creates a PDF and it should return me a simple
string with the url of the PDF but in order to get my string back I need
to restart repoze 'cause the application hangs at
Chris McDonough chr...@plope.com added the comment:
FTR, this is actually a Paste issue, not a repoze.who issue. The only way to
solve this would be
to change Paste's paste.auth.auth_tkt module or disuse it.
--
status: unread - chatting
__
Repoze Bugs
Chris McDonough chr...@plope.com added the comment:
Deferring this due to lack of response.
--
status: chatting - deferred
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue85
Chris McDonough chr...@plope.com added the comment:
Grok now ships with WSGI support out of the box, so repoze.grok is no longer
necessary.
--
assignedto: - chrism
status: in-progress - resolved
__
Repoze Bugs b...@bugs.repoze.org
http
Chris McDonough chr...@plope.com added the comment:
This must have been solved upstream by now in later Zope releases (egg Product
packages).
--
assignedto: - chrism
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org
Chris McDonough chr...@plope.com added the comment:
Thanks. A modified version of this patch has been checked into SVN.
--
assignedto: - chrism
nosy: +chrism
status: unread - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue95
Chris McDonough chr...@plope.com added the comment:
Wiggy reports this as fixed.
--
assignedto: - paul
nosy: +paul
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue23
Chris McDonough chr...@plope.com added the comment:
Wiggy reports this as fixed.
--
assignedto: - tseaver
nosy: +tseaver
status: testing - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue24
Chris McDonough chr...@plope.com added the comment:
OK.. I think at least that should be fixed before we merge. Also, fwiw, more
than one BFG
application can run in the same process space. In such a configuration, using
a global makes
less sense than using the component registry (each bfg
repoze.bfg 1.1a1 was released today.
New docs exist at http://docs.repoze.org/bfg/1.1/
The 1.0 docs continue to exist at http://docs.repoze.org/bfg/1.0
You can install repoze.bfg 1.1a1 via:
easy_install -i http://dist.repoze.org/bfg/1.1/simple repoze.bfg
This release is a feature release.
On 9/3/09 3:40 PM, Iain Duncan wrote:
Hey folks, I have some stuff in middleware that I need my models in a
bfg traversal graph to be able to get at.
Using request parameters in model code is technically unsupported.In the
bfg
mindset, models need no access to the request environment.
On 9/3/09 6:19 PM, Iain Duncan wrote:
On Thu, 2009-09-03 at 18:15 -0400, Chris McDonough wrote:
Using request parameters in model code is technically unsupported.In the
bfg
mindset, models need no access to the request environment. But please
check
out the repoze.bfg.threadlocal
Chris McDonough chr...@plope.com added the comment:
Thanks for the report!
I think the only suggestion I can make about this is don't do that. Instead,
check the callback info sent in as the second argument to determine which
transition is happening. The callback info's transition
On 8/28/09 2:24 PM, Iain Duncan wrote:
On Fri, 2009-08-28 at 14:07 -0400, Chris McDonough wrote:
Hi Iain,
Use an ini file setting in your bfg app's paste.ini section like:
configure_zcml = /path/to/configure.zcml
Would this also work if put in a pylons ini file? Or do you know what
else
I like this.
Some variations:
- Have IOWrap be a multiadapter on context and request, so we can vary the
o-wrap based on request type too (e.g. IManagementRequest vs.
IRetailRequest).
- If IOWrap can't be adapted, just return the result of the view (instead of
throwing a component lookup
Thanks... I may forget about this as I'm at a sprint but it's a good tip.
- C
On 8/21/09 2:39 PM, Fabio Tranchitella wrote:
Hello,
repoze.zcml depends on zope.testing, but I think it is a typo in setup.py:
zope.testing should go to the test dependencies.
Thanks,
Fabio
Chris McDonough chr...@plope.com added the comment:
Please use:
For the alchemy template:
./bin/paster --plugin=repoze.bfg bfgshell MyProject.ini alchemy
For the routesalchemy template:
./bin/paster --plugin=repoze.bfg bfgshell MyProject.ini sql
--
status: unread - done-cbb
On 8/20/09 10:18 PM, Iain Duncan wrote:
in a bfg app, is there a way to find all the objects that implement and
interface? I know we can do it the other way around ( get the interfaces
provided by an object ), but not sure how to programmatically find the
factory for making objects that
On 8/9/09 8:16 AM, Martin Aspeli wrote:
Hi,
I've been debugging some weirdness with deliverance 0.3 in front of
repoze.vhm and the vhm_xhosts middleware, which specifically happens
when the VHM host has a port in it (e.g. localhost:8000).
Basically, Deliverance uses webob.Request, and in
On 7/30/09 2:07 PM, george hu wrote:
Hi Chris,
I'm confused about the callable here. According to the official
python document - Note that classes are callable (calling a class
returns a new instance); class instances are callable if they have a
call() method. When I look at the code of the
On 7/24/09 6:23 PM, george hu wrote:
In the chapter of Add authorization, we create a root factory in
the model.py,
class RootFactory(object):
__acl__ = [ (Allow, Everyone, 'view'), (Allow, 'editor', 'edit') ]
def __init__(self, environ):
A bugfix release of repoze.bfg was released today.
The docs at http://docs.repoze.org/bfg/current/ have been updated.
To get the new release, use:
easy_install -i http://dist.repoze.org/bfg/current -U repoze.bfg
The changelog follows...
1.0.1 (2009-07-22)
==
- Added support
Thanks! I'll make a push of the docs today.
On 7/20/09 9:37 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
leopay wrote:
http://static.repoze.org/bfgdocs/narr/urldispatch.html#example-4
This code seems to have problems
class Article(object):
def __init__(self,
No, there is no demo code I'm aware of.
On 7/15/09 6:03 PM, david bain wrote:
Is there working demo code with these two together?
On Wed, Jul 15, 2009 at 6:01 PM, george hu geo...@gmail.com
mailto:geo...@gmail.com wrote:
I'm wondering anybody can write an example or step-by-step work
On 7/13/09 7:59 AM, Alberto Valverde wrote:
Hello,
I'm factoring out the core logic of a bunch of views into a generic CRUD
controller for a bfg app which looks something like this:
class GenericCrud(..):
def __init__(self, bunch of configuration options):
# update __dict__
On 7/8/09 2:54 AM, Iain Duncan wrote:
On Wed, 2009-07-08 at 02:36 -0400, Chris McDonough wrote:
We don't have a convention for flash. I've been remiss in seeing how the
other frameworks implement this, but I *think* something like this would be
closest:
return render_template_to_response
On 7/8/09 9:23 AM, david bain wrote:
Okay, I needed libxslt-dev also.
sudo apt-get install libxslt-dev libxml2-dev
seems to have done it. This needs to be mentioned, preferably right next
to the instructions for getting repoze.shootout and the other sample
applications.
Is 'python
One thing that those docs don't really make clear is that this functionality
comes from an add-on package:
easy_install -i http://dist.repoze.org/bfgsite/simple repoze.bfg.xmlrpc
- C
On 7/6/09 9:37 PM, Reed O'Brien wrote:
On Jul 6, 2009, at 9:23 PM, Tim Hoffman wrote:
Hi
I seem to
We can always do a better job at documentation discoverability and indexing and
searching and such, and we will over time. Currently the only docs that are
indexed on bfg.repoze.org are the actual BFG docs themselves, apologies.
That said, if I type in repoze.bfg xmlrpc to Google, the first
On 7/6/09 10:46 PM, Chris McDonough wrote:
We can always do a better job at documentation discoverability and indexing
and
searching and such, and we will over time. Currently the only docs that are
indexed on bfg.repoze.org are the actual BFG docs themselves, apologies.
That said, if I
Thanks Carlos... it's fixed; the ZEO server wasn't started.
- C
On 7/5/09 3:50 PM, Carlos de la Guardia wrote:
I'll have some time later tonight and I plan to do a few CSS fixes to
the site, since people other than us may take a look when the
announcement is out.
Right now, however, there's
repoze.bfg 1.0b1 is in the bfg current index
(http://dist.repoze.org/bfg/current/simple). The docs rendering at
http://docs.repoze.org/bfg has been updated.
Here's the change log:
1.0b1 (2009-07-02)
==
Features
- Allow a Paste config file (``configure_zcml``) value
On 7/2/09 4:12 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malthe Borch wrote:
2009/7/2 Tim Hoffmant...@zute.net:
I think you woul lose that capability with just name based registrations.
Yes, but perhaps for the better; it was always problematic to use
component
I know. This is getting tedious for me too. But another alpha release
(hopefully the last) is now in the http://dist.repoze.org/bfg/current index .
I
broke down and made ZCML directives for all the authentication policy and
authorization policy implementations included in BFG; as a result,
On 6/30/09 1:39 AM, Iain Duncan wrote:
Let's imagine a view pets:
from webob import Response
def pets(context, request):
return Response ('OK')
when a URL comes in that is for a paricular pet:
from webob import Response
def pets(context, request):
if request.subpath:
1.0a7 is a feature release which extends the resource feature required by a
customer; now it is possible to override static resources as well as templates.
There are no backwards incompatibilities. Tres also improved the
bfg_alchemy Paster template.
The bfg current index at
repoze.bfg 1.0a5 was a bit of a browbag release. 1.0a6 has been released to
fix
the feature added in 1.0a5. The changelog is:
1.0a6 (2009-06-29)
==
Bug Fixes
-
- Use ``caller_package`` function instead of ``caller_module``
function within ``templating`` to avoid
If nobody finds any showstopper bugs, repoze.bfg 1.0 will be released on or
before Monday July 6. Speak now or forever hold your peace wrt to API issues;
after 1.0 the existing APIs will be frozen.
- C
___
Repoze-dev mailing list
On 6/29/09 8:26 PM, Iain Duncan wrote:
I'm wondering what the conventional wisdom is for doing bfg apps to
handle crud operations with urls like
/pet - list pets
/pet/1 - view pet model, id 1
/pet/1/view
/pet/1/edit - edit pet model, id 1
Is this something that can be handled well
Hi,
repoze.bfg 1.0a5 has been released. This is a feature release, unfortunately.
We (Agendaless) needed this feature for a customer. I apologize for a
feature
addition this late in the alpha cycle. The feature is generally useful: a
resource ZCML directive that allows template (and other
I think what your first question boils down to is how to I make a view
redirect
to itself. The answer is usually:
from repoze.bfg.url import model_url
url = model_url(context, request, request.view_name)
As far as examples about form handling, the sample apps at
I've seen people use (or at least report using):
- ToscaWidgets
- formish
I've personally used ToscaWidgets on at least one bfg customer project,
although
we wound up removing it later in favor of just using ZPT macros.
- C
On 6/27/09 3:47 PM, Iain Duncan wrote:
what are folks using to
A workaround for this symptom was added to repoze.who 1.0.14 (contributed by
Gustavo Narea) which allows the auth_tkt configuration to specify a
userid_checker. If you pass a callable in to the auth_tkt identifier
plugin's
constructor, that callable will be called with the userid; if it
On 6/25/09 3:34 AM, Iain Duncan wrote:
First off, I am super impressed by the effort put into the bfg docs. The
ratio of docs to code is fantastic and IMHO bodes very well for
adoption. =)
Second, I'm finding some small typos that could be confusing to total
beginners. What's the routing for
On 6/25/09 3:38 AM, Chris Withers wrote:
Shane Hathaway wrote:
I'm not very familiar with pip, but I don't think that's an issue for
Buildout. Buildout also has the ability to pin the version of all
packages, but I don't think that's what Jens and I want in this case.
yep, the only thing
On 6/25/09 5:35 AM, Iain Duncan wrote:
On Wed, 2009-06-24 at 04:09 -0400, Chris McDonough wrote:
Just a heads up.
BFG currently uses Routes (http://routes.groovie.org) to do URL pattern
matching.
While fleshing out URL generation and matching support for BFG url
dispatch,
I've come
I just released repoze.bfg 1.0a3 to the BFG current index
(http://dist.repoze.org/bfg/current/simple). This release removed a dependency
on Routes and fixed bugs related to running BFG on GAE.
The documentation at http://docs.repoze.org/bfg has also been updated.
1.0a3 (2009-06-24)
repoze.bfg 1.0a2 is out (in the http://dist.repoze.org/bfg/current/simple
index)
with the following changes:
1.0a2 (2009-06-23)
==
Bug Fixes
-
- The ``bfg_routesalchemy`` paster template app tests failed due to a
mismatch between test and view signatures.
Features
On 6/22/09 11:48 AM, Nathan Yergler wrote:
I'm trying to use repoze.bfg.traversalwrapper instead of baking in
location awareness. It appears that the names used to identify
virtual host information drifted apart between repoze.bfg and
traversalwrapper. When trying to run I get a key error on
repoze.bfg.traversalwrapper 0.3, with BFG 1.0a1 compatibility, is in the
following indexes:
http://dist.repoze.org/bfg/current/simple
http://dist.repoze.org/bfg/dev/simple
- C
On 6/22/09 12:17 PM, Chris McDonough wrote:
On 6/22/09 11:48 AM, Nathan Yergler wrote:
I'm trying to use
I have released two new packages to PyPI. These packages were inspired by
(design almost entirely stolen from) zope.component and zope.configuration. I
don't really expect them to get much use, but writing them was enlightening.
Maybe they'll be interesting to someone who wants to introduce
On 6/22/09 4:22 PM, Chris Rossi wrote:
On Mon, Jun 22, 2009 at 3:52 PM, Chris McDonough chr...@plope.com
mailto:chr...@plope.com wrote:
http://svn.repoze.org/repoze.component/trunk/
This package differs from zope.component inasmuch as it disuses the
concept of
interface
Thanks for the report back George, glad it worked out for you...
On 6/22/09 5:25 PM, George Wright wrote:
Apologies for sending again - forgot to modify the Subject Line!
Chris
I installed a new python, a new virtualenv and created a new project as
suggested.
And all worked well!
Thanks
On 6/19/09 7:54 PM, George Wright wrote:
Hi. I'm new to this list.
Just wanted to record some problems using beginners tutorial.
The tutorial is excellent and well explained. Maybe it can be improved
if the glitches I encountered are fixed.
I haven't searched archives for previous discussion
at the very least and see value in putting it in
the docs if not already there. Might be that folks won't get it but
those that take time to understand both routing methods will find value
and possibilities in what you have done. Many thanks.
Regards,
David
On 11-Jun-09, at 11:10 PM, Chris McDonough
On 6/17/09 2:52 PM, Hanno Schlichting wrote:
On Wed, Jun 17, 2009 at 8:42 PM, Douglas Mayledoug...@openplans.org wrote:
I've been doing some testing of a new site, and I've used repoze.who
and repoze.what for authentication, and authorization respectively. I
did notice one unusual behavior
r.who 1.0.14 released with a fix like this.
- C
On 6/17/09 3:10 PM, Gustavo Narea wrote:
Chris said:
How did I miss this? This is a pretty good interim idea; thanks Gustavo.
I'll try to merge it in with the current state of affairs.
Cool ;-)
Cheers,
On 6/13/09 9:33 AM, Andreas Reuleaux wrote:
has anyone had a look at bobo (recently created
by Jim Fulton)?
http://bobo.digicool.com/
Seems similar in spirit to bfg, I wonder
why he doesn't want to join bfg development.
Maybe it's just for fun?
- C
FWIW, I took the redirect out for:
http://static.repoze.org/whatdocs
It now renders a copy of the what docs that are hosted on repoze.org.
- C
On 6/11/09 12:23 PM, Gustavo Narea wrote:
Hi, everyone.
Jorge's right, my personal server, which hosts code.gustavonarea.net and
what.repoze.org,
). But it might be an answer to reducing
some complexity.
On 6/10/09 11:21 PM, Chris McDonough wrote:
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
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
Tres was after the same thing earlier today so I think it's a good idea.
We could also change the PersistentApplicationFinder to look in the environment
for an open connection and use it instead of trying to open one itself.
On 6/9/09 4:16 PM, Shane Hathaway wrote:
Hi all,
I have been
On 6/9/09 4:25 PM, Chris McDonough wrote:
Tres was after the same thing earlier today so I think it's a good idea.
We could also change the PersistentApplicationFinder to look in the
environment
for an open connection and use it instead of trying to open one itself.
(FTR, I didn't mean
setup.py develop.
- C
On Tue, Jun 2, 2009 at 11:49 AM, Chris McDonough chr...@plope.com
mailto:chr...@plope.com wrote:
Hi George,
0.9.1 has now been released with a fix for this problem.
You can upgrade to it by doing:
bin/easy_install -U -i http://dist.repoze.org/bfg
Thanks Paul, I applied this patch.
- C
On 6/8/09 10:56 AM, Paul Johnston wrote:
Hi,
I've put a patch on the ticket http://bugs.repoze.org/issue83
To avoid the issue of the default to set, and for
backward-compatibility, this patch defaults to no timeout.
Paul
On 6/8/09 1:12 PM, george hu wrote:
And
then I switch to project directory and run
python setup.py develop
and it runs without issue. Then I run
paster --plugin=repoze.bfg bfgshell MyProject.ini main , it shows the
following error:
pkg_resources.DistributionNotFound: repoze.tm
On 6/8/09 4:51 PM, george hu wrote:
Now the problem is gone.
Good, sorry about that. It was another bug. :-( I've fixed it in SVN.
One question, the bfgshell command has changed to
..\scripts\paster --plugin=repoze.bfg bfgshell .ini alchemy
what is the difference between main and
On 6/8/09 7:10 PM, Chris Shenton wrote:
I've been plugging along with a routes and SQL based app, with BFG
0.8.0. I just changed my buildout.cfg to get BFG 0.9.1 -- and any new
versions of other packages -- but it's now throwing exceptions when
trying to render. I've removed any *.py, *.pyc
Chris McDonough chr...@plope.com added the comment:
I merged a modified version of your patch to the trunk, thanks Sean!
--
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue88
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.::
On 6/3/09 10:29 AM, Stephan Altmueller wrote:
Hi
It seems that model_url does not work correctly with routes that
do not contain dynamic parts. This worked in 0.7.x but not 0.8 and 0.9.
Could someone tell if/what I am doing wrong.
Here is my routes definition in configure.zcml:
route
On 6/2/09 8:08 AM, Reed O'Brien wrote:
Finished a once over the API docs.
Possible nit:
location.html#repoze.bfg.location.locate
I don't like locate as the name for the function as I expect it to
find me something rather than make something location aware.
I would expect it o be
On 6/2/09 12:27 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris McDonough wrote:
On 6/2/09 8:08 AM, Reed O'Brien wrote:
Finished a once over the API docs.
Possible nit:
location.html#repoze.bfg.location.locate
I don't like locate as the name for the function
Hi George,
0.9.1 has now been released with a fix for this problem.
You can upgrade to it by doing:
bin/easy_install -U -i http://dist.repoze.org/bfg/current/simple repoze.bfg
On 6/1/09 5:31 PM, george hu wrote:
When I run paster create -t bfg_alchemy as per the documentation
instructed, it
The 0.9 release features the separation of an authentication policy and an
authorization policy (previously there had been only a security policy), plus
some additional authentication-related API support via the forget and
remember APIs. It also comes with a new scripting module (for scripts
On 6/1/09 4:00 AM, Chris McDonough wrote:
The 0.9 release features the separation of an authentication policy and
an authorization policy (previously there had been only a security
policy), plus some additional authentication-related API support via
the forget and remember APIs. It also comes
Chris McDonough chr...@plope.com added the comment:
Hi Douglas,
Sorry for not responding til now; the worthwhile patches always require more
thought than plain bugreports. Thanks for the submission!
(FTR, I tried to apply the patch but it has a syntax error on line 267. That
was easy to fix
The last time I wrote a missive about BFG security pluggability, I
talked about breaking the existing security policy into two things:
an authentication policy and an authorization policy and put some code
up to show how that could be done.
So, that's now done and on the trunk (which will become
Version 0.9a1 of repoze.bfg has been released. It is the first release which
makes a distinction between an authorization policy and an authentication
policy. Older versions had a security policy which performed both
authentication and authorization, but it's much more frequent to only need
On 5/26/09 1:50 AM, Malthe Borch wrote:
2009/5/25 Chris McDonoughchr...@plope.com:
So to the end of breaking them apart, I just wrote up a bit of science
fiction
in code form. Could you take a look at the below and let me know what you
think?
It's very clear.
Cool. I've implemented
On 5/26/09 4:07 AM, Chris McDonough wrote:
On 5/26/09 3:52 AM, Wichert Akkerman wrote:
Previously Chris McDonough wrote:
def remember(self, principal, token):
Return a set of headers suitable for 'remembering' the
principal on subsequent requests
def
On 5/26/09 4:16 AM, Wichert Akkerman wrote:
Previously Chris McDonough wrote:
On 5/26/09 3:52 AM, Wichert Akkerman wrote:
Previously Chris McDonough wrote:
def remember(self, principal, token):
Return a set of headers suitable for 'remembering' the
principal
On 5/26/09 4:20 AM, Wichert Akkerman wrote:
from repoze.bfg.security import logout
def someview(context, request):
response = render_template_to_response('some.pt')
logout(response)
return response
vs.
from repoze.bfg.security import forget
def someview(context,
Hi all,
The current security policy abstraction in BFG is a bit brittle because it
conflates authentication and authorization APIs. Thus we get things like
RepozeWhoIdentityInheritingACLSecurityPolicy and
RemoteUserInheritingACLSecurityPolicy.
I'd like to tease apart the bits of the current
repoze.bfg 0.8.1 was just released (to the
http://dist.repoze.org/bfg/current/simple index) with the following features:
- Class objects may now be used as view callables (both via ZCML and
via use of the ``bfg_view`` decorator in Python 2.6 as a class
decorator). The calling semantics
Chris McDonough chr...@plope.com added the comment:
We're actually trying to encourage people to release plugins in separate
packages these days. This is a good candidate. I'm going to mark this one as
resolved as a result, although really the task is to create a separate Python
package
Chris McDonough chr...@plope.com added the comment:
You can currently write your own metadata plugin which could try to get info
from a cookie value first, then the database. Or better yet, retrieve the data
from cache instead of the database or a cookie.
But in general, yes, the eagerness
Chris McDonough chr...@plope.com added the comment:
Fixed in r4790 of the trunk, thank you.
--
status: unread - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue75
Chris McDonough chr...@plope.com added the comment:
Form plugins will be deprecated for common use in the next release of r.who,
FWIW. It's much easier to tell people to return a login form as their
unauthorized response rather than trying to challenge based on a 401
response from
Chris McDonough chr...@plope.com added the comment:
Note that you can use the identity or environ passed in to an authenticator
as a scratchpad to communicate with other plugins (such as the challenger).
--
status: unread - resolved
__
Repoze Bugs b
Chris McDonough chr...@plope.com added the comment:
What you ended up doing is the recommended standard right now. Thanks for the
report.
--
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue58
On 5/19/09 10:44 PM, Chris McDonough wrote:
On 5/19/09 10:05 PM, Stephan Altmueller wrote:
Hi,
I might be missing something, but it seems that in bfg 0.8 every
routes context can only have one view associated with it.
In 0.7.1 you could have something like this
view
name=itemview
On 5/12/09 11:54 AM, Hanno Schlichting wrote:
Chris McDonough wrote:
I think this package is becoming less repoze.zope2 than some other more
experimental system. Which is fine. But there's no way I'm going to be able
to give people help with it on IRC or the maillist when it breaks because
On 5/11/09 1:55 PM, Sebastien Douche wrote:
On Mon, May 11, 2009 at 15:39, Chris McDonoughchr...@plope.com wrote:
But in this case, I think this build failed because we're missing a more
recent version of Routes from the http://dist.repoze.org/bfg/dev/simple/
index.
Right.
The virtualenv
301 - 400 of 464 matches
Mail list logo
