Hello ...
I've been trying to put together a relatively small ZMI based
product. When I go to distribute it, I click on the distribution tab,
select to allow redistribution and then create distribution archive, as
per the Zope Book. (And I've also tried this w/o allowing redistribution,
as well
--On 14. März 2006 14:12:53 -0500 Jeff Gentry [EMAIL PROTECTED]
wrote:
My question is what is the appropriate workaround here?
Fix the related code and replace the rotor with something similar (never
seen any code that uses enigma-style encryption for _serious_ reasons).
Is this
Fix the related code and replace the rotor with something similar (never
seen any code that uses enigma-style encryption for _serious_ reasons).
It is unclear to me why they were using that in the first place. I'm not
sure which you mean by 'the related code', you mean the internal Zope code
--On 14. März 2006 14:34:27 -0500 Jeff Gentry [EMAIL PROTECTED]
wrote:
Fix the related code and replace the rotor with something similar (never
seen any code that uses enigma-style encryption for _serious_ reasons).
It is unclear to me why they were using that in the first place. I'm not
Rotor was removed form python for a variety of reasons (see the mailing
list archives) but one of them was that it's a terrible way to do any sort
of encryption. There are numberous python extensions that do encryption
and decryption which could be incorporated into your product.
Zope does not use the rotor module and I don't think that it used the rotor
module in the past.
Extensions.py and Product.py both have 'import rotor' calls in Zope
2.7.3-0, from Zope-2.7.3-0/lib/python/App in my installation.
___
Zope maillist -
Rotor was removed form python for a variety of reasons (see the
mailing list archives) but one of them was that it's a terrible way to
do any sort of encryption. There are numberous python extensions that
do encryption and decryption which could be incorporated into your
product.
On Tue, 14 Mar 2006, Andreas Jung wrote:
Scary enough, but obviously this is dead code...otherwise Zope would
not work.
Okay ... I will try upgrading Zope (which I've been meaning to do
anyways) and see if that changes things.
Thanks
-J
___
Zope
On 3/14/06, Jeff Gentry [EMAIL PROTECTED] wrote:
Ah ... In the 2.7 version of the zope book I saw this: 'Zope 2.7 requires
Python 2.3.2 or later' and assumed that the 'or later' was inclusive of
later Python versions beyond 2.3.x.
Which would have been impossible since they didn't exist then.
, in index_html
* Module App.Product, line 202, in _distribution
ImportError: No module named rotor
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http
, in index_html
* Module App.Product, line 202, in _distribution
ImportError: No module named rotor
--
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists
Hi Dennis ...
both contain references. If you do not need cross Zope compatibility you
should be able to safely remove the calls to rotor objects.
I was just looking at that. By cross Zope compatibility do you mean
ability to give the tarball to other people for installation in their
12 matches
Mail list logo
