Dennis J Harrison Jr wrote:
> Actually, looking over that other traceback.  The error is not the 
> same.  Here is the traceback I am seeing.
> 
> http://paste.plone.org/22858
> 
> This is on a brand new checkout with Products.remember Products.membrane 
> from trunk in as dev eggs.  This site has nothing but membrane / 
> remember installed.

i've done a bit of research... is it possible that you have a dependency 
problem, where you have a newer version of zope.interface installed in your 
environment, which is overriding the zope.interface implementation that would 
be the default in your Plone build?

the ArchetypeTool has a 'listPortalTypesWithInterfaces' method, which accepts 
a sequence of interfaces and calls 'iface.isImplementedByInstancesOf(klass)' 
on each one, for each type.  the 'isImplementedByInstancesOf' method is 
deprecated; the preferred spelling would be 'iface.implementedBy(klass)'.

this deprecated method was removed from zope.interface in r70211:

http://svn.zope.org/Zope3/trunk/src/zope/interface/interface.py?rev=70211&r1=70082&r2=70211

it seems that you've somehow ended up w/ an implementation of zope.interface 
that is newer than r70211.  it seems unlikely to me that Plone is shipping 
with a version of zope.interface that is newer than this... if it is, then 
this should be considered an Archetypes bug, b/c AT clearly shouldn't be 
calling methods that are no longer available.

more likely is that some other package that you have installed declared 
zope.interface as a dependency, and a more recent version of zope.interface 
was installed which is now conflicting w/ the one that your Plone version 
installed.  it's possible that this has happened at the system level.  when 
you created your virtualenv, did you use the --no-site-packages option?

-r


> On Tue, Jul 29, 2008 at 1:21 PM, Dennis J Harrison Jr 
> <dennis@... <mailto:dennis@...>> wrote:
> 
>     I had recently made a checkout of my development buildout on a local
>     dev server to create a new site.
> 
>     virtualenv it up, run the buildout, get new version of membrane to
>     handle those security issues in the gs that david bain brought up. 
>     And everything from that point on was roses.  Do further
>     development.  Write a bunch of extensions to getpaid to handle
>     paypal ipn and taxes, tax lookup, etc... and then merge the changes
>     to a staging buildout, I just install all the products looking for
>     an obvious error in fg, don't see any and we move on to checking all
>     that in to production.  So I get everything back up on production
>     and lo-and-behold! I can't get to remember. 
> 
>     Now, the confusing part comes in here ... I go back to my local
>     checkout of dev (5 days ago) and everything works.  I make sure svn
>     is the same.  It is.  So I checkout another copy of the dev
>     buildout, and I can't make the new checkout work either.  I feel
>     like I am going crazy :)
> 
>     However, I found someone else with the same problem... and he has a
>     resolution.  But I just don't know that I should have to worry about
>     this, as everything 'was' working and that was with plone 3.1.3 /
>     membrane 1.1b4 / remember 1.1svn
> 
>     http://sharbas.blogspot.com/2008/03/membraneremember-in-plone3.html
> 
>     Did anything funky happen recently I might not be aware of?  Did I
>     sleep through fixing this problem once already.  Am I checking out
>     the wrong versions?
> 
>     help?
> 
>     -- 
>     Dennis J Harrison Jr
>     Solutions Architect - Absolute IT
>     RHCE, CCNE, CEH
>     dennis@... <mailto:dennis@...>
>     B: 504.754.1343
>     C: 985.590.0420