This fixes all the warnings emitted by flake8, mostly involving
qualified imports, import grouping, and indentation.
Change-Id: Ia45839f3e65e15a34e2a2793fd21b83e4fc891d7
Needed-By: I158ea10f104549dd4f0f3ff777b39feb5886642e
* update test requirements with what's in g-r
* Remove hard-coded dependencies from tox.ini as update-requirements
does not edit tox.ini
* Remove requirements.txt as it is redundant (sdist already has it)
* Fix up all the issues identified by flake8
Co-Authored-By: Robert Collins <rbtcollins@hp.com>
Change-Id: I0508bd74edda20fbf844e7303c9b44b80ff794ef
Use parentheses for `print`, 0o for an octal literal, "as" for except.
import print_function from __future__.
Change-Id: Ie76910c3e0a03e4a103f612639a1b74e84f182bb
To further align with the canonical form of PEP440, pre-versions
leading to $VERSION should no longer be ${VERSION}b1 but
${VERSION}.0b1.
The logic to determine that is duplicated in upload_release.py, so
until we rearchitect that that needs to be fixed there too.
Change-Id: Ic0bb8f5e9ba31370cd495f4396eb1b1306e06911
The recently split neutron-*aas need special treatment in release
scripts. The extra deliverables need to be uploaded to the same
Launchpad milestone page, and bugs should only be closed once (all
projects share the same Launchpad bug pages).
To this effect, we distinguish in the scripts the Launchpad concept
of project from the git project name as used in tarballs and skip
parts as needed. We also introduce an optional --deliverable option
to upload_release.py so that it can use different values for both.
Change-Id: I8a4db8b09a3b9d480a767ea0ce94373b4528d1a2
Switch to using X.Y.Z format (think: 2015.1.0) versions for final
versions, X.Y.Z{b,rc}N for milestones and release candidates, to
match PEP440-normalized versions that setuptools and our tooling
now produce for our tarballs.
Change-Id: I42bd41b7fd2d9f1e9ead8a76f11a54926b637fdf
The usage of /usr/bin/env ensures that the first interpreter
found in the environment's $PATH variable is used. This should
be preferred.
Change-Id: I4011ec477534f920092cc323a26e75ff26a90051
For intermediary releases of Swift, first a RC tag is pushed on master
and bugs get fixreleased (using swiftrc.sh) then we use milestone.sh
in SKIPBUGS mode to push the final tag and upload the resulting tarball
without affecting bugs.
oslo-incubator does not produce tarballs, but we still want tags and
mark the 'oslo' Launchpad project milestone "released". We use
milestone.sh in SKIPTARBALL mode to just skip tarball wait and call
upload_release.py with the --nop argument to skip tarball upload.
oslo.messaging is not tagged at milestones, but we still want to mark
the milestone "released". We use milestone.sh in SKIPTARBALL and SKIPTAG
mode to skip tagging completely, skip tarball wait and call
upload_release.py with the --nop argument to skip tarball upload.
Change-Id: I7e670d2dd5052460a593a06e82dc212d176a395d
According to https://docs.python.org/3/howto/pyporting.html the
syntax changed in Python 3.x. The new syntax is usable with
Python >= 2.6 and should be preferred to be compatible with Python3.
Change-Id: I4624c9be5c70e4401c67f4f053daa9e85e3cdea4
Tarballs are now built when a tag is pushed. upload_release should
therefore support downloading that versioned tarball by default
(project-version~milestone.tar.gz). You can still use --tarball to
specify a specific tarball ("--tarball=milestone-proposed").
Jeremy Stanley