This is the fabulous result of running the update.py script from
openstack/requirements with this repository as the target. It therefore
updates all dependencies, with nice version numbers that this repository
have to use to work. It also fixes case on some dependencies.
This update also brings a brand shiny new setup.py automatically handled
and generate by this same openstack/requirements repository.
Change-Id: I22ec396e5fa802c1617514aa6df3ed82f05271b0
This is a workaround for bug 1194742. There is actually a bug in
upstream d2to1 that has a PR up:
https://github.com/iguananaut/d2to1/pull/32
But until that is released, this should fix the immediate problem.
Change-Id: I136b8493c8d8d48a0116facf5f23c2a1479c070f
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
Again discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-March/thread.html#6283http://lists.openstack.org/pipermail/openstack-dev/2013-March/thread.html#6138
The rationale is that the use of namespace packages is likely to
increase and there is apparently some consensus that the convention
should be to use period to separate the namespace package name from
the subpackage name - i.e. call it oslo.config. The zope.interface is
an example of this convention, but PasteDepoy is a counter-example.
Oslo is going to have a family of libraries, so it'd be much nicer if
they followed what the future Python convention is likely to be.
This is a disruptive change for packagers and the benefit isn't huge,
but pairing it with the also disruptive change to the versioning
scheme makes it somewhat more acceptable.
Change-Id: I63e96a8b48b166b07f1c8e79b6eaffb6234cc751
Discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-March/006283.html
The date based 2013.1 version is likely to be disallowed by PEP426
when it is ratified and we'll be required to treat the date based
version as a "private version" and use 0.2013.1 as the official
version.
Also, I'm coming around to the idea of using semantic versioning
(i.e. x.y.z) and increasing the major number when removing any
deprecated APIs. Th is the trend that Python is following according to
a discussion on distutils-sig.
One consequence of using semantic versioning is that we'll be very
loathe to remove any deprecated APIs since it will mean a version bump
from 1.y.z to 2.y.z. That's probably not a bad thing.
With this versioning scheme, I figure we should start with 1.1.0
(2013.1-2012). We'll increase the micro number when we do release from
the stable branch and increase the minor number with every coordinated
OpenStack release.
Change-Id: Ibe033d37742b82dee5f42d9e3d6a0b51582bd3ce
Each package under a namespace that should install that namespace
package so the __init__.py for the namespace gets copied.
Fixes Bug 1129587
Change-Id: I064b05479c8a41d8f793886d2a5895dce166a85a
Add basic sphinx config and copy the theming from oslo-incubator which
was originally copied from keystone.
Change-Id: Ibb3b679ce6e160c157ff63f0943807bd82aa1a67
Changes include:
6b3c544 setup: count revs for revno if there are no tags
9c8685a Use revno and git sha for pre-release versioning.
5f5ef7d Add env var version override for packagers.
602aa9c trivial pep whitespace fix
Hervé Beraud