| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This helps identifying what tests are slow or if the CI got stuck on
some of them
|
| |
|
|
|
|
|
|
|
|
| |
This has been done in a way that I hope might be able to be upstreamed
in to versioneer. This is not garanteed but it would be good if it
could be.
Please see https://github.com/warner/python-versioneer/pull/186 and
https://github.com/wsalmonct/python-versioneer/tree/feature/regexTags
for further details.
|
| |
|
|
|
|
| |
This is causing pytest to try to import the recently added app1.py
from the pip related tests. This fails because it's not meant to be
imported outside of the sandbox environment.
|
| |
|
|
| |
This allows code generation with ./setup.py build_grpc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using setuptools_scm had a couple of bad problems:
o Unexpected versioning semantics, setuptools_scm would
increment the micro version by itself in the case that
we derive a version number from something that is not a tag,
making the assumption that we are "leading up to" the next
micro version.
People mostly dont expect this.
o When installing in developer mode, i.e. with `pip3 install --user -e .`,
then we were always picking the generated version at install time
and never again dynamically resolving it.
Many of our users install this way and update through git, so it's
important that we report more precise versions all the time.
This commit needs to make a series of changes at the same time:
o Adds versioneer.py to the toplevel, this is used by setup.py
for various activities.
This is modified only to inform the linter to skip
o Adds buildstream/_version.py, which is generated by versioneer
and gives us the machinery to automatically derive the correct version
This is modified only to inform the linter to skip
o Adds a .gitattributes file which informs git to substitute
the buildstream/_version.py file, this is just to ensure that
the versioning output would work if ever we used `git archive`
to release a tarball.
o Modifies setup.py and setup.cfg for versioneer
o Modifies utils.py and _frontend/cli.py such as to avoid importing
the derived version when running bash completion mode, we dont
derive the version at completion time because this can result
in running a subprocess (when running in developer install mode)
and is an undesirable overhead.
o Updates tests/frontend/version.py to expect changed version output
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
For some reason, an undesired .eggs/ directory gets created
at times by the incomprehensible pip/setuptools machinery.
This makes sure it doesnt cause noise in our tests.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream of fuse.py is <https://github.com/terencehonles/fusepy>. It looks
pretty abandoned -- there have been no commits there since 5th April 2016 and
there are 17 pull requests dating from 2013 onwards that are still waiting for
responses from the maintainer.
There's no support in fuse.py for ppc64 platforms which means BuildStream is
unusable on that architecture at present. My pull request to fix that upstream
is being ignored; since the module is a single .py file provided under the
ISC license it is simplest to pull the whole thing into buildstream.git instead.
The version of fuse.py that's been embedded is the one from pull request #72,
from upstream release v2.0.4 (commit 0eafeb5).
|
| |
|
|
| |
Turns out we do need this in some corner cases
|
| |
|
|
|
|
|
| |
Turns out this doesnt work once you try to actually
run the full buildstream in a test case (in foreground
it screws with other parsing, in background it fails
in the test context with a strange error).
|
| | |
|
| | |
|
| |
|
|
| |
Ignore multiline statement has same indentation as next logical line.
|
| |
|
|
|
| |
Pep8 should not be run on all files in the basedir. Adding
an ignore rule for if a virtual env directory exists.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
80 columns is cool but either encourages abbreviated variable names, which sucks,
or forces too many line breaks with sanely named variables.
120 columns should still discourage too many nested indentation blocks while
also allowing full variable names.
|
| | |
|
| |
|
|
|
|
|
|
| |
This is just an annoyance, as mentioned here:
https://github.com/PyCQA/pycodestyle/issues/386
This error was explicitly split out from error 125 so that
it could safely be ignored.
|
| |
|
|
| |
Now when running ./setup.py test, pep8 linter checks are automatically run.
|
| |
|
|
| |
This enables the execution of test cases that use xattrs.
|
| |
|
