openstack/deb-python-fixtures
Code Issues Proposed changes

Release 0.3.17.

Browse Source
This commit is contained in:
Robert Collins
2014-09-26 09:09:29 +12:00
parent f556cff258
commit 88bf7ff386
3 changed files with 12 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
HACKING
View File

@@ -36,8 +36,7 @@ the fixtures __init__.py.
Releasing
+++++++++
1. Update the version number in __init__.py and setup.py and add a version to
NEWS.
1. Update the version number in __init__.py and add a version to NEWS.
1. Upload to pypi, signed.

3
NEWS
View File

@@ -6,6 +6,9 @@ fixtures release notes
NEXT
~~~~
0.3.17
~~~~~~
* FakeLogger now supports the ``datefmt`` parameter.
(Sean Dague)

29
fixtures/__init__.py
View File

@@ -36,7 +36,14 @@ Most users will want to look at TestWithFixtures and Fixture, to start with.
# established at this point, and setup.py will use a version of next-$(revno).
# If the releaselevel is 'final', then the tarball will be major.minor.micro.
# Otherwise it is major.minor.micro~$(revno).
__version__ = (0, 3, 16, 'final', 0)
# Uncomment when pbr 0.11 is released.
#import pbr.version
#_version = pbr.version.VersionInfo('fixtures').semantic_version()
#__version__ = _version.version_tuple()
#version = _version.release_string()
__version__ = (0, 3, 17, 'final', 0)
__all__ = [
'ByteStream',
@@ -67,8 +74,6 @@ __all__ = [
]
import pbr.version
from fixtures.fixture import (
Fixture,
FunctionFixture,
@@ -97,24 +102,6 @@ from fixtures._fixtures import (
)
from fixtures.testcase import TestWithFixtures
# same format as sys.version_info: "A tuple containing the five components of
# the version number: major, minor, micro, releaselevel, and serial. All
# values except releaselevel are integers; the release level is 'alpha',
# 'beta', 'candidate', or 'final'. The version_info value corresponding to the
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
# releaselevel of 'dev' for unreleased under-development code.
#
# If the releaselevel is 'alpha' then the major/minor/micro components are not
# established at this point, and setup.py will use a version of next-$(revno).
# If the releaselevel is 'final', then the tarball will be major.minor.micro.
# Otherwise it is major.minor.micro~$(revno).
# Uncomment when pbr 0.11 is released.
#_version = pbr.version.VersionInfo('fixtures').semantic_version()
#__version__ = _version.version_tuple()
#version = _version.release_string()
__version__ = (0, 3, 17, 'alpha', 0)
def test_suite():
import fixtures.tests