-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great ! ;)
J.
Fred L. Drake, Jr. wrote:
Log message for revision 38688:
move the Zope 3 trunk to Python 2.4
Changed:
U Zope3/trunk/Makefile
U Zope3/trunk/doc/DEBUG.txt
U Zope3/trunk/doc/INSTALL.txt
U
I've put the table formatter code (zc.table) and it's dependency the
resource library (zc.resourcelibrary) in the sandbox
svn://svn.zope.org/repos/main/Sandbox/zc. There is currently a proposal
to have the resource library code in Zope 3.2. We may make a similar
proposal for the table
On 9/30/05, Julien Anguenot [EMAIL PROTECTED] wrote:
Great ! ;)
Yeah, we've talked about it here and on IRC, but nobody did anything.
Then the tests failed because code got checked in that assumed 2.4, so
I figured it was time. :-)
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Zope
Fred Drake wrote:
On 9/30/05, Julien Anguenot [EMAIL PROTECTED] wrote:
Great ! ;)
Yeah, we've talked about it here and on IRC, but nobody did anything.
Then the tests failed because code got checked in that assumed 2.4, so
I figured it was time. :-)
My bad. Sorry about that. :)
I have
Martijn Faassen wrote:
Stephan Richter wrote:
On Friday 30 September 2005 04:58, Martijn Faassen wrote:
Such an event however does not appear to be fired when an
UnauthenticatedPrincipal gets fired. This makes adding groups to such a
principal not so easy.
I think you are right. Feel
Jim Fulton wrote:
Martijn Faassen wrote:
Stephan Richter wrote:
On Friday 30 September 2005 04:58, Martijn Faassen wrote:
Such an event however does not appear to be fired when an
UnauthenticatedPrincipal gets fired. This makes adding groups to such a
principal not so easy.
I think you
Martijn Faassen wrote:
...
Hm, you should be able to. This was badly broken a few months
ago and it was improved, but I never looked at what was done. I guess
I'd better do that.
Oh, then it might in fact be fixed now -- I am still working against the
beta here.
Anyway, still trying to
The last time we discussed the zcml:condition attribute for ZCML, we
decided that there should be a general registry of feature names that
should be checked when defining a new feature name. I think that I
suggested a page in the Zope 3 wiki as the registry.
Does anyone remember a registry ever
On Sep 30, 2005, at 2:25 PM, Fred Drake wrote:
The last time we discussed the zcml:condition attribute for ZCML, we
decided that there should be a general registry of feature names that
should be checked when defining a new feature name. I think that I
suggested a page in the Zope 3 wiki as
On 9/30/05, Gary Poster [EMAIL PROTECTED] wrote:
A generally accessible web page has some advantages--it is easy to
read, and usable even if you don't have the most recent version of
the software, for instance. It has some problems too.
The up-to-dateness of the registry is what I'm most
I've run into precisely the same thing using JSON-RPC, and I did
create a method to list all the other methods. However, I discovered
through use that this was not nearly as simple as I thought. Because a
single object can have multiple classes of JSON/XML methods, each one
with their own or
For the record, Gary capitulated via IM rather than by email to the
list. (I didn't even have to force his hand... wonder if he's feeling
ill?)
I'm send this email to:
1. Give Gary a chance to say Oh no I didn't! in public. :-)
2. Let people know the truth of the matter. :-)
3. Note that
On Friday 30 September 2005 12:55, Tarek Ziadé wrote:
I was wondering if there's actually any way to make xmlrpc introspection
in Z3,
so i can list methods from my rpc client.
(it seems not, looking at the code and the agile doc there
On Sep 30, 2005, at 6:29 PM, Fred Drake wrote:
For the record, Gary capitulated via IM rather than by email to the
list. (I didn't even have to force his hand... wonder if he's feeling
ill?)
I'm send this email to:
1. Give Gary a chance to say Oh no I didn't! in public. :-)
2. Let people
14 matches
Mail list logo
