Re: [Zope-dev] Failing Zope 2.8 / Python 2.3 tests on your box
It is a hand-compiled Python 2.3, not the one coming with the distro. I'll have to look into it, maybe ./configure missed something... Stefan On 20. Aug 2008, at 19:57, Tres Seaver wrote: Tests are blowing up on that box becaues the 'encodings' module has no attribute 'aliases': AFAICT, that doesn't happen on a standard build of Python: is there something weird about your setup? -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams ___ 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] zope.testbrowser.testing.Browser has undefined dependencies
Hi All, I'm just starting to play with zope.testbrowser's testing.Browser but I notice that is uses the following packages: transaction zope.app.testing zope.app.folder zope.app.component ...but zope.testbrowser doesn't declare any dependency on these. It probably should in some way, but I can see why it doesn't currently, give nthat there are likely lots of zope.testbrowser users who have to interested in zope.testbrowser.testing.Browser. Is this something that we can solve with: http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras-optional-features-with-their-own-dependencies If it is, I guess we would add an extra_requires to zoep.testbrowser's setup.py with the packages listed above? Would the following then work in a buildout: [test] recipe = zc.recipe.testrunner eggs = mypackage zope.testbrowser[testing.Browser] ? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] Zope Tests: 4 OK, 1 Unknown
Summary of messages to the zope-tests list. Period Wed Aug 20 11:00:00 2008 UTC to Thu Aug 21 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Aug 20 20:42:12 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010040.html Tests passed OK --- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 20 20:43:42 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010041.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 20 20:45:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010042.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 20 20:46:43 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010043.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 20 20:48:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010044.html ___ 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] How to put , in HTML attributes?
Am Mittwoch 20 August 2008 19:59:37 schrieb Christian Theune: On Wed, 2008-08-20 at 19:34 +0200, Hermann Himmelbauer wrote: Hi, I have a page template, that should have the characters and in the resulting HTML code, e.g.: input type=hidden, name=xyz, value=ABC / Zope3 makes a lt; / rt; out of the characters: input type=hidden, name=xyz, value=lt;ABCrt; Is there a way to get around this automatic conversion? I tried it via: input tal:attributes=value python:'ABC' / But this makes no difference. Any clues? Best Regards, Hermann P.S.: I know, this seems to make no sense, but the page is a template for another, foreign application, which needs this specific values as placeholders and which I can not adapt... My memory says and the HTML validator acknowledges it: this *is* broken. PT is designed to not do that. Here's how it *might* work: Take a view that generates the broken HTML snippet, like: class View: def code(self): return 'input value=broken/' And in your template do: div tal:replace=structure view/code/ I didn't test it and I'm not sure it works. It might, though. Yes, many thanks for that, this did the trick! Interestingly, something like this did not work:: def attrcode(self): return 'broken' input value= tal:attributes=value view/attrcode / Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ 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.testbrowser.testing.Browser has undefined dependencies
Chris Withers wrote: I'm just starting to play with zope.testbrowser's testing.Browser but I notice that is uses the following packages: transaction zope.app.testing zope.app.folder zope.app.component ...but zope.testbrowser doesn't declare any dependency on these. It does, using the extras mechanism you mention below. It probably should in some way, but I can see why it doesn't currently, give nthat there are likely lots of zope.testbrowser users who have to interested in zope.testbrowser.testing.Browser. Is this something that we can solve with: http://peak.telecommunity.com/DevCenter/setuptools#declaring-extras-optional-features-with-their-own-dependencies If it is, I guess we would add an extra_requires to zoep.testbrowser's setup.py with the packages listed above? If you had a look at zope.testbrowser/setup.py, you'd notice extras_require = dict( test = ['zope.interface', 'zope.schema', 'zope.app.component', 'zope.app.folder', 'zope.app.testing', 'zope.app.zcmlfiles', 'zope.app.securitypolicy', ], ), Would the following then work in a buildout: [test] recipe = zc.recipe.testrunner eggs = mypackage zope.testbrowser[testing.Browser] zope.testbrowser [test] ___ 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] How to put , in HTML attributes?
On Thu, 2008-08-21 at 13:30 +0200, Hermann Himmelbauer wrote: Yes, many thanks for that, this did the trick! Interestingly, something like this did not work:: def attrcode(self): return 'broken' input value= tal:attributes=value view/attrcode / Of course not. The quoting happens because of tal:attributes. Just moving the `python:...` statement into the view code doesn't make a structural difference. What makes it work is the `structure` prefix on the tal:replace part which doesn't touch the result of the evaluation. Christian -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ 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.app.form: Make no value always available?
Tres Seaver wrote: Thomas Lotze wrote: Oh well, it turns out that this doesn't really work well as the class in question is used as a base class by all the items edit widgets. The next-best approach we'd try would be a module-global flag that turns the old behaviour back on and must be set during application start-up for BBB. Would that be an acceptable solution? +0 if you release it with a new major release number (i.e., 3.6.0), and document clearly how to get the BBB behavior. If you need to release with a new minor number (i.e., 3.5.1), then the BBB behavior must be the default. I've done that. Dropdown widgets now display a no value item instead of selecting the first option, while select widgets and radio button groups don't need this since they can just leave everything unselected. Also, I've changed SourceSelectWidget so that it doesn't turn its `required` attribute off except in BBB mode. This is no longer useful for SourceDropdownWidgets and seems to have been a bug anyway for SourceSelectWidgets and SourceRadioWidgets. I'll release zope.app.form 3.6.0 tomorrow if nobody objects. If someone gives me access to the package on PyPI (username: tlotze), I can also upload it there. -- Thomas ___ 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.app.form: Make no value always available?
On Thu, Aug 21, 2008 at 8:45 AM, Thomas Lotze [EMAIL PROTECTED] wrote: If someone gives me access to the package on PyPI (username: tlotze), I can also upload it there. Done. -Fred -- Fred L. Drake, Jr. fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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] 404 on /manage frames with mod_rewrite
Nope, that rewrite rule only appeared to work because I had already authenticated on 8080, and the manage frames were pointing to that port. I followed Timo's advice and used the Rewrite Witch, and it worked (I'd used the rewrite witch last week and still couldn't get things to work - I must have had other broken elements last week, because now it's working). bernard On Thu, Aug 21, 2008 at 12:49 AM, Bernard Devlin [EMAIL PROTECTED] wrote: I worked it out. For the apache virtualhost config for 443 I changed the rewrite rule to this: RewriteRule ^/zp($|/.*) http://%{SERVER_NAME}:8080/VirtualHostRoot$1 [L,P] I probably should have included my rewrite rules in the earlier message. I'm sure my mistake would have been glaringly obvious. Bernard ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] 404 on /manage frames with mod_rewrite
Bernard Devlin wrote: I worked it out. For the apache virtualhost config for 443 I changed the rewrite rule to this: RewriteRule ^/zp($|/.*) http://%{SERVER_NAME}:8080/VirtualHostRoot$1 [L,P] I probably should have included my rewrite rules in the earlier message. I'm sure my mistake would have been glaringly obvious. Since 443 is missing in your rule its pretty obviously incorrect :-) The witch is outputting: RewriteRule ^/zp($|/.*) \ http://127.0.0.1:8080/VirtualHostBase/https/%{SERVER_NAME}:443/VirtualHostRoot/_vh_zp$1 [L,P] and I feel this should work :-) Regards Tino smime.p7s Description: S/MIME Cryptographic Signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need some help to get rid of an InvalidObjectReference exception
Yes this could be dangerous, but in my case these volatile attributes need not to be in the cache for a very long time, it's just a matter of 3 or 4 clicks in about half a dozen of minutes. But yeah, I'll really have to be careful about that, or to recreate them if they're gone (hence the setattr and getattr to make sure there's something in self._v_something and create one if there's not) Ok, I changed my mind again ^_^. Volatile attributes are shared across multiple sessions, which is not acceptable for my application. So here's what I cam up with : * 1 : Do not store references to a ZODBish object into a non ZODBish object * And 2 : just pass the context as a parameter to all the non-ZODBish methods that need it. I Tried to avoid this in the first place (hence storing it as an attribute), but putting them in the session broke everything. Cheers. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )