Re: [Zope-dev] List of packages in ZTK
Hi, On 05.07.2009, at 07:06, Lennart Regebro wrote: > 2009/7/5 Stephan Richter : >> To be honest, I am very disappointed by this list. It is totally >> meaningless >> to me since it does not represent any list with which I can build >> even a >> fairly simple application today. There is not a single z3c package >> in there. > > As I understand it, ZTK is not meant to build applications on. It's > meant to build application servers on. ZTK is supposed to be tha base > on which we build things like Grok, Plone, and yes, Zope 3. I'd like to mention repoze.bfg here. It takes a fairly small set of zope.* packages. What the ZTK is will be finally defined by the included packages. From a user's (developing with ZTK) perspective, I'd appreciate a small good documented well tested and stable set of tools to build web applications on regardless of which server or which db I want to use. Christian's list represents that very well, IMHO I'd kick a few packages I don't use at all. And where is zope.catalog? BTW z3c.* packages in the ZTK would baffle me a lot, OTOH renaming z3c packages just to fit into the ZTK seems a bit unorthodox. Very important are the tools and best practices surrounding the ZTK. Where do I start to get a state of the art but simple and inviting - from a developer's perspective - web application? Regards, Tobias ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A suggestion for changing exception handler when loading 'c' optimisations to make modules more friendly for GAE
On 03.07.2009, at 12:33, Jim Fulton wrote: > On Jul 3, 2009, at 6:25 AM, Tim Hoffman wrote: > >> Hi Jim >> >> That is what I am doing now, the problem I see though is when someone >> upates (via buildout etc a) module they need to remember to >> remove the recreated file before redeploying the app, >> unfortunately I >> am not sure I see a way reliable way of specifying that these files >> should be deleted in any automatic sense. At least an ignore in the >> app.yaml isn't feasible. > > > I'm sure there's a way to do it. It will just take some digging. > Maybe there's a way to tell setuptools not to do it or maybe there's > enough meta data laying around for buildout to undo it. For example, > the EGG-INFO/SOURCES.txt has a list of the original files in the > distribution, so it should be easy enough to figure out where these > extra bogus files are. Great idea to examine EGG-INFO/SOURCES.txt, Jim! I just added this to my recipe (http://pypi.python.org/pypi/rod.recipe.appengine) and got rid of the horrible monkey patch for imp.load_dynamic. Now it does exactly what Tim wants and excludes the optional c extension stuff (plus .pyo, and .pyc files) in a gae buildout. I'm planning to add an option for not deploying the additional packes as a zip archive if the gae file limit will not be exceeded. Cheers, Tobias ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A suggestion for changing exception handler when loading 'c' optimisations to make modules more friendly for GAE
On 03.07.2009, at 10:38, Chris Withers wrote:
> Tim Hoffman wrote:
>> gae/1.333250465889549129/zope/i18nmessageid/
>> _zope_i18nmessageid_message.py",
>> line 6, in __bootstrap__
>>imp.load_dynamic(__name__,__file__)
>> File "/base/python_dist/lib/python2.5/py_imp.py", line 116, in
>> load_dynamic
>>raise NotImplementedError('This function is not supported on App
>> Engine.')
>
> This actually feels like a bug in GAE to me... This should be an
> ImportError...
Sorry, I don't agree. We assume an imp.load_dynamic function from what
we read in the python documentation. But the implementation in GAE
does not provide the expected api. So the NotImplementedError seems
absolutely correct to me (see
http://www.python.org/doc/2.5.2/lib/module-exceptions.html#l2h-114)
.
Tobias
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A suggestion for changing exception handler when loading 'c' optimisations to make modules more friendly for GAE
Hi,
yes, I'd really appreciate such a modification. Then I could delete
the regarding code in my rod.recipe.appengine, which provides a dummy
implementation of imp.load_dynamic.
Tim, do you have a list of the concerning packages? I could help
making these changes. A good reason to file an application for commit
rights :-)
Regards
Tobias
On 03.07.2009, at 02:39, Tim Hoffman wrote:
> Hi all
>
> Can I make a suggestion that would make a couple of modules more gae
> friendly ;-)
> zope.interface and zope.i18nmessageid have 'c' optimisations which
> obviously don't work under app engine.
>
>
> When these modules are imported you get the following exception.
>
> gae/1.333250465889549129/zope/i18nmessageid/
> _zope_i18nmessageid_message.py",
> line 6, in __bootstrap__
>imp.load_dynamic(__name__,__file__)
> File "/base/python_dist/lib/python2.5/py_imp.py", line 116, in
> load_dynamic
>raise NotImplementedError('This function is not supported on App
> Engine.')
>
> Unfortunately the code (in this case in zope.i18nmessageid.Message)
> does the following which doesn't deal with the Exception
> raised by the app engine runtime.
>
>
> try:
>from _zope_i18nmessageid_message import Message
> except ImportError:
>pass
>
> To make it more "gae friendly" I think we should change these
> occurrences to
>
> try:
>from _zope_i18nmessageid_message import Message
> except ImportError, NotImplementedError:
>pass
>
> Regards
>
> Tim
> ___
> Zope-Dev maillist - Zope-Dev@zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.0a2 released
On 19.04.2009, at 10:52, Andreas Jung wrote: > I just released Zope 2.12.0a2: > > http://pypi.python.org/pypi/Zope2/2.12.0a2 doc/CHANGES.rst is missing in the source distribution on pypi: Getting distribution for 'Zope2'. error: doc/CHANGES.rst: No such file or directory An error occured when trying to install Zope2 2.12.0a2.Look above this message for any errors thatwere output by easy_install. While: Installing python. Getting distribution for 'Zope2'. Error: Couldn't install: Zope2 2.12.0a2 Regards, Tobias ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] several zope.* libs within gae (was ZCML implementations: where should they go)
Hi, Shane Hathaway wrote: > Hanno Schlichting wrote: >> Wichert Akkerman wrote: >>> I'ld rather not see a whole slew of extra packagse appear. I also wonder >>> how the extra number of packages and increasing size of sys.path >>> influence performance and restrictions on environments like GAE. >> >> For environments like GAE you don't want setuptools and its magic to be >> part of your application. This is were repackaging your entire app into >> one zipped egg or some other flat structure comes in handy. >> >> Setuptools and eggs are a distribution format from my point of view. >> They are certainly not the best way to deploy your applications. The >> growing sys.path is affecting performance to some degree in all >> deployment environments. > > Well, zc.buildout ought to be able to eliminate this concern for GAE > deployment. I haven't tried the recipe below, but it certainly seems > like the right idea. > > http://pypi.python.org/pypi/rod.recipe.appengine I released a new version today. It's a lot easier now to use several eggs within gae. This test thingy http://zpttest.appspot.com/ uses zope.interface and zope.pagetemplate plus their dependencies. I'm planning to release another sample project maybe during easter holidays. It's much more fun since you zope people cleaned up a lot of dependencies and unveiled zc.buildout. Thanks! Cheers, Tobias ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] trying out the buildout-based Zope 2.12...
On 28.03.2009, at 00:36, Chris Withers wrote: > There are currently two seperate issue with specifying zope2 as an > egg in a buildout.cfg. > > Which of these two issues is your solution designed to address? My versions.cfg resolved all version conflicts mentioned within this thread. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] trying out the buildout-based Zope 2.12...
On 28.03.2009, at 00:30, Chris Withers wrote: > Tobias Rodäbel wrote: >> Hi, >> >> had the same issue tonight. I'm using attached versions.cfg for now. >> That works quite well for me. > > Which issue is this supposed to help with? Using zc.buildout. This is my buildut.cfg: [buildout] parts = zope zopepy extends = versions.cfg unzip = true [zope] recipe = zc.recipe.egg:scripts eggs = Zope2 [zopepy] recipe = zc.recipe.egg eggs = Zope2 interpreter = zopepy scripts = zopepy ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] trying out the buildout-based Zope 2.12...
Hi, had the same issue tonight. I'm using attached versions.cfg for now. That works quite well for me. Cheers, Tobias [buildout] versions = versions [versions] Acquisition = 2.12.0a1 DateTime = 2.11.2 ExtensionClass = 2.11.1 Persistence = 2.11.1 tempstorage = 2.11.1 zLOG = 2.11.1 ClientForm = 0.2.10 RestrictedPython = 3.5.0 ZConfig = 2.6.1 ZODB3 = 3.9.0a11 docutils = 0.5 jquery.javascript = 1.0.0 jquery.layer = 1.0.0 lxml = 2.2beta4 mechanize = 0.1.11 pytz = 2009a setuptools = 0.6c9 transaction = 1.0a1 z3c.coverage = 1.1.2 z3c.csvvocabulary = 1.0.0 z3c.etestbrowser = 1.2.1 z3c.form = 1.9.0 z3c.formdemo = 1.5.3 z3c.formjs = 0.4.1 z3c.formjsdemo = 0.3.1 z3c.formui = 1.4.2 z3c.i18n = 0.1.1 z3c.layer.minimal = 1.0.1 z3c.layer.pagelet = 1.0.1 z3c.layer.ready2go = 0.5.1 z3c.layer.trusted = 1.0.1 z3c.macro = 1.1.0 z3c.macroviewlet = 1.0.0 z3c.menu.ready2go = 0.5.1 z3c.menu.simple = 0.5.1 z3c.optionstorage = 1.0.4 z3c.pagelet = 1.0.3 z3c.rml = 0.7.3 z3c.schema = 0.6.0 z3c.skin.pagelet = 1.0.2 z3c.template = 1.2.0 z3c.testing = 0.3.0 z3c.traverser = 0.2.4 z3c.viewtemplate = 0.4.0 z3c.zrtresource = 1.1.0 zc.buildout = 1.2.0 zc.catalog = 1.4.1 zc.datetimewidget = 0.6.1 zc.i18n = 0.6.1 zc.lockfile = 1.0 zc.recipe.egg = 1.1.0 zc.recipe.filestorage = 1.0.1 zc.recipe.testrunner = 1.1.0 zc.resourcelibrary = 1.0.2 zc.table = 0.7.0 zc.zope3recipes = 0.7.0 zdaemon = 2.0.2 zodbcode = 3.4.0 zope.annotation = 3.4.1 zope.app.apidoc = 3.6.1 zope.app.applicationcontrol = 3.4.3 zope.app.appsetup = 3.9.0 zope.app.authentication = 3.5.0a2 zope.app.basicskin = 3.4.0 zope.app.boston = 3.4.0 zope.app.broken = 3.5.0 zope.app.cache = 3.5.0 zope.app.catalog = 3.8.0 zope.app.component = 3.6.0 zope.app.container = 3.7.0 zope.app.content = 3.4.0 zope.app.dav = 3.5.0 zope.app.debug = 3.4.1 zope.app.debugskin = 3.4.0 zope.app.dependable = 3.4.0 zope.app.dtmlpage = 3.5.0 zope.app.error = 3.5.2 zope.app.exception = 3.4.2 zope.app.externaleditor = 3.5.0 zope.app.file = 3.5.0 zope.app.folder = 3.5.0 zope.app.form = 3.7.1 zope.app.ftp = 3.5.0 zope.app.generations = 3.4.2 zope.app.homefolder = 3.5.0 zope.app.http = 3.5.0 zope.app.i18n = 3.5.0 zope.app.i18nfile = 3.4.1 zope.app.interface = 3.4.0 zope.app.interpreter = 3.4.0 zope.app.intid = 3.7.0 zope.app.layers = 3.4.0 zope.app.locales = 3.5.1 zope.app.locking = 3.5.0 zope.app.module = 3.5.0 zope.app.onlinehelp = 3.5.0 zope.app.pagetemplate = 3.5.0 zope.app.pluggableauth = 3.4.0 zope.app.preference = 3.6.0 zope.app.preview = 3.4.0 zope.app.principalannotation = 3.5.0 zope.app.publication = 3.5.1 zope.app.publisher = 3.6.0 zope.app.pythonpage = 3.5.0 zope.app.renderer = 3.5.0 zope.app.rotterdam = 3.5.0 zope.app.schema = 3.5.0 zope.app.security = 3.6.0 zope.app.securitypolicy = 3.5.1 zope.app.server = 3.4.2 zope.app.session = 3.6.0 zope.app.skins = 3.4.0 zope.app.sqlscript = 3.5.0 zope.app.testing = 3.6.0 zope.app.traversing = 3.4.0 zope.app.tree = 3.6.0 zope.app.twisted = 3.4.2 zope.app.undo = 3.5.0 zope.app.wfmc = 0.1.2 zope.app.workflow = 3.5.0 zope.app.wsgi = 3.4.1 zope.app.xmlrpcintrospection = 3.5.0 zope.app.zapi = 3.4.0 zope.app.zcmlfiles = 3.5.2 zope.app.zopeappgenerations = 3.4.0 zope.app.zptpage = 3.5.0 zope.broken = 3.5.0 zope.browser = 0.5.0 zope.cachedescriptors = 3.4.1 zope.catalog = 3.8.0 zope.component = 3.5.1 zope.configuration = 3.4.1 zope.container = 3.7.1 zope.contentprovider = 3.4.0 zope.contenttype = 3.4.1 zope.copy = 3.5.0 zope.copypastemove = 3.5.1 zope.datetime = 3.4.0 zope.decorator = 3.4.0 zope.deferredimport = 3.5.0 zope.deprecation = 3.4.0 zope.documenttemplate = 3.4.2 zope.dottedname = 3.4.5 zope.dublincore = 3.4.2 zope.error = 3.6.0 zope.event = 3.4.0 zope.exceptions = 3.5.2 zope.file = 0.4.0 zope.filerepresentation = 3.5.0 zope.formlib = 3.5.2 zope.hookable = 3.4.0 zope.html = 1.1.0 zope.i18n = 3.6.0 zope.i18nmessageid = 3.4.3 zope.index = 3.5.1 zope.interface = 3.5.0 zope.intid = 3.7.0 zope.keyreference = 3.6.1 zope.lifecycleevent = 3.5.0 zope.location = 3.5.2 zope.mimetype = 0.3.0 zope.minmax = 1.1.0 zope.modulealias = 3.4.0 zope.pagetemplate = 3.4.1 zope.proxy = 3.5.0 zope.publisher = 3.5.5 zope.rdb = 3.5.0 zope.schema = 3.5.2 zope.security = 3.6.0 zope.securitypolicy = 3.5.0 zope.sendmail = 3.5.1 zope.sequencesort = 3.4.0 zope.server = 3.5.0 zope.session = 3.8.1 zope.site = 3.6.0 zope.size = 3.4.0 zope.structuredtext = 3.4.0 zope.tal = 3.5.0 zope.tales = 3.4.0 zope.testbrowser = 3.6.0a2 zope.testing = 3.7.1 zope.testrecorder = 0.3.0 zope.traversing = 3.5.2 zope.ucol = 1.0.2 zope.viewlet = 3.5.0 zope.wfmc = 3.4.0 zope.xmlpickle = 3.4.0 On 27.03.2009, at 21:47, Chris Withers wrote: > Hey All, > > I'm trying to get Zope 2.12 working with buildout, in the absence of > docs, I thought I'd try: > > [buildout] > parts = zopetest > > [zopetest] > recipe = zc.recipe.egg > interpreter = py > eggs = > zope2 > > ...and was rewarded with: > > Got zope.principalregistry 3.7.0. > While: > Installing zopetest. > Error: There is a version conflict. > We already have: zope.c
