summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
...
* setup.py: Specify minimum required version of pytest-cov pluginTristan Van Berkom2018-07-201-1/+1
| | | | | | This causes the new artifact tests to pass (unless you happened to already have a recent enough version of pytest-cov, in which case you didn't notice the breakage).
* Bump required python version to 3.5Tristan Maat2018-07-181-2/+2
|
* Remove OSTree artifact cacheJürg Billeter2018-07-171-43/+0
| | | | | | No longer used. Fixes #134, #138, #148, #217, #268, #276, #443, #460.
* _artifactcache: Add CAS artifact serverJürg Billeter2018-07-171-1/+2
|
* setup.py: Add grpcio dependency and support for code generationJürg Billeter2018-07-171-2/+59
| | | | This allows code generation with ./setup.py build_grpc
* Restrict version of pylint138-aborting-bst-push-command-causes-stack-trace-2Daniel Playle2018-06-201-1/+2
| | | | | | | | | | | | pylint >2 is not compatible with pytest_pylint in its current form. As such, allowing any version of pylint for testing results in a failure. This commit restricts down the allowable versions of pylint to those that are both compatible with pytest_pylint, and also offer the feature set that we require. See https://gitlab.com/BuildStream/buildstream/issues/427 for further details.
* setup.py: Stop installing test cases.Tristan Van Berkom2018-04-261-1/+1
| | | | As recommended by Valentin David in issue #332.
* Use versioneer instead of setuptools_scmTristan Van Berkom2018-04-261-12/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* setup.py: Assert Bubblewrap versionmilloni2018-04-201-4/+35
| | | | | The required version is 0.1.2 based on the fact that we're using --hostname and --remount-ro.
* pylint - disabled no-member, bad-exception-context and ↵James Ennis2018-03-141-0/+4
| | | | catching-non-exception warnings
* pylint - dealt with broad-except and bare-except warningsJames Ennis2018-03-141-1/+1
|
* Add pylint to setup.cfg and setup.pyJames Ennis2018-03-141-0/+1
|
* setup.py: Require jinja >= 2.10Javier Jardón2018-02-051-1/+1
| | | | | | jinja2 2.10 import time has been divided by two compared to Jinja 2.9.6 Fixes #194
* Get version number w/o pkg_resourcesGökçen Nurlu2018-01-311-1/+10
| | | | | | | | | | | | This removes most of the usages of pkg_resources from the codebase, helping the goal of getting rid of that completely. With this change, version number is generated during install and embedded into `__version__` which is then imported by root level `__init__`. From there, it is used by other parts of the codebase when needed. Generated `__version__` file is ignored and not tracked by git to prevent unnecessary 'changes' messages and accidental commits of that file.
* Modify the generated CLI script by monkey patchingGökçen Nurlu2018-01-311-0/+37
| | | | | | | This change monkey patches setuptools' code generation functionality, so that pkg_resources won't be imported in the generated file. Fixes #172
* setup.py: Removing explicitly set version, we use setuptools_scm for this.Tristan Van Berkom2018-01-031-1/+0
|
* Remove unused importsGökçen Nurlu2017-12-071-2/+0
|
* setup.py: Pinning coverage at 4.4.0 instead of 4.2Tristan Van Berkom2017-11-251-1/+1
| | | | | | Our problem is with 4.4.2; and 4.2 lacks some features and fails to collect all of the coverage from sub processes, causing our reports to drop by 10%.
* setup.py: Add pytest-xdist dependencyJürg Billeter2017-11-221-0/+2
| | | | | | This allows running tests in parallel: ./setup.py test --addopts "-n auto"
* setup.py: Pinning coverage down to version 4.2Tristan Van Berkom2017-11-211-1/+3
| | | | | | | Seeing random crashes with 4.4.2, these are solved by simply using version 4.2. Need to investigate and report proper bug to upstream for this.
* setup.py: Added jinja2 dependencyTristan Van Berkom2017-10-081-1/+2
|
* setup.py: Use env var instead of --install-option for the receiver installTristan Van Berkom2017-10-011-27/+11
| | | | | Fixes the previous commits which attempt to allow optionally only installing bst-artifact-receive, which doesnt work, because pip.
* setup.py: Added --artifact-receiver-only install optionTristan Van Berkom2017-09-291-37/+83
| | | | | | A convenience to install `bst-artifact-receive` on an artifact server that does not have the ostree and bubblewrap requirements to install the main `bst` program.
* setup.py: Make setup.py work on non-linuxcross_platformTristan Maat2017-09-281-25/+29
|
* Implement tarcacheTristan Maat2017-09-281-1/+1
|
* Fork and embed fusepySam Thursfield2017-09-271-2/+1
| | | | | | | | | | | | | | | 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).
* Specify the minimum required version of pytestMathieu Bridon2017-09-201-1/+1
| | | | | | | | A previous change introduced the usage of pytest.param to our test suite in commit 7aba0bfc906409073c4d246ec009a8622551726a. This was only added to pytest 3.1.0, and the tests can't work with older versions.
* setup.{cfg,py}: Bring back BST_TEST_SUITE env variableTristan Van Berkom2017-09-051-0/+1
| | | | Turns out we do need this in some corner cases
* plugin.py: Removed special case for test casesTristan Van Berkom2017-09-031-1/+0
| | | | | | | 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).
* buildstream/data/bst: Adding a bash completion scriptlet.Tristan Van Berkom2017-08-281-1/+17
| | | | | Currently this gets installed at ${prefix}/share/bash-completion/completions but this is not exactly correct.
* setup.py: Catch exception with OSTree < 2017.4Jürg Billeter2017-08-101-5/+8
| | | | Fixes #58
* setup.py: Hard require OSTree >= 2017.8Tristan Van Berkom2017-08-011-15/+13
|
* _artifactcache/pushreceive.py: Our local copy of ostree-pushTristan Van Berkom2017-07-101-0/+1
| | | | Added entry point for running `bst-artifact-receive`
* Removing ostree-pull-ssh and ostree-pushTristan Van Berkom2017-07-091-2/+1
| | | | Including changes in _site.py and setup.py
* Add script templatesTristan Maat2017-06-281-1/+2
|
* _ostree.py: Add SSH artifact fetch supportJürg Billeter2017-06-271-1/+1
|
* _ostree.py: Add SSH artifact push supportJürg Billeter2017-06-271-1/+2
|
* setup.py: Added comment about OSTree.YEAR_VERSION & OSTree.RELEASE_VERSIONTristan Van Berkom2017-06-151-0/+7
| | | | We can start using those to assert the version >= 2017.4
* Added fusepy dependency to setup.pyTristan Van Berkom2017-06-121-1/+2
|
* setup.py: Remove the old 'build-stream' entry pointTristan Van Berkom2017-05-271-1/+0
| | | | Now you can only invoke BuildStream with the `bst` command
* Make logging go to stdout when the test suite is being run in CIJonathan Maw2017-05-251-0/+1
|
* setup.py: Use setuptools_scm pluginTristan Van Berkom2017-05-081-1/+2
| | | | | | | | | | This plugin automatically encodes git versioning information into the package version string so that it shows up in `bst --version` This versioning information is encoded into source distributions as well, so that when installing from a source distribution without the git repository the precise VCS provenance is still encoded into the version.
* Install man pages in ${prefix}/share/man/man1Tristan Van Berkom2017-04-131-1/+1
| | | | Instead of ${prefix}/man/man1, share/man/man1 is more correct.
* Adding man pages to distributionTristan Van Berkom2017-04-131-0/+22
| | | | | | | | | | Man pages are automatically generated but unfortunately committed to the repository, this should be fixed by integrating the man page generation as a part of the build step, but this seems to be very difficult and is not well documented at all. Tip: The man_pages module of click_man implements a distutils.core.Command for generating man pages, this command should be run as a part of setup.py
* setup.py: BuildStream now depends on python 3.4Tristan Van Berkom2017-04-081-2/+2
| | | | | | It was now tested on 3.4, after a few changes it seems to work well with 3.4, backing down the version requirement as 3.4 is more widely available in today's distros.
* setup.py: Removing the xdg dependencyTristan Van Berkom2017-03-211-1/+0
|
* context.py: Now using the XDG Base Directory specTristan Van Berkom2017-03-201-0/+1
| | | | | | | | | | | | | | o Attempt to load user configuration from ${XDG_CONFIG_HOME}/buildstream.conf if one exists, only if not overridden on the command line o Set the XDG Base Directory values at initialization time o Allow environment vars to be specified in paths o userconfig.yaml: Default paths now use XDG_CACHE_HOME instead of ~/buildstream o Removed the deploydir and ccache dir as we're not using those, we'll re-add those configs if they become relevant.
* setup.py: Added setuptools as install requirementTristan Van Berkom2017-03-081-1/+2
| | | | | | This is redundant in cases where setuptools is used to install, but is pedantically correct since we use setuptools in BuildStream to detect and print the package version.
* Restructuring, moved frontend related files to _frontend/ submoduleTristan Van Berkom2017-03-071-2/+2
| | | | | Probably widget.py could be split up and cleaned up some more, but at least this puts the frontend out of the way.
* setup.py: BuildStream now requires blessings.Tristan Van Berkom2017-03-071-1/+2
| | | | | | Blessings gives us some code for positioning the cursor on terminals which support that (almost all terminals on linux), this lets us print some things always at the bottom of the output.
View Lorry Controller Status