gmane.comp.web.zope.grok.devel

Re: zope.app.file/zope.file buildout error

Danilo G B — 2012-05-23T12:39:39

Mauro, this was a very boring situation I had to handle some time ago.

After a long time I came up with this solution: include the snippet below before <grok:grok package="." /> in your configure.zcml. Soon you will learn that this way of handling files is not the best. I'm temporarily using an ancient version of dolmen.file (when it still depended on z3c.form). When the need comes, I'll probably have to write a package of my own since it seems people out there don't share this issue nor do they regarding a good solution.


<!-- zope.file requirements -->
  <include package="zope.browsermenu" file="meta.zcml" />
  <include package="zope.browsermenu" />
  <browser:menu id="zmi_views" title="ZMI Views" />
  <browser:menu id="zmi_actions" title="ZMI Actions" />




________________________________
---------------------------------------------------------------------

Message: 1
Date: Tue, 22 May 2012 17:48:54 +0200
From: Mauro Boschi <me< at >monadic.org>
To: grok-dev< at >zope.org
Subject: [Grok-dev] zope.app.file/

Re: zope.app.file/zope.file buildout error

Uli Fouquet — 2012-05-22T23:13:20

Hi Mauro,

On Tue, 22 May 2012 17:48:54 +0200 Mauro Boschi wrote:


This one is because of zope.file trying to register menus for the ZMI
(Zope Management Interface). As the ZMI is gone from Grok (since v1.2, I
think) along with a huge pile of dependencies, you get this error.

To 'solve' it temporarily, i.e. to start the tutorial, you can switch
back to an older Grok version by modfiying buildout.cfg:

  [buildout]
  #extends = http://grok.zope.org/releaseinfo/1.5.4/versions.cfg
  # Use grok toolkit version 1.1
  extends = http://grok.zope.org/releaseinfo/1.1/versions.cfg

With current grokprojects this won't be enough as newer grokprojects
would require some new packages that did not exist at time of 1.1
release. You therefore have to pin some versions also in buildout.cfg:

  [versions]
  # Override versions here.
  zc.recipe.egg = 1.3.0
  zc.buildout = 1.5.0
  zope.fanstatic = 0.9
  megrok.layout = 1.0.1
  grokcore.startup = 1.0.2

helped here. After rerunning bin/buildout (maybe also python
bootstrap.py

zope.app.file/zope.file buildout error

Mauro Boschi — 2012-05-22T15:48:54

Hi,
I've tried to run Music Tutorial but it doesn't work in song.py section ( http://grok.zope.org/documentation/tutorial/musical-performance-organizer-part-1 ). So I've tried zope.file how-to: http://grok.zope.org/documentation/how-to/uploading-file but it doesn't work too! :(

with a new grokproject test

I've added in buildout.cfg:
[zope_conf]
recipe = collective.recipe.template
input = etc/zope.conf.in
output = ${buildout:parts-directory}/etc/zope.conf
filestorage = ${buildout:directory}/var/filestorage
blobstorage = ${buildout:directory}/var/blobstorage
devmode = on
extra =

#I've added the devmode line to resolve another error.

Then I've added in setup.py:
      install_requires=['setuptools',
                        'grok',
                        'grokui.admin',
                        'fanstatic',
                        'zope.fanstatic',
                        'grokcore.chameleon',
                        'grokcore.startup',
                        # Add extra requirements here

Pickle namespace clash

Alex Leach — 2012-05-21T12:50:52

Dear Grok Devs,

I've got Grok set up on a number of machines, and have started getting some
errors on my Mac OS X Lion machine
I had Grok set up nicely using mod_wsgi and the Enthought Python
Distribution, so that I could take advantage of Enthought's MKL libraries
with numpy, but a recent buildout has somehow killed it.

The end of the paster error is below.


  File 
"/Users/albl500/.buildout/eggs/zope.configuration-3.7.4-py2.7.egg/zope/confi
guration/config.py", line 706, in finish
    actions = self.handler(context, **args)
  File 
"/Users/albl500/.buildout/eggs/z3c.autoinclude-0.3.3-py2.7.egg/z3c/autoinclu
de/zcml.py", line 51, in includeDependenciesDirective
    info = DependencyFinder(dist).includableInfo(['configure.zcml',
'meta.zcml'])
  File 
"/Users/albl500/.buildout/eggs/z3c.autoinclude-0.3.3-py2.7.egg/z3c/autoinclu
de/dependency.py", line 24, in includableInfo
    module = resolve(dotted_name)
  File 
"/Users/albl500/.buildout/eggs/zope.dottedname-3.4.6-py2.7.egg/zope/dottedna
me/resolve.py",

Re: pickling of dynamic classes

Leonardo Rochael Almeida — 2012-05-16T22:27:27

Hi,

You've hit the explanation exactly for your problem problem. The Pickle
module (and ZODB, by extension) can only store instances of classes that
exist at the top of modules.

This is because Pickle, when storing instances, stores the state of the
object (it's __dict__) with the name of the class and the name of the
module. When unpickling, It'll try to do the equivalent of:

module = sys.modules[module_name]
cls = getattr(module, class_name)
instance = cls.__new__()
instance.__dict__ = pickled_state

So, if your class does not exist at the top level, it can't be unpickled,
so it can't be pickled.

The only way to generate classes dynamically AND pickle their content is if
you store the generated class in some module. Something Like.

some_module.class_name = type('class_name', (<base class>,), dict())

However, this will only work if the above also happens before any class
instance is ever unpickled from the ZODB.

Hope it makes sense,

Cheers,

Leo

On Wed, May 16, 2012 at 1:24 PM, Anurag Sharma <a.sha

pickling of dynamic classes

Anurag Sharma — 2012-05-16T11:24:30

Dear All,

This seems to be generally a problem with pickle but I hope I will be able
to get some inputs for the problem.

In one function of my grok.Application class I'm dynamically creating a
class

self.VarName = type('class name', (<base class>,), dict())
* <base class> does inherit grok.Container.*

While running this I'm getting following error:

Module ZODB.serialize:*422* in serialize
<http://localhost:8080/bizopine#>
__getstate__*(**)**)*
Module ZODB.serialize:*431* in _dump        <http://localhost:8080/bizopine#>
*PicklingError: Can't pickle <class '<appname>.app.<class name>'>:
attribute lookup **<appname>.app.<class name>** failed*

Pickling documentation does say that :
What can be pickled and unpickledclasses that are defined at the top level
of a module

*But is it the problem here and if yes then what can be the possible
solution for this ?*

Thanks,
Anurag
_______________________________________________
Grok-dev mailing list
Grok-dev< at >zope.org
https://mail.zope.org/mailman/listinfo/grok-dev

grokcore.resource

Jan-Jaap Driessen — 2012-05-14T19:02:27

After the recent grok sprint I have spent some hours taking parts of
megrok.resource and putting them in the grokcore.resource package:

svn+ssh://svn.zope.org/repos/main/grokcore.resource/trunk

grokcore.resource helps you use fanstatic resources in your view
components. Instead of `needing` resources in the update method of
your view components, you can use a directive to associate resources
with a view component, so instead of::

class MyView(grok.View):
    def update(self):
        myresource.need()

You write::

class MyView(grok.View):
    grok.resources(myresource)

This removes a lot of one-line update methods from our code base,
which is good. grokcore.resource works for grok.View, grok.Viewlet,
grok.Layout and grok.ContentProvider view components.

Are you ok with making this a part of grok? I created a branch of grok
in which I incorporated grokcore.resource:

svn+ssh://svn.zope.org/repos/main/grok/branches/janjaapdriessen-grokcore-resource

I would like you to try this out in your own applicatio

Re: grokcore.resource

Jan-Jaap Driessen — 2012-05-14T18:54:30

Hi Danilo,

Thank you for your input.

On Wed, May 2, 2012 at 1:03 AM, Danilo G B <danilogbotelho< at >yahoo.com> wrote:

`resources` is a better name indeed. I changed it.


It was indeed not a good idea to include the resources of the parents
of an object. I removed this.


I am not sure how I feel about passing in the Layout class to the
`grok.resources` directive. I don't see an immediate use case in my
applications so I won't implement it now.


In the most recent release of grokcore.layout, this has been made
available as a "private" method. I am using that one to get to the
layout of a view.


Thanks for thinking with me. I will send a separate email to the
mailing list asking other developers to try grokcore.resource and
learn whether they find it useful.

Cheers,

JJ

Re: Static dir with grok.PageTemplateFile

Alex Leach — 2012-05-14T11:08:25

Hi Christian,

Thanks for that. I believe I am indeed using grokcore.view 2.7.

Soo, if I understand the CHANGES.txt correctly, I have to add a 
__static_name__ attribute to all forms that use the grok.PageTemplateFile 
directive, pointing to the relevant library.

Thanks, that works actually! In case anyone else comes across this, my form 
declaration now looks like:-


from app_name import resource

class AddSQLDatabaseForm(grok.AddForm):
grok.context(Server)
grok.implements(ISQLDatabase)
grok.name('addSQLdatabase')
form_fields = grok.AutoFields(ISQLDatabase)
template = grok.PageTemplateFile("edit-form.pt")
__static_name__ = resource.library

Cheers,
Alex


On Monday 14 May 2012 10:55:28 Christian Klinger wrote:
| Hi Alex,
| 
| we recently worked on the bavarian sprint on that topic. Which version
| of grokcore.view do you use?
| 
|  From the CHANGES.TXT in grokcore.view 2.7:
| 
| Fix how the static resource are found. Instead of using as name the
| package name where the component is defined, using

Re: Static dir with grok.PageTemplateFile

Christian Klinger — 2012-05-14T08:55:28

Hi Alex,

we recently worked on the bavarian sprint on that topic. Which version
of grokcore.view do you use?

 From the CHANGES.TXT in grokcore.view 2.7:

Fix how the static resource are found. Instead of using as name the 
package name where the component is defined, using as name the package 
where the template for the component is defined, or the base component. 
This is done by setting an attribute __static_name__ on the component 
that specify which resource directory should be used. This fix missing 
resources when you extend the component and don't redefined the template.

HTH

Christian

Alex Leach schrieb:

Static dir with grok.PageTemplateFile

Alex Leach — 2012-05-13T18:05:46

I have a few forms in separate modules that share the same template. Rather 
than having the template in the <module_name>_templates/ directory, I've got 
this one 'edit-form.pt' template in the bottom, src/ directory.

It worked fine, until I added a (conditional) include in the head of the page 
template, so that it downloads a CSS stylesheet if the form request wasn't 
done through an AJAX call.

So I'm getting an error now, whenever I request one of the forms which use 
this template, as it fails to find the static directory holding the CSS. I've 
tried adding `resource.style.need()` to the forms' update methods, but they 
still don't find the static directory. Part of the traceback shows this:-

Line 5, Column 10
In expression: <PathExpr standard:u'static/css/style.css'>

   - Names:
      {'args': (),
       'context': <server.app.Server object at 0x7f4878033668>,
       'default': <object object at 0x7f4891c0a490>,
       'loop': {},
       'nothing': None,
       'options': {},
       'repeat': {},

Re: authentication and authorization

Souheil CHELFOUH — 2012-05-12T13:25:06

please, have a look at dolmen.app.authentication for examples too.
http://gitweb.dolmen-project.org/dolmen.app.authentication.git?a=tree;f=src/dolmen/app/authentication;h=1b9f0d9a65d101077a0f82182e387183799bbb93;hb=f24fd82b80c687115513bfebd86a671cf28e3f1b
or the pypi release http://pypi.python.org/pypi/dolmen.app.authentication/1.0b3

2012/5/12 Alex Leach <albl500< at >york.ac.uk>:

Re: authentication and authorization

Alex Leach — 2012-05-12T12:30:10

The same concepts in that documentation are relevant for the replacement 
modules. The imports are the main difference.

The PyPi pages for zope.authentication and zope.pluggableauth are good 
reference points.

Cheers,
Alex


On Saturday 12 May 2012 13:37:40 Anurag Sharma wrote:

Following link says information is outdated.
http://grok.zope.org/documentation/how-to/authentication-with-grok

Could somebody please point me to latest documentation on this ?

Thanks
Anurag



_______________________________________________
Grok-dev mailing list
Grok-dev< at >zope.org
https://mail.zope.org/mailman/listinfo/grok-dev

authentication and authorization

Anurag Sharma — 2012-05-12T08:07:40

Following link says information is outdated.
http://grok.zope.org/documentation/how-to/authentication-with-grok

Could somebody please point me to latest documentation on this ?

Thanks
Anurag
_______________________________________________
Grok-dev mailing list
Grok-dev< at >zope.org
https://mail.zope.org/mailman/listinfo/grok-dev

Re: megrok.rdb setup error

Jeffrey Peterson — 2012-05-10T18:05:26

You need to pin some libraries…

                       'megrok.rdb>=0.12',
                        'SQLAlchemy<=0.7',
                        'z3c.saconfig>=0.12',
                        'psycopg2>=2.4.2',

that setup works for me.

Jeffrey Peterson
bgpete3< at >gmail.com



On May 10, 2012, at 11:26 AM, Mauro Boschi wrote:

megrok.rdb setup error

Mauro Boschi — 2012-05-10T16:26:53

Hi to all,
I'm new with Grok!

As in http://grok.zope.org/documentation/how-to/orm-using-megrok.rdb-and-sqlalchemy

I have added megrok.rdb to setup.py

install_requires=['setuptools',
          ...
          # Add extra requirements here
          'megrok.rdb'
          ],

than run bin/buildout

restarting Grok I see this error:

# bin/paster serve --reload parts/etc/deploy.ini 
Starting subprocess with file monitor
Traceback (most recent call last):
File "bin/paster", line 20, in <module>
  paste.script.command.run()
File "/home/usytis/.buildout/eggs/PasteScript-1.7.5-py2.7.egg/paste/script/command.py", line 104, in run
  invoke(command, command_name, options, args[1:])
File "/home/usytis/.buildout/eggs/PasteScript-1.7.5-py2.7.egg/paste/script/command.py", line 143, in invoke
  exit_code = runner.run(args)
File "/home/usytis/.buildout/eggs/PasteScript-1.7.5-py2.7.egg/paste/script/command.py", line 238, in run
  result = self.command()
File "/home/usytis/.buildout/eggs/PasteScript-1.7.5-py2.7.egg/paste/scr

Re: PageTemplateFile('path/to/template.cpt') does notwork anymore

Jan-Wijbrand Kolman — 2012-05-07T11:31:25

Actually, it getting clearer now:

The ChameleonPageTemplate class (subclassing from GrokTemplate) is the
component that is attached to a view by way of the grok.template()
directive. It is the glue between grok's idea of calling an template
(including injecting extra namespaces etc.) and the concrete template
implementation's rendering.

The ChameleonPageTemplateFile class is new to grokcore.chameleon and,
since it subclasses ChameleonPageTemplate and thus GrokTemplate, tries
to behave like a glue too, making it easier to point to a path relative
to the caller module.

In other words, ChameleonPageTemplateFile seems to be useful after all,
and can be used instead of the template =
ChameleonPageTemplate(filename='asdasdas.cpt') pattern that used to work
on grok view components.

Still I think the ChameleonPageTemplate(File) classes in
grokcore.chameleon.components could have a shorter name. This would mean
the helper PageTemplate(File) helper classes in
grokcore.chalemeon.components should be renamed to ind

Re: PageTemplateFile('path/to/template.cpt') does not work anymore

Uli Fouquet — 2012-05-07T10:33:11

Hi JW,

On Mon, 07 May 2012 12:06:49 +0200 Jan-Wijbrand Kolman wrote:


Possibly, because the package grew out of megrok.chameleon which grew
out of another package that provided different pagetemplate engines
(Genshi, I think) and had to mark the differences in names. Clearly not
a valid reason any more.


I agree. The only reason to keep ChameleonPageTemplate would be to stay
backward-compatible. Don't know, however, whether it is used widely.


IMO that would be great :-)

Best regards,

Re: PageTemplateFile('path/to/template.cpt') does notwork anymore

Jan-Wijbrand Kolman — 2012-05-07T10:21:04

Furthermore, AFAICT, the ChameleonPageTemplate(File) components do not
have a __call__ anymore, where I think we're used to the pattern of
calling a template to have it rendered.

regards, jw

Re: PageTemplateFile('path/to/template.cpt') does notwork anymore

Jan-Wijbrand Kolman — 2012-05-07T10:06:49

I agree. To what extent is the PageTemplate(File) useful in itself?

In other words, why is there *both* a PageTemplate(File) *and* a
ChameleonPageTemplate(File).

I'd rather have just a PageTemplate(File) component. The package is
enough of a prefix to understand it is a chameleon-based template.

I could do that right now, as I'm fixing code in our applications
regarding this issue anyway...

regards, jw

Re: PageTemplateFile('path/to/template.cpt') does not work anymore

Uli Fouquet — 2012-05-07T09:51:54

Hi Christian and JW,

On Mon, 07 May 2012 11:45:43 +0200 Christian Klinger wrote:


Wouldn't it make sense to offer `PageTemplateFile` as a shortcut as well
(additionally)?

Best regards,