delta/buildstream.git/doc/source, branch chandan/python3.8 gitlab.com: buildstream/buildstream.git Drop support for `setup.py test` 2019-12-23T09:33:21+00:00 Chandan Singh chandan@chandansingh.net 2019-12-06T15:14:32+00:00 8a9e3cb9f71e3cac683af1ff667e4de8ef802132 Drop support for running tests via `setup.py test`, that is considered deprecated. `tox` is our primary frontend for running tests, so this change ensures that we don't have to support multiple ways of running tests. For testing against a specific installation environment, `tox` is not quite practical. But in these cases, one can run `pytest` directly. So, there is no need for this additional indirection. This was discussed in the following mailing list thread: https://mail.gnome.org/archives/buildstream-list/2019-December/msg00006.html. 
Drop support for running tests via `setup.py test`, that is considered
deprecated. `tox` is our primary frontend for running tests, so this
change ensures that we don't have to support multiple ways of running
tests.

For testing against a specific installation environment, `tox` is not
quite practical. But in these cases, one can run `pytest` directly. So,
there is no need for this additional indirection.

This was discussed in the following mailing list thread:
https://mail.gnome.org/archives/buildstream-list/2019-December/msg00006.html.
doc/coding_guidelines: Drop section about line lengths 2019-11-27T19:56:13+00:00 Chandan Singh csingh43@bloomberg.net 2019-11-26T19:13:05+00:00 96b3975e7abac91522d8d064a2ea7e147f96295e Since we format our code using Black, contributors don't have to think about line lengths themselves. In fact, Black is going to rewrite the files anyway so it's not even possible to make a judgement call in most cases. 
Since we format our code using Black, contributors don't have to think
about line lengths themselves. In fact, Black is going to rewrite the
files anyway so it's not even possible to make a judgement call in most
cases.
doc: Add glossary of common terms 2019-11-27T18:03:59+00:00 Chandan Singh chandan@chandansingh.net 2019-11-11T21:04:36+00:00 8d27cf5a73454c6580954dfe539075ecbc54a785 Start a new glossary document, aimed at helping newcomers relevant links to more detailed documents. 
Start a new glossary document, aimed at helping newcomers relevant links
to more detailed documents.
doc/examples/flatpak-autotools: remove references to sdk.gnome.org 2019-11-19T19:15:26+00:00 Abderrahim Kitouni akitouni@gnome.org 2019-11-17T10:06:49+00:00 a573cce33c90cafb029e1d782af112e7a99bcfdd download from flathub instead, and update to 1.6 as flathub doesn't include 1.4 
download from flathub instead, and update to 1.6 as flathub doesn't include 1.4
Start linting doc/source/conf.py 2019-11-14T21:21:46+00:00 Chandan Singh csingh43@bloomberg.net 2019-11-12T18:03:46+00:00 6130ea6767f91f40e84c83b038f36d3d984fe3c7 Add `doc/source/conf.py` to the filelist for Black and Pylint. Previously this file was not covered by any of the linters, so this patch includes one-off sweeping changes for the formatting. To make pylint happy, we had to disable a warning about defining a variable called `copyright` since that's a built-in. It's unlikely that we will ever need the built-in `copyright()` in this module, so it seems safe to disable it. 
Add `doc/source/conf.py` to the filelist for Black and Pylint.
Previously this file was not covered by any of the linters, so this
patch includes one-off sweeping changes for the formatting.

To make pylint happy, we had to disable a warning about defining a
variable called `copyright` since that's a built-in. It's unlikely that
we will ever need the built-in `copyright()` in this module, so it seems
safe to disable it.
doc/source/hacking: Remove pycodestyle, add Black 2019-11-14T21:21:06+00:00 Chandan Singh csingh43@bloomberg.net 2019-11-11T17:17:05+00:00 91c6bb651beb0954840635a22b7b4b74fd35ac08 Now that code formatting is managed by Black, and we don't need to run `pycodestyle` separately, remove corresponding mentions from hacking documentation. Add documentation on how to run Black. Move out linting and formatting into a separate section for better readability. 
Now that code formatting is managed by Black, and we don't need to run
`pycodestyle` separately, remove corresponding mentions from hacking
documentation.

Add documentation on how to run Black.

Move out linting and formatting into a separate section for better
readability.
format_project.rst: De-obfuscate element/package differences 2019-10-25T16:28:05+00:00 Tristan Maat tristan.maat@codethink.co.uk 2019-10-25T13:49:21+00:00 798cac74a700e79ce67baed21b95e68e940d8aa6 When the package and project have the same name, it can be a little confusing what these things actually mean. This commit makes it a bit more obvious that the two can (and will often) be different. 
When the package and project have the same name, it can be a little
confusing what these things actually mean. This commit makes it a bit
more obvious that the two can (and will often) be different.
Update doc commands to use 'source fetch' 2019-10-07T15:40:48+00:00 ctolentino8 ctolentino8@bloomberg.net 2019-10-03T14:27:52+00:00 390d0387083f8f305c0d882da92314040b734c3f 






CONTRIBUTING.rst: Add UI section
2019-09-16T12:11:09+00:00

James Ennis
james.ennis@codethink.co.uk

2019-09-04T12:01:58+00:00

163a4758cfdf1c72e300fc86302a2c3da5bb17be

Now that the frontend has been mostly reworked/standardized,
this patch attempts to put our some guidelines/information in
around UI contributions.





Now that the frontend has been mostly reworked/standardized,
this patch attempts to put our some guidelines/information in
around UI contributions.







using_commands.rst: Add internal X-references
2019-09-16T10:57:25+00:00

James Ennis
james.ennis@codethink.co.uk

2019-09-04T12:00:40+00:00

4d9b595da63c24b3b5251cce47f23b2ee6cfd86b

This patch adds internal cross references for the artifact and
source commands.





This patch adds internal cross references for the artifact and
source commands.