[Checkins] SVN: grokcore.formlib/trunk/ Moved to GitHub.
Stephen Richter
cvs-admin at zope.org
Fri Mar 1 15:41:31 UTC 2013
Log message for revision 129947:
Moved to GitHub.
Changed:
D grokcore.formlib/trunk/CHANGES.txt
D grokcore.formlib/trunk/COPYRIGHT.txt
D grokcore.formlib/trunk/CREDITS.txt
D grokcore.formlib/trunk/INSTALL.txt
D grokcore.formlib/trunk/LICENSE.txt
A grokcore.formlib/trunk/MOVED_TO_GITHUB
D grokcore.formlib/trunk/README.txt
D grokcore.formlib/trunk/bootstrap.py
D grokcore.formlib/trunk/buildout.cfg
D grokcore.formlib/trunk/setup.py
D grokcore.formlib/trunk/src/
-=-
Deleted: grokcore.formlib/trunk/CHANGES.txt
===================================================================
--- grokcore.formlib/trunk/CHANGES.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/CHANGES.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,85 +0,0 @@
-Changes
-=======
-
-1.10 (unreleased)
------------------
-
-- Nothing changed yet.
-
-
-1.9 (2012-05-01)
-----------------
-
-- Nothing changed yet.
-
-
-1.8 (2010-11-03)
-----------------
-
-- The context directive now has its own default computation.
-
-1.7 (2010-11-01)
-----------------
-
-- Update version requirements for martian, grokcore.component, grokcore.security
- grokcore.view.
-
-1.6 (2010-10-18)
-----------------
-
-- Made package comply to zope.org repository policy.
-
-- Update functional tests to zope.app.wsgi Browser instead of zope.app.testing
- one.
-
-- Don't depend anymore on zope.app.zcmlfiles for tests.
-
-1.5 (2009-12-13)
-----------------
-
-- Use zope.container instead of zope.app.container (in tests and in the
- configure.zcml).
-
-- Fixed up missing dependencies and splitted regular and test dependencies.
-
-
-1.4 (2009-09-17)
-----------------
-
-* Reflect the changes in ``grokcore.view`` 1.12 where ``View`` and ``CodeView``
- become a single ``View`` again. This reverts to the View situation of
- ``grokcore.formlib`` 1.1.
-
-1.3 (2009-09-16)
-----------------
-
-* Remove the reference to the grok.View permission that is no longer in
- grokcore.security 1.2
-
-* Use 1.0b1 versions.cfg in Grok's release info instead of a local
- copy; a local copy for all grokcore packages is just too hard to
- maintain.
-
-
-1.2 (2009-07-20)
-----------------
-
-* Adapted tests to the grokcore.view split of View and CodeView.
-
-* Fixed forms to use self.template.render() directly instead of using a
- removed private method from grokcore.view.
-
-* Add grok.View permissions for functional tests.
-
-1.1 (2009-01-07)
-----------------
-
-* Have GrokForm define an empty actions attribute by default, in order
- for "action-less" forms to work easily.
-
-1.0 (2008-09-25)
-----------------
-
-* Created ``grokcore.formlib`` in July 2008 by factoring
- ``zope.formlib``-based components, grokkers and directives out of
- Grok.
Deleted: grokcore.formlib/trunk/COPYRIGHT.txt
===================================================================
--- grokcore.formlib/trunk/COPYRIGHT.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/COPYRIGHT.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1 +0,0 @@
-Zope Foundation and Contributors
\ No newline at end of file
Deleted: grokcore.formlib/trunk/CREDITS.txt
===================================================================
--- grokcore.formlib/trunk/CREDITS.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/CREDITS.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,6 +0,0 @@
-CREDITS
-=======
-
-This package was extracted from the Grok web framework.
-
-For credits, see the CREDITS file in the main ``grok`` project itself.
Deleted: grokcore.formlib/trunk/INSTALL.txt
===================================================================
--- grokcore.formlib/trunk/INSTALL.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/INSTALL.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,63 +0,0 @@
-Preparing for grok development
-------------------------------
-
-The Grok development sandbox is set up via `zc.buildout`_
-
-.. _zc.buildout: http://cheeseshop.python.org/pypi/zc.buildout
-
-You may have setuptools already installed for your system Python. In
-that case, you may need to upgrade it first because buildout requires
-a very recent version::
-
- $ sudo easy_install -U setuptools
-
-If this command fails because easy_install is not available, there is
-a good chance you do not have setuptools available for your system
-Python. If so, there is no problem because setuptools will be
-installed locally by buildout.
-
-Bootstrap the buildout environment::
-
- $ python bootstrap/bootstrap.py
-
-and run the buildout command::
-
- $ bin/buildout
- [lots of stuff will be downloaded and installed here]
-
-Note that if you have more than one sandbox for a Zope-based web
-application, it will probably make sense to share the eggs between the
-different sandboxes. You can tell zc.buildout to use a central eggs
-directory by creating ``~/.buildout/default.cfg`` with the following
-contents::
-
- [buildout]
- eggs-directory = /home/bruno/buildout-eggs
-
-Running the demo applications
------------------------------
-
-You can start Zope with the demo applications installed with the
-following command:
-
- $ bin/zopectl fg
-
-If you now connect to port 8080 and log in with username 'grok',
-password 'grok', you should be able to add the grok-based applications
-(such as grokwiki) from the menu.
-
-Running the tests
------------------
-
-Grok's tests are easily run by executing the test runner that's
-installed in the ``bin`` directory::
-
- $ bin/test
-
-Generating the website files
-----------------------------
-
-Grok's tutorial documents for the website can easily be generated
-using the following script in ``bin``:
-
- $ bin/grok2html /path/of/output/directory
Deleted: grokcore.formlib/trunk/LICENSE.txt
===================================================================
--- grokcore.formlib/trunk/LICENSE.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/LICENSE.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,44 +0,0 @@
-Zope Public License (ZPL) Version 2.1
-
-A copyright notice accompanies this license document that identifies the
-copyright holders.
-
-This license has been certified as open source. It has also been designated as
-GPL compatible by the Free Software Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions in source code must retain the accompanying copyright
-notice, this list of conditions, and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the accompanying copyright
-notice, this list of conditions, and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-
-3. Names of the copyright holders must not be used to endorse or promote
-products derived from this software without prior written permission from the
-copyright holders.
-
-4. The right to distribute this software or to use it for any purpose does not
-give you the right to use Servicemarks (sm) or Trademarks (tm) of the
-copyright
-holders. Use of them is covered by separate agreement with the copyright
-holders.
-
-5. If any files are modified, you must cause the modified files to carry
-prominent notices stating that you changed the files and the date of any
-change.
-
-Disclaimer
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY EXPRESSED
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
-EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Added: grokcore.formlib/trunk/MOVED_TO_GITHUB
===================================================================
--- grokcore.formlib/trunk/MOVED_TO_GITHUB (rev 0)
+++ grokcore.formlib/trunk/MOVED_TO_GITHUB 2013-03-01 15:41:30 UTC (rev 129947)
@@ -0,0 +1 @@
+See https://github.com/zopefoundation/grokcore.formlib
\ No newline at end of file
Deleted: grokcore.formlib/trunk/README.txt
===================================================================
--- grokcore.formlib/trunk/README.txt 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/README.txt 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,166 +0,0 @@
-This package provides support for writing forms using the Zope Formlib
-library and registering them directly in Python (without ZCML).
-
-.. contents::
-
-Setting up ``grokcore.formlib``
-===============================
-
-This package is essentially set up like the `grokcore.component`_
-package, please refer to its documentation for details. The
-additional ZCML lines you will need are::
-
- <include package="grokcore.formlib" file="meta.zcml" />
- <include package="grokcore.formlib" />
-
-Put the first line somewhere near the top of your root ZCML file.
-
-Examples
-========
-
-We need an example interface::
-
- from zope import interface, schema
-
- class IMammoth(interface.Interface):
-
- name = schema.TextLine(title=u"Name")
- age = schema.Int(title=u"Age", min=0)
-
-Edit forms
-----------
-
-You can provide an edit form for ``IMammoth`` like this::
-
-
- from grokcore import formlib
-
- class Edit(formlib.EditForm):
-
- formlib.context(IMammoth)
-
-
-If your content object is defined in the same Python file and
-implements ``grokcore.formlib.IContext``, then it will be the default
-context for your form.
-
-
-Display forms
--------------
-
-Display forms are as easy as edit forms::
-
- class Index(formlib.DisplayForm):
-
- formlib.context(IMammoth)
-
-
-Generic forms
--------------
-
-
-You can build more generic forms, providing your own actions for a form::
-
-
- class ISearch(interface.Interface):
-
- search = schema.TextLine(title=u"Text")
-
-
-After this, you define your form. It's applied to a mammoth, but uses
-the ``ISearch`` interface to generate fields::
-
- class Search(formlib.Form):
-
- formlib.context(IMammoth)
-
- form_fields = formlib.Fields(ISearch)
-
- def update(self):
- # Default search results are None
- self.search_result = None
-
- @formlib.action(u"Search")
- def search(self, text):
- self.search_result = 'something found with text'
-
-
-
-Create a custom template ``search.pt`` to render your form (in a
-directory ``modulename_templates``).
-
-
-Add forms
----------
-
-Add forms work like generic forms, you have to provide your action
-``Add``.
-
-Customization
--------------
-
-Since a Grok form is a Grok view, all configuration directives and
-attributes available on a Grok view are available as well on a Grok
-form.
-
-This means that you can customize your form by associating a template
-with it. The template is responsible for displaying widgets and
-actions. The API to access them is the same as on a Zope Formlib form.
-
-You can't customize a form by providing a ``render()`` method on it,
-but you can still use the ``update()`` method if you want.
-
-Please refer to the documentation of `grokcore.view`_ for more
-details.
-
-API Overview
-============
-
-Base classes
-------------
-
-``EditForm``
- Extends ``Form`` to create an edit form for your content.
-
-``DisplayForm``
- Creates simple display forms.
-
-``Form``
- Is a base class to create generic forms.
-
-``AddForm``
- Extends ``Form`` to create add forms. You have to provide the *add*
- action which is going to create the new object.
-
-
-
-Decorators
-----------
-
-``action``
- Is a decorator to create an action on the form. Your action only has
- to accept values from the form as parameters.
-
-Helpers
--------
-
-``AutoFields``
- Create form fields from the given context. If the context is an
- interface, Zope fields defined in that interface are going to be
- used to build form fields.
- If the context is a regular object, Zope fields of all implemented
- interfaces of that object are going to used to build form fields.
-
-``Fields``
- Create and reorder fields on the form.
-
-
-Additionally, the ``grokcore.formlib`` package exposes the
-`grokcore.component`_, `grokcore.security`_ and `grokcore.view`_ APIs.
-
-.. _grokcore.component: http://pypi.python.org/pypi/grokcore.component
-.. _grokcore.formlib: http://pypi.python.org/pypi/grokcore.formlib
-.. _grokcore.security: http://pypi.python.org/pypi/grokcore.security
-.. _grokcore.view: http://pypi.python.org/pypi/grokcore.view
-
-
Deleted: grokcore.formlib/trunk/bootstrap.py
===================================================================
--- grokcore.formlib/trunk/bootstrap.py 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/bootstrap.py 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,258 +0,0 @@
-##############################################################################
-#
-# Copyright (c) 2006 Zope Foundation and Contributors.
-# All Rights Reserved.
-#
-# This software is subject to the provisions of the Zope Public License,
-# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
-# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
-# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
-# FOR A PARTICULAR PURPOSE.
-#
-##############################################################################
-"""Bootstrap a buildout-based project
-
-Simply run this script in a directory containing a buildout.cfg.
-The script accepts buildout command-line options, so you can
-use the -c option to specify an alternate configuration file.
-"""
-
-import os, shutil, sys, tempfile, textwrap, urllib, urllib2, subprocess
-from optparse import OptionParser
-
-if sys.platform == 'win32':
- def quote(c):
- if ' ' in c:
- return '"%s"' % c # work around spawn lamosity on windows
- else:
- return c
-else:
- quote = str
-
-# See zc.buildout.easy_install._has_broken_dash_S for motivation and comments.
-stdout, stderr = subprocess.Popen(
- [sys.executable, '-Sc',
- 'try:\n'
- ' import ConfigParser\n'
- 'except ImportError:\n'
- ' print 1\n'
- 'else:\n'
- ' print 0\n'],
- stdout=subprocess.PIPE, stderr=subprocess.PIPE).communicate()
-has_broken_dash_S = bool(int(stdout.strip()))
-
-# In order to be more robust in the face of system Pythons, we want to
-# run without site-packages loaded. This is somewhat tricky, in
-# particular because Python 2.6's distutils imports site, so starting
-# with the -S flag is not sufficient. However, we'll start with that:
-if not has_broken_dash_S and 'site' in sys.modules:
- # We will restart with python -S.
- args = sys.argv[:]
- args[0:0] = [sys.executable, '-S']
- args = map(quote, args)
- os.execv(sys.executable, args)
-# Now we are running with -S. We'll get the clean sys.path, import site
-# because distutils will do it later, and then reset the path and clean
-# out any namespace packages from site-packages that might have been
-# loaded by .pth files.
-clean_path = sys.path[:]
-import site
-sys.path[:] = clean_path
-for k, v in sys.modules.items():
- if (hasattr(v, '__path__') and
- len(v.__path__)==1 and
- not os.path.exists(os.path.join(v.__path__[0],'__init__.py'))):
- # This is a namespace package. Remove it.
- sys.modules.pop(k)
-
-is_jython = sys.platform.startswith('java')
-
-setuptools_source = 'http://peak.telecommunity.com/dist/ez_setup.py'
-distribute_source = 'http://python-distribute.org/distribute_setup.py'
-
-# parsing arguments
-def normalize_to_url(option, opt_str, value, parser):
- if value:
- if '://' not in value: # It doesn't smell like a URL.
- value = 'file://%s' % (
- urllib.pathname2url(
- os.path.abspath(os.path.expanduser(value))),)
- if opt_str == '--download-base' and not value.endswith('/'):
- # Download base needs a trailing slash to make the world happy.
- value += '/'
- else:
- value = None
- name = opt_str[2:].replace('-', '_')
- setattr(parser.values, name, value)
-
-usage = '''\
-[DESIRED PYTHON FOR BUILDOUT] bootstrap.py [options]
-
-Bootstraps a buildout-based project.
-
-Simply run this script in a directory containing a buildout.cfg, using the
-Python that you want bin/buildout to use.
-
-Note that by using --setup-source and --download-base to point to
-local resources, you can keep this script from going over the network.
-'''
-
-parser = OptionParser(usage=usage)
-parser.add_option("-v", "--version", dest="version",
- help="use a specific zc.buildout version")
-parser.add_option("-d", "--distribute",
- action="store_true", dest="use_distribute", default=False,
- help="Use Distribute rather than Setuptools.")
-parser.add_option("--setup-source", action="callback", dest="setup_source",
- callback=normalize_to_url, nargs=1, type="string",
- help=("Specify a URL or file location for the setup file. "
- "If you use Setuptools, this will default to " +
- setuptools_source + "; if you use Distribute, this "
- "will default to " + distribute_source +"."))
-parser.add_option("--download-base", action="callback", dest="download_base",
- callback=normalize_to_url, nargs=1, type="string",
- help=("Specify a URL or directory for downloading "
- "zc.buildout and either Setuptools or Distribute. "
- "Defaults to PyPI."))
-parser.add_option("--eggs",
- help=("Specify a directory for storing eggs. Defaults to "
- "a temporary directory that is deleted when the "
- "bootstrap script completes."))
-parser.add_option("-t", "--accept-buildout-test-releases",
- dest='accept_buildout_test_releases',
- action="store_true", default=False,
- help=("Normally, if you do not specify a --version, the "
- "bootstrap script and buildout gets the newest "
- "*final* versions of zc.buildout and its recipes and "
- "extensions for you. If you use this flag, "
- "bootstrap and buildout will get the newest releases "
- "even if they are alphas or betas."))
-parser.add_option("-c", None, action="store", dest="config_file",
- help=("Specify the path to the buildout configuration "
- "file to be used."))
-
-options, args = parser.parse_args()
-
-# if -c was provided, we push it back into args for buildout's main function
-if options.config_file is not None:
- args += ['-c', options.config_file]
-
-if options.eggs:
- eggs_dir = os.path.abspath(os.path.expanduser(options.eggs))
-else:
- eggs_dir = tempfile.mkdtemp()
-
-if options.setup_source is None:
- if options.use_distribute:
- options.setup_source = distribute_source
- else:
- options.setup_source = setuptools_source
-
-if options.accept_buildout_test_releases:
- args.append('buildout:accept-buildout-test-releases=true')
-args.append('bootstrap')
-
-try:
- import pkg_resources
- import setuptools # A flag. Sometimes pkg_resources is installed alone.
- if not hasattr(pkg_resources, '_distribute'):
- raise ImportError
-except ImportError:
- ez_code = urllib2.urlopen(
- options.setup_source).read().replace('\r\n', '\n')
- ez = {}
- exec ez_code in ez
- setup_args = dict(to_dir=eggs_dir, download_delay=0)
- if options.download_base:
- setup_args['download_base'] = options.download_base
- if options.use_distribute:
- setup_args['no_fake'] = True
- ez['use_setuptools'](**setup_args)
- reload(sys.modules['pkg_resources'])
- import pkg_resources
- # This does not (always?) update the default working set. We will
- # do it.
- for path in sys.path:
- if path not in pkg_resources.working_set.entries:
- pkg_resources.working_set.add_entry(path)
-
-cmd = [quote(sys.executable),
- '-c',
- quote('from setuptools.command.easy_install import main; main()'),
- '-mqNxd',
- quote(eggs_dir)]
-
-if not has_broken_dash_S:
- cmd.insert(1, '-S')
-
-find_links = options.download_base
-if not find_links:
- find_links = os.environ.get('bootstrap-testing-find-links')
-if find_links:
- cmd.extend(['-f', quote(find_links)])
-
-if options.use_distribute:
- setup_requirement = 'distribute'
-else:
- setup_requirement = 'setuptools'
-ws = pkg_resources.working_set
-setup_requirement_path = ws.find(
- pkg_resources.Requirement.parse(setup_requirement)).location
-env = dict(
- os.environ,
- PYTHONPATH=setup_requirement_path)
-
-requirement = 'zc.buildout'
-version = options.version
-if version is None and not options.accept_buildout_test_releases:
- # Figure out the most recent final version of zc.buildout.
- import setuptools.package_index
- _final_parts = '*final-', '*final'
- def _final_version(parsed_version):
- for part in parsed_version:
- if (part[:1] == '*') and (part not in _final_parts):
- return False
- return True
- index = setuptools.package_index.PackageIndex(
- search_path=[setup_requirement_path])
- if find_links:
- index.add_find_links((find_links,))
- req = pkg_resources.Requirement.parse(requirement)
- if index.obtain(req) is not None:
- best = []
- bestv = None
- for dist in index[req.project_name]:
- distv = dist.parsed_version
- if _final_version(distv):
- if bestv is None or distv > bestv:
- best = [dist]
- bestv = distv
- elif distv == bestv:
- best.append(dist)
- if best:
- best.sort()
- version = best[-1].version
-if version:
- requirement = '=='.join((requirement, version))
-cmd.append(requirement)
-
-if is_jython:
- import subprocess
- exitcode = subprocess.Popen(cmd, env=env).wait()
-else: # Windows prefers this, apparently; otherwise we would prefer subprocess
- exitcode = os.spawnle(*([os.P_WAIT, sys.executable] + cmd + [env]))
-if exitcode != 0:
- sys.stdout.flush()
- sys.stderr.flush()
- print ("An error occurred when trying to install zc.buildout. "
- "Look above this message for any errors that "
- "were output by easy_install.")
- sys.exit(exitcode)
-
-ws.add_entry(eggs_dir)
-ws.require(requirement)
-import zc.buildout.buildout
-zc.buildout.buildout.main(args)
-if not options.eggs: # clean up temporary egg directory
- shutil.rmtree(eggs_dir)
Deleted: grokcore.formlib/trunk/buildout.cfg
===================================================================
--- grokcore.formlib/trunk/buildout.cfg 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/buildout.cfg 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,21 +0,0 @@
-[buildout]
-develop = .
-parts = interpreter test
-extends = http://svn.zope.org/repos/main/groktoolkit/trunk/grok.cfg
-versions = versions
-extensions = buildout.dumppickedversions
-
-
-[versions]
-grokcore.formlib =
-
-[interpreter]
-recipe = zc.recipe.egg
-eggs = grokcore.formlib
-interpreter = python
-
-[test]
-recipe = zc.recipe.testrunner
-eggs = grokcore.formlib
- grokcore.formlib[test]
-defaults = ['--tests-pattern', '^f?tests$', '-v']
Deleted: grokcore.formlib/trunk/setup.py
===================================================================
--- grokcore.formlib/trunk/setup.py 2013-03-01 15:41:19 UTC (rev 129946)
+++ grokcore.formlib/trunk/setup.py 2013-03-01 15:41:30 UTC (rev 129947)
@@ -1,57 +0,0 @@
-from setuptools import setup, find_packages
-import os
-
-def read(*rnames):
- return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
-
-long_description = (
- read('README.txt')
- + '\n' +
- read('CHANGES.txt')
- )
-
-tests_require = [
- 'zope.app.wsgi [test]',
- 'zope.configuration',
- 'zope.testing',
- ]
-
-setup(
- name='grokcore.formlib',
- version='1.10.dev0',
- author='Grok Team',
- author_email='grok-dev at zope.org',
- url='http://grok.zope.org',
- download_url='http://cheeseshop.python.org/pypi/grokcore.formlib',
- description='Grok-like configuration for zope.formlib components',
- long_description=long_description,
- license='ZPL',
- classifiers=['Environment :: Web Environment',
- 'Intended Audience :: Developers',
- 'License :: OSI Approved :: Zope Public License',
- 'Programming Language :: Python',
- 'Framework :: Zope3',
- ],
-
- packages=find_packages('src'),
- package_dir = {'': 'src'},
- namespace_packages=['grokcore'],
- include_package_data = True,
- zip_safe=False,
- install_requires=['setuptools',
- 'grokcore.component >= 2.1',
- 'grokcore.security >= 1.5',
- 'grokcore.view >= 2.0',
- 'martian >= 0.13',
- 'pytz',
- 'zope.container',
- 'zope.event',
- 'zope.formlib',
- 'zope.interface',
- 'zope.lifecycleevent',
- 'zope.publisher',
- 'zope.schema',
- ],
- tests_require=tests_require,
- extras_require={'test': tests_require},
-)
More information about the checkins
mailing list