Re: [Zope-dev] Buildout - including per-user site-packages dir.

2013-06-26 Thread Alex Leach

Hi again,

I got the same error with zpasswd, so had to repeat the process with that  
section of buildout.cfg, too... Thought I'd explain the specifics, while I  
remember...



On Tue, 25 Jun 2013 19:44:48 +0100, Alex Leach albl...@york.ac.uk wrote:


The buildout configuration that seemed to fix this, was to add 'recipe =  
zc.recipe.egg:scripts' to my package's section, and  
'allowed-eggs-from-site-packages = peak' to the `[buildout]` section.


I found the documentation on these options, unsurprisingly on the  
zc.recipe.egg and z3c.recipe.scripts PyPi pages.  
('allowed-eggs-from-site-packages = peak' is not what I thought it was  
yesterday, so please ignore it).


I don't think I had edited the zpasswd section before yesterday, so it  
should have been exactly as it was, when initially generated by  
`grokproject`:


[zpasswd]
recipe = z3c.recipe.scripts
eggs =
my_package
zope.password
entry-points =
zpasswd=zope.password.zpasswd:main


I'm not entirely sure why zpasswd has to import every module in  
my_package, but it seems to try. So the above configuration causes zpasswd  
to fail, when a required package is installed into the user's  
site-packages folder.


It's worth mentioning, if you're unfamiliar with the user's site-packages  
folder, that it is supported by every Python build system I've tried:  
distutils, distutils2, numpy.distutils and setuptools. The following  
setup.py command, which works on all of these build systems, installs a  
package into the user's site-packages folder:-


$ python setup.py install --user



With the documentation in front of my, I added these options to zpasswd,  
but none of these add the user's site-packages folder to the search path:-


include-site-packages = true
exec-sitecustomize = true
relative-paths = true
extra-paths = ${buildout:directory}/eggs
interpreter = python-console


However, changing the recipe does:

recipe = zc.recipe.egg:script

So, my conclusion is that it's a feature / limitation / regression in  
z3c.recipe.scripts. I only say regression, because on the  
z3c.recipe.scripts PyPi page, I've just read:-


The script recipe installs eggs into a buildout eggs directory, exactly  
like zc.recipe.egg [...].


Well, not exactly... This is one difference. I'll continue to use  
zc.recipe.egg, as that works as desired in this situation, but it feels  
like I'm downgrading, which is never fun...


Hope that clarifies things, anyway.

Kind regards,
Alex
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Security fixes from Plone hotfix ported to Zope ?

2013-06-26 Thread Gael Le Mignot
Hello,

Plone recently released a security hotfix with a dozen of patches in it
[1].

With a quick glance at the source code of those fixes, it seemed several
of them directly patch Zope, not Plone-related products.

Is  there any  plan to  make new  releases of  Zope 2.12  and  Zope 2.13
integrating the  patches that  are meaningful for  pure-Zope (non-Plone)
applications ?

[1] http://plone.org/products/plone/security/advisories/20130618-announcement

Regards,
-- 
Gaël Le Mignot - g...@pilotsystems.net
Pilot Systems - 82, rue de Pixérécourt - 75020 Paris
Tel : +33 1 44 53 05 55 - www.pilotsystems.net
Gérez vos contacts et vos newsletters : www.cockpit-mailing.com
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Security fixes from Plone hotfix ported to Zope ?

2013-06-26 Thread Matthew Wilkes

 Is  there any  plan to  make new  releases of  Zope 2.12  and  Zope 2.13
 integrating the  patches that  are meaningful for  pure-Zope (non-Plone)
 applications ?

Plone doesn't always use the latest version of Zope. These are backports.

Matt



smime.p7s
Description: S/MIME Cryptographic Signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Important! buildout 2.1.1 released, prepare for distribute 0.7 and buildout 2.2

2013-06-26 Thread Jim Fulton
Distribute/setuptools 0.7 bring some big changes.  These changes can't be
handled by buildout's normal automatic upgrade mechanism.  For this reason,
it's important to do one of the following if you're using buildout 2:

- Pin your distribute version to 0.7dev or to some other 0.6 version.

- Upgrade to buildout 2.1.1, which was just released.  This will prevent
  automatic upgrade to distribute 0.7 or buildout 2.2.  To upgrade,
  imply rerun your existing buildout scripts.

- Be prepared to re-bootstrap your buildouts with the the new buildout 2.2
  bootstrap script, which will be released soon after the release of
distribute 0.7.

-- 
Jim Fulton
http://www.linkedin.com/in/jimfulton
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )