[Grok-dev] megrok.form.fields import BlobFile : Error: Couldn't find a distribution for 'z3c.javascript'
DIVINE, PAUL (PAUL)
paul.divine at alcatel-lucent.com
Fri Apr 8 10:26:45 EDT 2011
Hi grokkers,
from megrok.form.fields import BlobFile : Error: Couldn't find a distribution for 'z3c.javascript'
I just installed Debian linux last version squeeze on a machine.
#Linux AlSys1 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 GNU/Linux
then I installed the last version Grok 1.4 without any problem.
Then I modified the app.py. In the app.py I have the following line
from megrok.form.fields import BlobFile
then the BloBfile was used in a interface like in the great book of Carlos de la guardia.
file_name = BlobFile(title=u'The expected file name' , required=False)
So the buildout.cfg and setup.py are consequently updated
I found that z3c.javascript : The project was moved because of licensing issues on svn.zope.org.
http://svn.zope.org/z3c.javascript/
Do you know a workaround or a solution?
Thanks in advance for your help.
Paul
Details are given in the following lines.
npotools# cat setup.py
from setuptools import setup, find_packages
version = '0.0'
setup(name='npotools',
version=version,
description="",
long_description="""\
""",
# Get strings from http://www.python.org/pypi?%3Aaction=list_classifiers
classifiers=[],
keywords="",
author="",
author_email="",
url="",
license="",
package_dir={'': 'src'},
packages=find_packages('src'),
include_package_data=True,
zip_safe=False,
install_requires=['setuptools',
'grok',
'grokui.admin',
'fanstatic',
'zope.fanstatic',
'grokcore.startup',
# Add extra requirements here
'megrok.form', <----------
],
entry_points={
'fanstatic.libraries': [
'npotools = npotools.resource:library',
]
})
npotools# cat buildout.cfg
[buildout]
extends = http://grok.zope.org/releaseinfo/1.4/versions.cfg
extends-cache = extends-cache
include-site-packages = false
develop = .
unzip = true
parts =
app
daemon
paster_ini_debug
paster_ini_deploy
i18n
mkdirs
site_zcml
test
zope_conf_debug
zope_conf_deploy
zpasswd
interactive_debugger
# For backward compatibility, telling buildout not to throw away
# the data and log subdirectories from the parts directory.
data
log
newest = false
versions = versions
# eggs will be installed in the default buildout location
# (see .buildout/default.cfg in your home directory)
# unless you specify an eggs-directory option here.
extensions += buildout.dumppickedversions
[versions]
# Override versions here.
megrok.form = 0.2.5 <---------------
zc.resourcelibrary = 1.0.1 <---------------
[app]
recipe = z3c.recipe.scripts
eggs = npotools
z3c.evalexception>=2.0
Paste
PasteScript
PasteDeploy
interpreter = python-console
[daemon]
recipe = collective.recipe.scriptgen
cmd = ${buildout:bin-directory}/paster
arguments = serve ${buildout:parts-directory}/etc/deploy.ini
--daemon --pid-file=${buildout:directory}/var/daemon.pid
--log-file=${buildout:directory}/log/daemon.log
[paster_ini_debug]
recipe = collective.recipe.template
input = etc/debug.ini.in
output = ${buildout:parts-directory}/etc/debug.ini
host = xx.xx.xx.xx
port = xxxx
[paster_ini_deploy]
recipe = collective.recipe.template
input = etc/deploy.ini.in
output = ${buildout:parts-directory}/etc/deploy.ini
host = xx.xx.xx.xx
port = xxxx
# this section named so that the i18n scripts are called bin/i18n...
[i18n]
recipe = z3c.recipe.i18n:i18n
packages = npotools
eggs = npotools
domain = npotools
output = src/npotools/locales
zcml =
[mkdirs]
recipe = z3c.recipe.mkdir
paths =
${zope_conf:filestorage}
${zope_conf:logfiles}
${zope_conf:blobstorage}
[site_zcml]
recipe = collective.recipe.template
input = etc/site.zcml.in
output = ${buildout:parts-directory}/etc/site.zcml
[test]
recipe = zc.recipe.testrunner
eggs = npotools
defaults = ['-v']
[zope_conf]
input = etc/zope.conf.in
filestorage = ${buildout:directory}/var/filestorage
blobstorage = ${buildout:directory}/var/blobstorage
logfiles = ${buildout:directory}/var/log
# 'extra' is copied verbatim. Use it for product config sections and so.
extra =
[zope_conf_debug]
<= zope_conf
recipe = collective.recipe.template
output = ${buildout:parts-directory}/etc/zope.debug.conf
devmode = on
[zope_conf_deploy]
<= zope_conf
recipe = collective.recipe.template
output = ${buildout:parts-directory}/etc/zope.deploy.conf
devmode = off
# This section is named so that the zpasswd utility is
# called `zpasswd`
[zpasswd]
recipe = z3c.recipe.scripts
eggs =
npotools
zope.password
entry-points =
zpasswd=zope.password.zpasswd:main
[interactive_debugger]
recipe = z3c.recipe.scripts
eggs = npotools
entry-points =
interactive_debugger=grokcore.startup.startup:interactive_debug_prompt
arguments = zope_conf="${zope_conf_debug:output}"
# The [data] and [log] parts are still in here to instruct buildout to not
# unintentionally throw away the parts/data and parts/log subdirectories
# that contain the Data.fs and the log files. These files should be
# copied to the new locations. See the upgrade notes for more information.
[data]
recipe = zc.recipe.filestorage
[log]
recipe = zc.recipe.filestorage
npotools#
(npogrok10)npotools# bin/buildout
/root/.buildout/eggs/zc.buildout-1.5.2-py2.6.egg/zc/buildout/buildout.py:303:
UserWarning: Buildout has been asked to exclude or limit site-packages so
that builds can be repeatable when using a system Python. However, the
chosen Python executable has a broken implementation of -S
(see https://bugs.launchpad.net/virtualenv/+bug/572545 for an example
problem) and this breaks buildout's ability to isolate site-packages.
If the executable already has a clean site-packages (e.g., using
virtualenv's ``--no-site-packages`` option) you may be getting equivalent
repeatability. To silence this warning, use the -s argument to the
buildout script. Alternatively, use a Python executable with a
working -S (such as a standard Python binary).
warnings.warn(zc.buildout.easy_install.BROKEN_DASH_S_WARNING)
Develop: '/npogrok/npogrok10/npotools/.'
Unused options for buildout: 'sources'.
Installing app.
/root/.buildout/eggs/zc.buildout-1.5.2-py2.6.egg/zc/buildout/easy_install.py:372:
UserWarning: Buildout has been asked to exclude or limit site-packages so
that builds can be repeatable when using a system Python. However, the
chosen Python executable has a broken implementation of -S
(see https://bugs.launchpad.net/virtualenv/+bug/572545 for an example
problem) and this breaks buildout's ability to isolate site-packages.
If the executable already has a clean site-packages (e.g., using
virtualenv's ``--no-site-packages`` option) you may be getting equivalent
repeatability. To silence this warning, use the -s argument to the
buildout script. Alternatively, use a Python executable with a
working -S (such as a standard Python binary).
warnings.warn(BROKEN_DASH_S_WARNING)
Couldn't find index page for 'z3c.javascript' (maybe misspelled?)
Getting distribution for 'z3c.javascript'.
While:
Installing app.
Getting distribution for 'z3c.javascript'.
Error: Couldn't find a distribution for 'z3c.javascript'. <--------------
*************** PICKED VERSIONS ****************
[versions]
#Required by:
#z3c.widget 0.1.6
z3c.schema = 0.7.2
#Required by:
#zc.datetimewidget 0.5.2
zc.i18n = 0.7.0
#Required by:
#z3c.widget 0.1.6
zope.app.cache = 3.7.0
#Required by:
#z3c.blobfile 0.1.0
#z3c.widget 0.1.6
zope.app.file = 3.6.1
*************** /PICKED VERSIONS ***************
z3c.javascript : The project was moved because of licensing issues on svn.zope.org.
More information about the Grok-dev
mailing list