[Checkins] SVN: martian/trunk/ Moved to GitHub.
Stephen Richter
cvs-admin at zope.org
Fri Mar 1 15:43:29 UTC 2013
Log message for revision 129962:
Moved to GitHub.
Changed:
D martian/trunk/CHANGES.txt
D martian/trunk/COPYRIGHT.txt
D martian/trunk/CREDITS.txt
D martian/trunk/LICENSE.txt
A martian/trunk/MOVED_TO_GITHUB
D martian/trunk/README.txt
D martian/trunk/bootstrap.py
D martian/trunk/buildout.cfg
D martian/trunk/setup.py
D martian/trunk/src/
-=-
Deleted: martian/trunk/CHANGES.txt
===================================================================
--- martian/trunk/CHANGES.txt 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/CHANGES.txt 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,330 +0,0 @@
-CHANGES
-*******
-
-0.15 (unreleased)
-=================
-
-- Fix an encoding issue under Python-2.7 in the doctests.
-
-0.14 (2010-11-03)
-=================
-
-Feature changes
----------------
-
-* The computation of the default value for a directive can now be defined inside
- the directive class definition. Whenever there is a ``get_default``
- classmethod, it is used for computing the default::
-
- class name(Directive):
- scope = CLASS
- store = ONCE
-
- @classmethod
- def get_default(cls, component, module=None, **data):
- return component.__name__.lower()
-
- When binding the directive, the default-default behaviour can still be
- overriden by passing a ``get_default`` function::
-
- def another_default(component, module=None, **data):
- return component.__name__.lower()
-
- name.bind(get_default=another_default).get(some_component)
-
- Making the default behaviour intrinsic to the directive, prevents having to
- pass the ``get_default`` function over and over when getting values, for
- example in the grokkers.
-
-0.13 (2010-11-01)
-=================
-
-Feature changes
----------------
-
-* Ignore all __main__ modules.
-
-* List zope.testing as a test dependency.
-
-0.12 (2009-06-29)
-=================
-
-Feature changes
----------------
-
-* Changes to better support various inheritance scenarios in combination with
- directives. Details follow.
-
-* ``CLASS_OR_MODULE`` scope directives will be aware of inheritance of
- values that are defined in module-scope. Consider the following case::
-
- module a:
- some_directive('A')
- class Foo(object):
- pass
-
- module b:
- import a
- class Bar(a.Foo):
- pass
-
- As before, ``Foo`` will have the value ``A`` configured for it. ``Bar``,
- since it inherits from ``Foo``, will inherit this value.
-
-* ``CLASS_OR_MODULE`` and ``CLASS`` scope directives will be aware of
- inheritance of computed default values. Consider the following case::
-
- module a:
- class Foo(object):
- pass
-
- module b:
- import a
- class Bar(a.Foo):
- pass
-
- def get_default(component, module, **data):
- if module.__name__ == 'a':
- return "we have a default value for module a"
- return martian.UNKNOWN
-
- When we now do this::
-
- some_directive.bind(get_default=get_default).get(b.Bar)
-
- We will get the value "we have a default value for module a". This
- is because when trying to compute the default value for ``Bar`` we
- returned ``martian.UNKNOWN`` to indicate the value couldn't be found
- yet. The system then looks at the base class and tries again, and in
- this case it succeeds (as the module-name is ``a``).
-
-* ``martian.ONCE_IFACE`` storage option to allow the creation of
- directives that store their value on ``zope.interface``
- interfaces. This was originally in ``grokcore.view`` but was of
- wider usefulness.
-
-Bugs fixed
-----------
-
-* Ignore things that look like Python modules and packages but aren't.
- These are sometimes created by editors, operating systems and
- network file systems and we don't want to confuse them.
-
-* Ignore .pyc and .pyo files that don't have a matching .py file via
- ``module_info_from_dotted_name`` if its ``ignore_nonsource``
- parameter is ``True``. The default is ``True``. To revert to the
- older behavior where .pyc files were honored, pass
- ``ignore_nonsource=False``.
-
-* Pass along ``exclude_filter`` (and the new ``ignore_nonsource``
- flag) to ModuleInfo constructor when it calls itself recursively.
-
-* Replace ``fake_import`` to import fake modules in tests with a real
- python import statement (``from martiantest.fake import
- my_fake_module``). This works by introducing a metaclass for
- ``FakeModule`` that automatically registers it as a module. The
- irony does not escape us. This also means that
- ``martian.scan.resolve()`` will now work on fake modules.
-
-0.11 (2008-09-24)
-=================
-
-Feature changes
----------------
-
-* Added MULTIPLE_NOBASE option for directive store. This is like MULTIPLE
- but doesn't inherit information from the base class.
-
-0.10 (2008-06-06)
-=================
-
-Feature changes
----------------
-
-* Add a ``validateClass`` validate function for directives.
-
-* Moved ``FakeModule`` and ``fake_import`` into a ``martian.testing``
- module so that they can be reused by external packages.
-
-* Introduce new tutorial text as README.txt. The text previously in
- ``README.txt`` was rather too detailed for a tutorial, so has been
- moved into ``core.txt``.
-
-* Introduce a ``GrokkerRegistry`` class that is a ``ModuleGrokker``
- with a ``MetaMultiGrokker`` in it. This is the convenient thing to
- instantiate to start working with Grok and is demonstrated in the
- tutorial.
-
-* Introduced three new martian-specific directives:
- ``martian.component``, ``martian.directive`` and
- ``martian.priority``. These replace the ``component_class``,
- ``directives`` and ``priority`` class-level attributes. This way
- Grokkers look the same as what they grok. This breaks backwards
- compatibility again, but it's an easy replace operation. Note that
- ``martian.directive`` takes the directive itself as an argument, and
- then optionally the same arguments as the ``bind`` method of
- directives (``name``, ``default`` and ``get_default``). It may be
- used multiple times. Note that ``martian.baseclass`` was already a
- Martian-specific directive and this has been unchanged.
-
-* For symmetry, add an ``execute`` method to ``InstanceGrokker``.
-
-0.9.7 (2008-05-29)
-==================
-
-Feature changes
----------------
-
-* Added a ``MethodGrokker`` base class for grokkers that want to grok
- methods of a class rather than the whole class itself. It works
- quite similar to the ``ClassGrokker`` regarding directive
- definition, except that directives evaluated not only on class (and
- possibly module) level but also for each method. That way,
- directives can also be applied to methods (as decorators) in case
- they support it.
-
-0.9.6 (2008-05-14)
-==================
-
-Feature changes
----------------
-
-* Refactored the ``martian.Directive`` base class yet again to allow
- more declarative (rather than imperative) usage in grokkers.
- Directives themselves no longer have a ``get()`` method nor a
- default value factory (``get_default()``). Instead you will have to
- "bind" the directive first which is typically done in a grokker.
-
-* Extended the ``ClassGrokker`` baseclass with a standard ``grok()``
- method that allows you to simply declare a set of directives that
- are used on the grokked classes. Then you just have to implement an
- ``execute()`` method that will receive the data from those
- directives as keyword arguments. This simplifies the implementation
- of class grokkers a lot.
-
-0.9.5 (2008-05-04)
-==================
-
-* ``scan_for_classes`` just needs a single second argument specifying
- an interface. The support for scanning for subclasses directly has
- been removed as it became unnecessary (due to changes in
- grokcore.component).
-
-0.9.4 (2008-05-04)
-==================
-
-Features changes
-----------------
-
-* Replaced the various directive base classes with a single
- ``martian.Directive`` base class:
-
- - The directive scope is now defined with the ``scope`` class
- attribute using one of ``martian.CLASS``, ``martian.MODULE``,
- ``martian.CLASS_OR_MODULE``.
-
- - The type of storage is defined with the ``store`` class attribute
- using one of ``martian.ONCE``, ``martian.MULTIPLE``,
- ``martian.DICT``.
-
- - Directives have now gained the ability to read the value that they
- have set on a component or module using a ``get()`` method. The
- ``class_annotation`` and ``class_annotation_list`` helpers have
- been removed as a consequence.
-
-* Moved the ``baseclass()`` directive from Grok to Martian.
-
-* Added a ``martian.util.check_provides_one`` helper, in analogy to
- ``check_implements_one``.
-
-* The ``scan_for_classes`` helper now also accepts an ``interface``
- argument which allows you to scan for classes based on interface
- rather than base classes.
-
-Bug fixes
----------
-
-* added dummy ``package_dotted_name`` to ``BuiltinModuleInfo``. This
- allows the grokking of views in test code using Grok's
- ``grok.testing.grok_component`` without a failure when it sets up the
- ``static`` attribute.
-
-* no longer use the convention that classes ending in -Base will be considered
- base classes. You must now explicitly use the grok.baseclass() directive.
-
-* The type check of classes uses isinstance() instead of type(). This means
- Grok can work with Zope 2 ExtensionClasses and metaclass programming.
-
-0.9.3 (2008-01-26)
-==================
-
-Feature changes
----------------
-
-* Added an OptionalValueDirective which allows the construction of
- directives that take either zero or one argument. If no arguments
- are given, the ``default_value`` method on the directive is
- called. Subclasses need to override this to return the default value
- to use.
-
-Restructuring
--------------
-
-* Move some util functions that were really grok-specific out of Martian
- back into Grok.
-
-0.9.2 (2007-11-20)
-==================
-
-Bug fixes
----------
-
-* scan.module_info_from_dotted_name() now has special behavior when it
- runs into __builtin__. Previously, it would crash with an error. Now
- it will return an instance of BuiltinModuleInfo. This is a very
- simple implementation which provides just enough information to make
- client code work. Typically this client code is test-related so that
- the module context will be __builtin__.
-
-0.9.1 (2007-10-30)
-==================
-
-Feature changes
----------------
-
-* Grokkers now receive a ``module_info`` keyword argument. This
- change is completely backwards-compatible since grokkers which don't
- take ``module_info`` explicitly will absorb the extra argument in
- ``**kw``.
-
-0.9 (2007-10-02)
-=================
-
-Feature changes
----------------
-
-* Reverted the behaviour where modules called tests or ftests were skipped
- by default and added an API to provides a filtering function for skipping
- modules to be grokked.
-
-0.8.1 (2007-08-13)
-==================
-
-Feature changes
----------------
-
-* Don't grok tests or ftests modules.
-
-Bugs fixed
-----------
-
-* Fix a bug where if a class had multiple base classes, this could end up
- in the resultant list multiple times.
-
-0.8 (2007-07-02)
-================
-
-Feature changes
----------------
-
-* Initial public release.
Deleted: martian/trunk/COPYRIGHT.txt
===================================================================
--- martian/trunk/COPYRIGHT.txt 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/COPYRIGHT.txt 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1 +0,0 @@
-Zope Foundation and Contributors
\ No newline at end of file
Deleted: martian/trunk/CREDITS.txt
===================================================================
--- martian/trunk/CREDITS.txt 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/CREDITS.txt 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,21 +0,0 @@
-CREDITS
-=======
-
-* Martijn Faassen
-
-* Wolfgang Schnerring
-
-* Christian Theune
-
-* Philipp von Weitershausen
-
-* Jan-Wijbrand Kolman
-
-* Luciano Ramalho
-
-* Chris McDonough
-
-Thank you
----------
-
-* The core Grok developers.
Deleted: martian/trunk/LICENSE.txt
===================================================================
--- martian/trunk/LICENSE.txt 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/LICENSE.txt 2013-03-01 15:43:29 UTC (rev 129962)
@@ -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: martian/trunk/MOVED_TO_GITHUB
===================================================================
--- martian/trunk/MOVED_TO_GITHUB (rev 0)
+++ martian/trunk/MOVED_TO_GITHUB 2013-03-01 15:43:29 UTC (rev 129962)
@@ -0,0 +1 @@
+See https://github.com/zopefoundation/martian
\ No newline at end of file
Deleted: martian/trunk/README.txt
===================================================================
--- martian/trunk/README.txt 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/README.txt 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,5 +0,0 @@
-*******
-Martian
-*******
-
-A library to grok configuration from Python code.
Deleted: martian/trunk/bootstrap.py
===================================================================
--- martian/trunk/bootstrap.py 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/bootstrap.py 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,260 +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 k in ('setuptools', 'pkg_resources') or (
- 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)
- if 'pkg_resources' in sys.modules:
- 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: martian/trunk/buildout.cfg
===================================================================
--- martian/trunk/buildout.cfg 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/buildout.cfg 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,13 +0,0 @@
-[buildout]
-develop = .
-parts = devpython test
-
-[devpython]
-recipe = zc.recipe.egg
-interpreter = devpython
-eggs = martian
-
-[test]
-recipe = zc.recipe.testrunner
-eggs = martian
- martian[test]
Deleted: martian/trunk/setup.py
===================================================================
--- martian/trunk/setup.py 2013-03-01 15:43:23 UTC (rev 129961)
+++ martian/trunk/setup.py 2013-03-01 15:43:29 UTC (rev 129962)
@@ -1,41 +0,0 @@
-import os
-from setuptools import setup, find_packages
-
-def read(*rnames):
- return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
-
-long_description = (
- read('README.txt')
- + '\n' +
- read('src', 'martian', 'README.txt')
- + '\n' +
- read('CHANGES.txt')
- + '\n' +
- 'Download\n'
- '********\n'
- )
-
-setup(
- name='martian',
- version='0.15dev',
- author='Grok project',
- author_email='grok-dev at zope.org',
- description="""\
-Martian is a library that allows the embedding of configuration
-information in Python code. Martian can then grok the system and
-do the appropriate configuration registrations. One example of a system
-that uses Martian is the system where it originated: Grok
-(http://grok.zope.org)
-""",
- long_description=long_description,
- packages=find_packages('src'),
- package_dir = {'': 'src'},
- include_package_data = True,
- zip_safe=False,
- license='ZPL',
- install_requires=[
- 'zope.interface',
- 'setuptools',
- ],
- extras_require = dict(test=['zope.testing']),
-)
More information about the checkins
mailing list