Re: [Zope-dev] Re: [Plone-developers] PAULA: bringing Zope 3's authentication to Plone and beyond
On Sat, Jul 12, 2008 at 02:04:32PM +0100, Martin Aspeli wrote: > I think it's worth displaying some sensitivity to the context of Google > Summer of Code here. I too worry that PAULA may throw the baby (PAS) out > with the bathwater. > > However, GSoC is an excellent incubator of R&D, and has secondary goals such > as bringing more people into the community and engaging with students so > that they become the future contributors of our projects. Shooing them down > in flames is not going to help. I see my work clearly in the R&D area, too, and I would like to take it as an opportunity to get further involved with Plone and Zope development. Sorry, if I am kicking off flames on the way there ;) > I wish that some of these discussions had been had in the open so that more > people could weigh in. However, most people who aren't used to the open > source way (and plenty who are, even) find it difficult to address a whole > community on a public mailing list and understand the nuances of the > responses. That very thing is part of the learning curve that GSoC seeks to > address. point taken > On balance, I think it's great that Florian is exploring new territory here. > PAULA may or may become a part of Zope and/or Plone in the future. It may be > that we use bits of it and let other bits evolve separately. It may be that > it dies, but at least then we have a clear idea about what PAU is and what > benefits it can bring. The notion of having a bridge component certainly > sounds sensible to me. > > So, please, let's not be too harsh until we've seen the final product and > given it a fair chance. thank you very much for supporting my idea florian PS: Did you intentionally not post to plone-developer's? As all of them are on zope-dev, too? pgpFu54UVRDDr.pgp Description: PGP signature ___ 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] Re: [Plone-developers] PAULA: bringing Zope 3's authentication to Plone and beyond
On Mon, Jul 14, 2008 at 09:50:25AM +0200, Hermann Himmelbauer wrote: > (..) > 1) No way to pass PAU-related information to form-code: In PAU, the > (..) As I using PAU within Plone and PlonePAS to handle the credential extraction and form stuff, I can't say anything about PAU's capabilities of doing that. However, I wrote it down and will eventually look into it. > 2) Lack of documentation: The entities "Principal, InternalPrincipal, > PrincipalInfo" are very confusing to a newbie, I still don't get the "big > picture". InternalPrincipal is a persistent object used to store the data of principals in a PrincipalFolder, PrincipalInfo is returned upon successfull authentication and handed to FoundPrincipalFactory, which extracts some information and returns Principal objects. > 3) Lack of plugins: No plugin for URL-rewriting, e.g. cookie-less browsers > (retrieving auth-information from URL) etc. I don't know about URL-rewriting, but you should be easily able to write your own credentials plugin to extract whatever you like from a request object. > I personally needed to write an authentication plugin for a SQLAlchemy based > RDB, and was confused a lot of how/why to create Principal / PrincipalInfo > objects: Should I create my own Principal/PrincipalInfo objects in order to > stuff information into them that my application needs? Most probably that could work. > How excactly should I cache user data so that a single browser request does > not lead to multiple RDB queries? And where in the big picture is the "User" > entity? (It's probably the InternalPrincipal object, I assume)... You don't need InternalPrincipal objects, they are specific to PrincipalFolder, IMHO. I think you need: - custom authenticator plugin, that authenticates against RDB and has a dictionary as cache: key = login, value = password; - custom foundprinciplefactory, that generates Principal objects from RDB data, again using a simple key=login,value=Principal dictionary as cache; - eventually a custom credentials plugin, that for your point 3. > (..) > So I would very, very much suggest to dig into PAU first and fix those > shortcomings before porting it to Plone/Zope2. Exactly what I am doing :) Thank you very much for your feedback. florian pgpanEfbeSGFw.pgp Description: PGP signature ___ 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] how many checkin lists?!
Hi All, Just me, or is it excessive that we have: http://mail.zope.org/pipermail/zope3-checkins/ http://mail.zope.org/pipermail/zope-checkins/ http://mail.zope.org/pipermail/checkins/ ...and maybe more I don't know about? Surely one list would suffice? 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] Re: No events in zope.annotation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: > On Tuesday 15 July 2008, Tres Seaver wrote: >>> Comments? Silence is consent as always. >> I must be missing something: why would you catalog annoations as though >> they were separate content objects? The entire point of annotations was >> to be "meta" about some other content object. > > Right, but annotations are still content in their own right. Not by design, anyway, although you might be using them that way. They aren't traversable (by default), nor are they "located". Why not just fire the event in whatever application code you are using to stash the annoation? However this works out, any events fired should not be of the same type as events that "normal" content emits. > And we fire > events that are specific to annotations all the time, for example in workflow > instances. The events are not *about* the annotation: they are about the state transition. In fact, one way to implement workflow history would be to create and add the annotation *in the subscriber* to the state transition event. >> -1 to any change which encourages abusing them to look like "items" in >> the target object as a container. > > It does not have to be like a container. It could be: > > IAnnotationAdded(object, key, annotation) > > Right now, I have no hook that allows me to do something else after I added a > new annotation for an object. How likely is it that such a hook is generically useful (compared to just publishing the event, or doing the work, in the code which is adding your custom annotations?) It sounds as though you are creating a framework for which such events are meaningful, but I would be extremely surprised if that framework expected "foreign code to add its annotations. > Events are designed to allow expanding the > system without touching the original code. And that's what I want to do. We > do it in all the other packages of Zope 3. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIfSx3+gerLs4ltQ4RAkYkAKDMNcAcPF9uorwX3rXFC8MlonyCcwCfUyri f3nMn9kLcdQS1l6XQBC0vms= =vFd6 -END PGP SIGNATURE- ___ 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 )
AW: [Zope-dev] Re: No events in zope.annotation
Hi > Betreff: Re: [Zope-dev] Re: No events in zope.annotation > > On Tue, Jul 15, 2008 at 2:28 PM, Stephan Richter > <[EMAIL PROTECTED]> wrote: > > Right, but annotations are still content in their own right. And we > > fire events that are specific to annotations all the time, > for example > > in workflow instances. > > I agree that it's reasonable to fire some event when an > annotation is added; I don't think it should provide to > zope.app.container.interfaces.IObjectAddedEvent, because that > is about the containment hierarchy. > > It *might* be reasonable for the factory machinery to trigger > an ObjectCreatedEvent for the new object; I've little opinion on that. > > It *is* reasonable for the IAnnotations adapters to generate > a specific annotation-added event when an annotation is > added. There are probably a whole bunch of other hooks > needed to get all that working with catalogs, and I'd hate to > see more magical subscribers added to make that happen; the > existing subscribers that deal with catalogs and int id > assignments are already excessively implicit, and often need > to be suppressed for large applications. I agree on that. I recommend everybody to use it's own custom event handling in complexer applications. And avoid every event which is offered by Zope3 as default. The speedup can be hugh if you select carfully what really happens! Regards Roger Ineichen > -Fred > > -- > Fred L. Drake, Jr. "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 ) > ___ 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] Re: No events in zope.annotation
On Tuesday 15 July 2008, Fred Drake wrote: > It *is* reasonable for the IAnnotations adapters to generate a > specific annotation-added event when an annotation is added. There > are probably a whole bunch of other hooks needed to get all that > working with catalogs, and I'd hate to see more magical subscribers > added to make that happen; the existing subscribers that deal with > catalogs and int id assignments are already excessively implicit, and > often need to be suppressed for large applications. No, the catalog hookup would be app specific. I am not proposing to add more code other than the event itself. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ 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] Re: No events in zope.annotation
On Tue, Jul 15, 2008 at 2:28 PM, Stephan Richter <[EMAIL PROTECTED]> wrote: > Right, but annotations are still content in their own right. And we fire > events that are specific to annotations all the time, for example in workflow > instances. I agree that it's reasonable to fire some event when an annotation is added; I don't think it should provide to zope.app.container.interfaces.IObjectAddedEvent, because that is about the containment hierarchy. It *might* be reasonable for the factory machinery to trigger an ObjectCreatedEvent for the new object; I've little opinion on that. It *is* reasonable for the IAnnotations adapters to generate a specific annotation-added event when an annotation is added. There are probably a whole bunch of other hooks needed to get all that working with catalogs, and I'd hate to see more magical subscribers added to make that happen; the existing subscribers that deal with catalogs and int id assignments are already excessively implicit, and often need to be suppressed for large applications. -Fred -- Fred L. Drake, Jr. "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-dev] Re: No events in zope.annotation
On Tuesday 15 July 2008, Tres Seaver wrote: > > Comments? Silence is consent as always. > > I must be missing something: why would you catalog annoations as though > they were separate content objects? The entire point of annotations was > to be "meta" about some other content object. Right, but annotations are still content in their own right. And we fire events that are specific to annotations all the time, for example in workflow instances. > -1 to any change which encourages abusing them to look like "items" in > the target object as a container. It does not have to be like a container. It could be: IAnnotationAdded(object, key, annotation) Right now, I have no hook that allows me to do something else after I added a new annotation for an object. Events are designed to allow expanding the system without touching the original code. And that's what I want to do. We do it in all the other packages of Zope 3. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ 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] Re: No events in zope.annotation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: > Hi everyone, > > I just tried to create a catalog for an annotation and noticed that it does > not get filled. Digging around in the zope.annotation package, I noticed that > the zope.annotation package does not send out any object events. This > sucks. ;-) > > Thus I propose: > > - Add ObjectCreatedEvent event notification to zope.annotation factory call. > > - Add ObjectAddedEvent to attribute annotations __setitem__. > > - Add ObjectRemovedEvent to attribute annotations __delitem__. > > This would mimic the behavior of the other containers. the downside is that > we > have 2 new dependencies, zope.event and zope.lifecycleevent, both of which > are acceptable in my opinion. > > Comments? Silence is consent as always. I must be missing something: why would you catalog annoations as though they were separate content objects? The entire point of annotations was to be "meta" about some other content object. - -1 to any change which encourages abusing them to look like "items" in the target object as a container. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIfN90+gerLs4ltQ4RAiusAJ0dSzChnQme4ncb79I52wyVY7nkDQCgizOK rmzBPUOJtZgQiTmpswogzDc= =Acg2 -END PGP SIGNATURE- ___ 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] No events in zope.annotation
On Tuesday 15 July 2008, Fred Drake wrote: > On Tue, Jul 15, 2008 at 12:30 PM, Stephan Richter > > <[EMAIL PROTECTED]> wrote: > > Thus I propose: > > > > - Add ObjectCreatedEvent event notification to zope.annotation factory > > call. > > By this, I presume you mean the stuff in zope.annotation.factory; is that > right? Yes. > In our group, we've decided to avoid that machinery. It causes the > separation between data and code to become excessively blurred. I'd > love to see that factory machinery become unused. I definitely > consider it unusable. I use it all the time. I think it makes development a lot easier. In fact, this came out of the ST project, where we constantly repeated this sort of code. BTW, I really do not understand how it blurs the separation of code and data. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ 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] No events in zope.annotation
On Tue, Jul 15, 2008 at 12:30 PM, Stephan Richter <[EMAIL PROTECTED]> wrote: > Thus I propose: > > - Add ObjectCreatedEvent event notification to zope.annotation factory call. By this, I presume you mean the stuff in zope.annotation.factory; is that right? In our group, we've decided to avoid that machinery. It causes the separation between data and code to become excessively blurred. I'd love to see that factory machinery become unused. I definitely consider it unusable. -Fred -- Fred L. Drake, Jr. "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 )
[Zope-dev] No events in zope.annotation
Hi everyone, I just tried to create a catalog for an annotation and noticed that it does not get filled. Digging around in the zope.annotation package, I noticed that the zope.annotation package does not send out any object events. This sucks. ;-) Thus I propose: - Add ObjectCreatedEvent event notification to zope.annotation factory call. - Add ObjectAddedEvent to attribute annotations __setitem__. - Add ObjectRemovedEvent to attribute annotations __delitem__. This would mimic the behavior of the other containers. the downside is that we have 2 new dependencies, zope.event and zope.lifecycleevent, both of which are acceptable in my opinion. Comments? Silence is consent as always. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ 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: 5 OK
Summary of messages to the zope-tests list. Period Mon Jul 14 11:00:00 2008 UTC to Tue Jul 15 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Mon Jul 14 21:01:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009855.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 14 21:03:01 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009856.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 14 21:04:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009857.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 14 21:06:01 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009858.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 14 21:07:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009859.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 )
[Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Martin Aspeli wrote: Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. I would expect the above to work as *everything* is built using mingw32. No, it is not. It uses the official Python Windows installer, being built with some M$ C compiler, adds Python Win32 add-ons and PIL using the Windows binary installers and only advertises using MinGW for compiling all of Zope itself. I haven't seen anyone running into any problems with this approach for years now. From my understanding starting with 2.4 Python includes certain files to make this approach work as smooth as possible. In the old days you had to extract some header files out of the dll's, which are now included in the binary installers by default. Hanno ___ 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] Re: Zope 3 on Python 2.5, Zope 3 releases
Martin Aspeli wrote: Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. I'm not sure if you're deliberately missing my point here ;-) I would expect the above to work as *everything* is built using mingw32. I'm asking what happens if python is built using whatever the official python releases are built with but the c extensions we provide are built with mingw32? 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 )
Re: [Zope-dev] RestrictedPython
Martijn Faassen wrote: It's good to know we have some eyes on this particular topic. Thanks Stephan! I talked to Chris about this at the EuroPython conference after Chris started offering free beer and even bottles of champagne for people who could point out flaws (beer) and submit fixes with tests (champagne). Unfortunately for everybody now suddenly hopeful this offer has since expired (nobody took him up on it during EuroPython :). ...and unfortunately, from chatting with some of the PyPy guys, I set an unfair challenge too: you couldn't even iterate over [1,2,3] in the environment I set in the challenge. The problem is that the module is poorly documented and tested. The docs on PyPI cover one specific use path and that's not even the one used by Zope 2's PythonScripts. The PyPy guys are also of the opinion that the AST hacking is completely the wrong way to go about creating a restricted python environment. They gave an interesting lightning talk where they showed a truly restricted environment where you could still do all the "normal" python things except the provider of the restricted environment had to actively implement hooks for any c-level stuff to be do-able. They could also control the maximum amount of memory the restricted environment could consume, which is something we sorely miss in RestrictedPython. (the code they were using is up here: http://codespeak.net/pypy/dist/pypy/doc/sandbox.html ...and in particular: http://codespeak.net/svn/pypy/dist/pypy/translator/sandbox/sandlib.py) I think the "right" thing to do here is engage with the PyPy guys on their mailing list: http://codespeak.net/mailman/listinfo/pypy-dev ...and work with their guidance to re-implement RestrictedPython in a way that doesn't use AST hacks. I suspect we'll likely end up with a much faster and more robust environment. It would be great if, on the way, RestrictedPython was fully documented and tested... 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] Re: Zope 3 on Python 2.5, Zope 3 releases
Chris Withers wrote: Stephan Richter wrote: On Saturday 12 July 2008, Martijn Faassen wrote: Chris wants to do them, he just wants some documentation on how to get started, I suspect. I use Philipp's blog entry from ages ago: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_07_26_cheap-binary-windows You see, I've always worried about using mingw32. I was under the impression that you really wanted to have all the C bits compiled with the same compiler, and I know that the official Python 2.5 releases aren't compiled with mingw32... Can someone with definitive knowledge let us know if there can be problems when some C-extensions are compiled with mingw32 and others (including python itself!) are compiled with the appropriate microsoft compiler? Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on Windows as per http://plone.org/documentation/tutorial/buildout has not given us any problems after a few months of using it. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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 3 on Python 2.5, Zope 3 releases
Stephan Richter wrote: On Saturday 12 July 2008, Martijn Faassen wrote: Chris wants to do them, he just wants some documentation on how to get started, I suspect. I use Philipp's blog entry from ages ago: http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_07_26_cheap-binary-windows You see, I've always worried about using mingw32. I was under the impression that you really wanted to have all the C bits compiled with the same compiler, and I know that the official Python 2.5 releases aren't compiled with mingw32... Can someone with definitive knowledge let us know if there can be problems when some C-extensions are compiled with mingw32 and others (including python itself!) are compiled with the appropriate microsoft compiler? You also need to get access to the packages on PyPI, which I am happy to give to anyone I know. Great, please give me access to any packages you can... 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 )
