Installing PloneGetPaid on Plone 4

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Used template plone3_buildout for Plone4 Alpha 4
   paster create -t plone3_buildout plone4a3

2. Created devel.cfg file as 
   [buildout]
   extends = buildout.cfg
   parts+=
       instance
       getpaid

    find-links +=
        http://dist.repoze.org/

    eggs += PIL
    [getpaid]
    recipe = getpaid.recipe.release

    addpackages=
        getpaid.paymentech
        getpaid.discount

    [instance]
    http-address = 9095
    eggs +=
        ${getpaid:eggs}

3. Ran buildout 
   ./bin/buildout -c devel.cfg -vvv

What is the expected output? What do you see instead?

Plone 4 instance with PloneGetPaid product.
Buildout out failing with the following error.

===================================================
ValueError: This extension should not be used with Python 2.6 or later
(already built in), and has not been tested with Python 2.3.4 or earlier.
An error occured when trying to install ssl-for-setuptools 1.10. Look above
this message for any errors that were output by easy_install.
While:
  Installing getpaid.
  Getting distribution for 'ssl-for-setuptools'.
Error: Couldn't install: ssl-for-setuptools 1.10
======================================================

What version of the product are you using? On what version of Plone? How
did you install it (tarball vs buildout vs...)?

getpaid.recipe.release 2.0
--------------------------
getpaid.core==0.7.5
Products.PloneGetPaid==0.8.8
getpaid.wizard==0.3
getpaid.nullpayment==0.3.1
five.intid==0.3.0
hurry.workflow==0.9.1-getpaid
simplejson==2.0.9
yoma.batching==0.2.1-getpaid
zc.resourcelibrary==0.5-getpaid
zc.table==0.5.1-getpaid
getpaid.paymentech==0.3
getpaid.discount==0.8.3
-----------------------------
Plone 4 Alpha 4
Used Buildout

Please provide any additional information below.

Attached Buildout output file

Original issue reported on code.google.com by john.dor...@gmail.com on 11 Feb 2010 at 4:07

Attachments:

• buildout-output.txt

[GoogleCodeExporter]

ValueError: This extension should not be used with Python 2.6 or later
(already built in)
and you are using 2.6
I would think that the first part of the error message is misleading and that 
the problem comes from the fact the extension is *already built*.
But the easy_install package should detect whether the native Python ssl module 
is present.
Check anyway if you can import ssl
python
>>> import ssl
>>> import _ssl2 
(to be safe remove __init__.pyc in the /ssl )

Original comment by danielle...@gmail.com on 16 Jul 2010 at 5:13