commit
b986640bf1
2
.gitignore
vendored
2
.gitignore
vendored
@ -2,6 +2,8 @@
|
||||
/.coverage
|
||||
/.tox
|
||||
/.venv
|
||||
/AUTHORS
|
||||
/ChangeLog
|
||||
/build
|
||||
/cov_html
|
||||
/dist
|
||||
|
24
README.rst
24
README.rst
@ -1,3 +1,27 @@
|
||||
=======
|
||||
Striker
|
||||
=======
|
||||
|
||||
Striker is a deployment package builder, capable of building packages
|
||||
in several different formats, running basic tests on those packages,
|
||||
and distributing them. It is a tool for managing the build and
|
||||
release lifecycle.
|
||||
|
||||
Packaging
|
||||
=========
|
||||
|
||||
Why another packaging tool? After all, the Python world already has
|
||||
eggs and wheels, and they work really well, right? Well, yes and no.
|
||||
A wheel (or the older egg) contains a single package and information
|
||||
about its dependencies. Installing a full project onto a system
|
||||
requires that several wheels be downloaded and installed, and we often
|
||||
have dependencies on the exact versions that are used--i.e., which
|
||||
exact versions have we performed acceptance tests against? Also, when
|
||||
you're talking about installing a package across several thousand
|
||||
machines, just downloading all those dependencies represents an
|
||||
enormous network load.
|
||||
|
||||
Striker is intended to help with this problem. The packages it builds
|
||||
include all of the dependencies into a single artifact, which can then
|
||||
be distributed to those several thousand systems in a much more
|
||||
scalable fashion, such as a peer-to-peer system like BitTorrent.
|
||||
|
@ -877,12 +877,6 @@ class ConfigMeta(type):
|
||||
configuration value keys to those ``Binding`` instances. It also
|
||||
initializes schema-related class attributes, such as
|
||||
``_schema_raw``, ``_schema_cache``, and ``_parents``.
|
||||
|
||||
Note that a class is officially an instance of its metaclass, so
|
||||
methods and properties defined on ``ConfigMeta`` become class
|
||||
methods and properties on the ``Config`` subclass. These methods
|
||||
and properties do not appear on *instances* of ``Config``,
|
||||
however.
|
||||
"""
|
||||
|
||||
def __new__(mcs, name, bases, namespace):
|
||||
|
Loading…
x
Reference in New Issue
Block a user