[Repoze-dev] bfg- Routes...

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 to the conclusion that it's probably a better long-term strategy to just write some simple regex generatio

[Repoze-dev] bfg vs buildout

Hey All, Just been reading http://docs.repoze.org/bfg/narr/install.html and I notice a conspicuous absence of zc.buildout... Do you guys recommend not using buildout? If not, are there docs anywhere for using BFG in a buildout context? cheers, Chris -- Simplistix - Content Management, Zope &

[Repoze-dev] BFG testing

Hi All, I see BFG uses the tests_require parameter to setuptools' setup function rather than the "normal zope way" of an extra_requires dict with a 'test' key. What's the difference between these two from your perspective and what made you guys choose tests_require over extra_requires? Also,

Re: [Repoze-dev] bfg vs buildout

Am Wed, 24 Jun 2009 10:54:33 +0100 schrieb Chris Withers: > Hey All, > > Just been reading http://docs.repoze.org/bfg/narr/install.html and I > notice a conspicuous absence of zc.buildout... > > Do you guys recommend not using buildout? If not, are there docs > anywhere for using BFG in a buildo

Re: [Repoze-dev] bfg vs buildout

Jens W. Klein wrote: > - > [buildout] > extensions = buildout.dumppickedversions > parts = instance > eggs-directory = ${buildout:directory}/eggs > find-links = > http://dist.repoze.org/bfg/1.0/ > > [instance] > recipe = repoze.recipe.egg:scripts > eggs = > repoze.bfg > --

Re: [Repoze-dev] bfg vs buildout

On Wed, Jun 24, 2009 at 9:16 AM, Chris Withers wrote: > > Also, how do you wire running tests, particularly running them with > nose, into this? > > bin/nosetests path/to/src Chris ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.rep

Re: [Repoze-dev] bfg vs buildout

Chris Rossi wrote: > On Wed, Jun 24, 2009 at 9:16 AM, Chris Withers > wrote: > > > Also, how do you wire running tests, particularly running them with > nose, into this? > > bin/nosetests path/to/src ...having added nosetests as a dependent egg, right? H

Re: [Repoze-dev] bfg vs buildout

On Wed, Jun 24, 2009 at 9:22 AM, Chris Withers wrote: > > > How/where do you encapsulate options to nosetests such that they don't have > to be continuously re-typed? > > The project I work on where we do this, we just write a shell script and check it in to svn. If you were to look in the Karl

Re: [Repoze-dev] bfg vs buildout

Am Wed, 24 Jun 2009 14:16:38 +0100 schrieb Chris Withers: > Jens W. Klein wrote: [...] >> Missing is a version fixation like done in ZTK, Grok, Plone, ... I'd >> really like to see such a version.cfg for each repoze release. Creation >> could be automated. > > Why don't you just replace find-link

Re: [Repoze-dev] bfg vs buildout

Am Mittwoch, den 24.06.2009, 08:52 -0400 schrieb Chris Rossi: [...] > Not really missing, just done in a different way. The index itself is > populated only with a KGS and maintained to be up to date. The > Agendaless guys also typically make a private index for each customer > project that the

Re: [Repoze-dev] bfg vs buildout

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens W. Klein wrote: > Am Wed, 24 Jun 2009 10:54:33 +0100 schrieb Chris Withers: > >> Hey All, >> >> Just been reading http://docs.repoze.org/bfg/narr/install.html and I >> notice a conspicuous absence of zc.buildout... >> >> Do you guys recommend not

Re: [Repoze-dev] BFG testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: > I see BFG uses the tests_require parameter to setuptools' setup function > rather than the "normal zope way" of an extra_requires dict with a > 'test' key. > > What's the difference between these two from your perspective and

Re: [Repoze-dev] bfg vs buildout

Chris Rossi wrote: > > > (karl3)ch...@opportunity:~/proj/karl3/src/karl$ cat test > ../../bin/nosetests $* > > So, we just do: > > $ cd src/karl > $ ./test Hackish, but I guess functional. Sadly not cross platform. I wonder if a little buildout recipe is in order? I see: http://pypi.python.

Re: [Repoze-dev] BFG testing

Tres Seaver wrote: >> I see BFG uses the tests_require parameter to setuptools' setup function >> rather than the "normal zope way" of an extra_requires dict with a >> 'test' key. >> >> What's the difference between these two from your perspective and what >> made you guys choose tests_require o

Re: [Repoze-dev] bfg vs buildout

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: > Chris Rossi wrote: >> On Wed, Jun 24, 2009 at 9:16 AM, Chris Withers > > wrote: >> >> >> Also, how do you wire running tests, particularly running them with >> nose, into this? >> >> bin/nos

Re: [Repoze-dev] bfg vs buildout

Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Chris Withers wrote: >> Chris Rossi wrote: >>> On Wed, Jun 24, 2009 at 9:16 AM, Chris Withers >> > wrote: >>> >>> >>> Also, how do you wire running tests, particularly running them with >>>

Re: [Repoze-dev] bfg vs buildout

Am Wed, 24 Jun 2009 09:59:14 -0400 schrieb Tres Seaver: [..] >> Missing is a version fixation like done in ZTK, Grok, Plone, ... I'd >> really like to see such a version.cfg for each repoze release. Creation >> could be automated. > > You shouldn't need to pin the versions if you would use the ind

Re: [Repoze-dev] bfg vs buildout

Jens W. Klein wrote: Am Wed, 24 Jun 2009 09:59:14 -0400 schrieb Tres Seaver: [..] Missing is a version fixation like done in ZTK, Grok, Plone, ... I'd really like to see such a version.cfg for each repoze release. Creation could be automated. You shouldn't need to pin the versions if you would

Re: [Repoze-dev] Installing repoze.bfg (George Wright)

Gidday Using repoze.bfg-1.0a1 I am working through the tutorial bfgwiki2 - up to adding authorization http://docs.repoze.org/bfg/tutorials/bfgwiki2/authorization.html When I attempt to edit a page and login as 'editor', 'editor' I get the following error displayed URL: http://127.0.0.1:6543/1 Fi

Re: [Repoze-dev] Installing repoze.bfg (George Wright)

Hi... please us repoze.bfg 1.0a2 (that's what the tutorial you're working from is based on). - C On 6/24/09 3:48 PM, George Wright wrote: > Gidday > Using repoze.bfg-1.0a1 > > I am working through the tutorial bfgwiki2 - up to adding authorization > http://docs.repoze.org/bfg/tutorials/bfgwiki2/

[Repoze-dev] repoze.bfg 1.0a3 released

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) =

Re: [Repoze-dev] Installing repoze.bfg (George Wright)

Ok Thanks works fine with repoze.bfg 1.0a3 George On 25/06/2009, at 5:56 AM, Chris McDonough wrote: > Hi... please us repoze.bfg 1.0a2 (that's what the tutorial you're > working from is based on). > > - C > > On 6/24/09 3:48 PM, George Wright wrote: >> Gidday >> Using repoze.bfg-1.0a1 >> >> I a

Re: [Repoze-dev] bfg vs buildout

Hi All, I've become a big fan of pip. The --freeze option is great. It seems that it lets you pin your versions all the way down. I'm just watching all of the pain with certain buildout recipes where I could imagine them easier to create if the person creating the recipe had the possibility

Re: [Repoze-dev] bfg vs buildout

z...@kevinkal.com wrote: > I've become a big fan of pip. The --freeze option is great. It seems > that it lets you pin your versions all the way down. I'm just watching > all of the pain with certain buildout recipes where I could imagine them > easier to create if the person creating the r

Re: [Repoze-dev] bfg vs buildout

Hi Shane, > z...@kevinkal.com wrote: >> I've become a big fan of pip. The --freeze option is great. It >> seems that it lets you pin your versions all the way down. I'm just >> watching all of the pain with certain buildout recipes where I could >> imagine them easier to create if the perso