taskflow/.gitignore

*.py[cod]

# C extensions
*.so

# Packages
*.egg
*.eggs
*.egg-info
dist
build
eggs
parts
bin
var
sdist
develop-eggs
.installed.cfg
lib
lib64

# Installer logs
pip-log.txt

# Unit test / coverage reports
.coverage*
.diagram-tools/*
.tox
nosetests.xml
.venv
cover
.stestr/
htmlcov

# Translations
*.mo

# Mr Developer
.mr.developer.cfg
.project
.pydevproject
.settings

# DS_STORE
.DS_Store

# Sqlite databases
*.sqlite

# Modified Files
*.swp

# PBR
build
AUTHORS
ChangeLog

# doc
doc/build/

.idea
env

# files created by releasenotes build
RELEASENOTES.rst
releasenotes/notes/reno.cache
releasenotes/build
Fixing .py in .gitignore 2013-05-28 16:13:39 -05:00			`*.py[cod]`
Initial commit 2013-05-07 10:45:34 -07:00
			`# C extensions`
			`*.so`

			`# Packages`
			`*.egg`
Uncap jsonschema We have jsonschema capped at a fairly old version. Other than some specific releases, it looks like keeping it below 3.0 was added in I943fd68b9fab3bce1764305a5058df5339470757 without really any explanation why. In order to update to a 3.x release we need to: 1. Remove the cap from global-requirements.txt (see Depends-On), leaving upper-constraints.txt at a 2.x release 2. Remove the cap from all consumers (this change) 3. Release a new version of consumers that are published to pypi 4. Update upper-constraints.txt with those new releases 5. Update jsonschema in upper-constraints.txt to a 3.X release (See: https://review.openstack.org/649789) 6. Test consumers with the change from 5. 7. [Optional] fix issues in consumers that arise from 6. 8. Merge the change from 5. Also includes squashed commit: Raise lower constraint of psycopg2 Versions prior to 3.7 did not support postgresql version numbering starting with postgresql 10, causing setup failures. This raises the lower-constraint to the first version that contained the fix [0] to support that. With the change in global requirements for jsonschema, requirements check fails on raising psycopg2, but we need that raised in order for the jsonschema version to be raised. [0] https://github.com/psycopg/psycopg2/pull/504 Also required updating networkx constraints to match current g-r. Change-Id: Ifd0f0586f945d1da4dd597ae7b4514117cd49f57 Co-Authored-by: Sean McGinnis <sean.mcginnis@gmail.com> Depends-On: https://review.openstack.org/649669 2019-04-09 08:44:44 -05:00			`*.eggs`
Initial commit 2013-05-07 10:45:34 -07:00			`*.egg-info`
			`dist`
			`build`
			`eggs`
			`parts`
			`bin`
			`var`
			`sdist`
			`develop-eggs`
			`.installed.cfg`
			`lib`
			`lib64`

			`# Installer logs`
			`pip-log.txt`

			`# Unit test / coverage reports`
.gitignore update After running tox some extra files were created. TrivialFix Change-Id: I3e5a38abf49cf3b246de436f78137b23154d8101 2015-07-29 00:04:36 +03:00			`.coverage*`
			`.diagram-tools/*`
Initial commit 2013-05-07 10:45:34 -07:00			`.tox`
			`nosetests.xml`
Add .settings and .venv into .gitignore Change-Id: I02255b9cea996dc88df607a34ee5f0b1f38a33cb 2013-06-05 22:35:32 -04:00			`.venv`
Coverage calculation improvements - add .coveragerc to configure coverage calculations and omissions; - add python 2.x specific test requirements to coverage tox env; - update .gitignore. Change-Id: Idc35e4f18ec297506576f09e468ab34e8704c0b1 2013-11-22 11:25:03 +04:00			`cover`
Switch to use stestr for unit test According to Openstack summit session [1], stestr is maintained project to which all Openstack projects should migrate. So we should switch to stestr. [1] https://etherpad.openstack.org/p/YVR-python-pti Depends-On: https://review.openstack.org/#/c/589728/ Change-Id: I943a73e22eb23bd52c3a96e75c98b88665474e67 2018-07-20 13:38:36 +07:00			`.stestr/`
Added htmlcov folder to .gitignore Change-Id: Iea321a98929285af7bde5e013d4fdd46040da5c2 2014-01-06 17:07:39 +02:00			`htmlcov`
Initial commit 2013-05-07 10:45:34 -07:00
			`# Translations`
			`*.mo`

			`# Mr Developer`
			`.mr.developer.cfg`
			`.project`
			`.pydevproject`
Add .settings and .venv into .gitignore Change-Id: I02255b9cea996dc88df607a34ee5f0b1f38a33cb 2013-06-05 22:35:32 -04:00			`.settings`
Update db api test 2013-05-28 16:11:46 -05:00
			`# DS_STORE`
			`.DS_Store`
Fixing .py in .gitignore 2013-05-28 16:13:39 -05:00
Use oslo's sqlalchemy layer Bring over the sqlalchemy layer + dependents that oslo provides so that we can use it in a dependent commit to replace pieces of our own mini sqlalchemy layer (that was derived from oslos) Change-Id: Ifda2fd5c5b8eb1d71a4cfce2a2e0046a23010270 2013-08-15 15:05:05 -07:00			`# Sqlite databases`
			`*.sqlite`

Fixing .py in .gitignore 2013-05-28 16:13:39 -05:00			`# Modified Files`
			`*.swp`
Move to using pbr. The new way to build packages and perform setuptools interactions seems to be via the pbr library so to play well with others, use said library. Change-Id: I519503fdf59457dc554870b8e6ff61613ab30d11 2013-07-07 21:22:34 -07:00
			`# PBR`
			`build`
			`AUTHORS`
			`ChangeLog`
Task progress Add update progress method to base task class Implements blueprint: task-progress Change-Id: Id7d554ce6c31778f1f1a084a3b268257e66a5fea 2013-09-12 22:15:56 +04:00
Ignore doc build files Change-Id: I064eaa43ed603143d1cbb28669c8b0cd1e43a252 2014-01-03 11:50:32 -05:00			`# doc`
Fix the sphinx build path in .gitignore file Change-Id: I80b930c164f5453204d7aea0954d7a98d90e3a51 2015-09-22 22:44:33 +05:30			`doc/build/`
Ignore doc build files Change-Id: I064eaa43ed603143d1cbb28669c8b0cd1e43a252 2014-01-03 11:50:32 -05:00
Task progress Add update progress method to base task class Implements blueprint: task-progress Change-Id: Id7d554ce6c31778f1f1a084a3b268257e66a5fea 2013-09-12 22:15:56 +04:00			`.idea`
			`env`
Add reno for release notes management The release management team have indicated this is their preferred way to collect release notes in future. Change-Id: I98383e53b1d78b0bb01b16642d8b8a1b69ad3769 Signed-off-by: Chuck Short <chuck.short@canonical.com> 2016-10-25 20:33:55 -04:00
			`# files created by releasenotes build`
ignore reno generated artifacts Change-Id: Iaf8370e62918bb5a83222f13796a923a6d157c0f 2020-09-08 14:34:51 +02:00			`RELEASENOTES.rst`
			`releasenotes/notes/reno.cache`
Add reno for release notes management The release management team have indicated this is their preferred way to collect release notes in future. Change-Id: I98383e53b1d78b0bb01b16642d8b8a1b69ad3769 Signed-off-by: Chuck Short <chuck.short@canonical.com> 2016-10-25 20:33:55 -04:00			`releasenotes/build`