|
1 | 1 | [](http://www.vfxplatform.com/)
|
2 |
| -[](https://www.python.org/) |
3 |
| -[](http://developer.shotgunsoftware.com/python-api) |
| 2 | +[](https://www.python.org/) |
| 3 | +[](http://developer.shotgridsoftware.com/python-api) |
4 | 4 | [](http://travis-ci.org/shotgunsoftware/python-api)
|
5 | 5 | [](https://ci.appveyor.com/project/jfboismenu/python-api/branch/master)
|
7 | 7 | [](https://coveralls.io/github/shotgunsoftware/python-api?branch=master)
|
8 | 8 |
|
9 | 9 | # Shotgun Python API
|
10 | 10 |
|
11 |
| -Shotgun provides a simple Python-based API for accessing Shotgun and integrating with other tools. This is the official API that is maintained by Shotgun Software ( [email protected]) |
| 11 | +ShotGrid provides a simple Python-based API for accessing ShotGrid and integrating with other tools. This is the official API that is maintained by ShotGrid Software ( [email protected]) |
12 | 12 |
|
13 | 13 | The latest version can always be found at http://github.com/shotgunsoftware/python-api
|
14 | 14 |
|
15 | 15 | ## Minimum Requirements
|
16 | 16 |
|
17 |
| -* Shotgun server v2.4.12+. |
18 |
| -* Python v2.6 - v2.7 or v3.7 |
| 17 | +* ShotGrid server v2.4.12+. |
| 18 | +* Python v2.7 or v3.7 |
19 | 19 |
|
20 | 20 | ## Documentation
|
21 |
| -Tutorials and detailed documentation about the Python API are available at http://developer.shotgunsoftware.com/python-api). |
| 21 | +Tutorials and detailed documentation about the Python API are available at http://developer.shotgridsoftware.com/python-api). |
22 | 22 |
|
23 | 23 | Some useful direct links:
|
24 | 24 |
|
25 |
| -* [Installing](http://developer.shotgunsoftware.com/python-api/installation.html) |
26 |
| -* [Tutorials](http://developer.shotgunsoftware.com/python-api/cookbook/tutorials.html) |
27 |
| -* [API Reference](http://developer.shotgunsoftware.com/python-api/reference.html) |
28 |
| -* [Data Types](http://developer.shotgunsoftware.com/python-api/reference.html#data-types) |
29 |
| -* [Filter Syntax](http://developer.shotgunsoftware.com/python-api/reference.html#filter-syntax) |
| 25 | +* [Installing](http://developer.shotgridsoftware.com/python-api/installation.html) |
| 26 | +* [Tutorials](http://developer.shotgridsoftware.com/python-api/cookbook/tutorials.html) |
| 27 | +* [API Reference](http://developer.shotgridsoftware.com/python-api/reference.html) |
| 28 | +* [Data Types](http://developer.shotgridsoftware.com/python-api/reference.html#data-types) |
| 29 | +* [Filter Syntax](http://developer.shotgridsoftware.com/python-api/reference.html#filter-syntax) |
30 | 30 |
|
31 | 31 | ## Changelog
|
32 | 32 |
|
33 |
| -You can see the [full history of the Python API on the documentation site](http://developer.shotgunsoftware.com/python-api/changelog.html). |
| 33 | +You can see the [full history of the Python API on the documentation site](http://developer.shotgridsoftware.com/python-api/changelog.html). |
34 | 34 |
|
35 | 35 | ## Updating HTTPLib2
|
36 | 36 |
|
@@ -108,8 +108,8 @@ Integration and unit tests are provided.
|
108 | 108 | - A `tests/config` file (you can copy an example from `tests/example_config`).
|
109 | 109 | - Tests can be run individually like this: `nosetests --config="nose.cfg" tests/test_client.py`
|
110 | 110 | - Make sure to not forget the `--config="nose.cfg"` option. This option tells nose to use our config file. This will exclude python 2- and 3-specific files in the `/lib` directory, preventing a failure from being reported by nose for compilation due to incompatible syntax in those files.
|
111 |
| -- `test_client` and `tests_unit` use mock server interaction and do not require a Shotgun instance to be available (no modifications to `tests/config` are necessary). |
112 |
| -- `test_api` and `test_api_long` *do* require a Shotgun instance, with a script key available for the tests. The server and script user values must be supplied in the `tests/config` file. The tests will add test data to your server based on information in your config. This data will be manipulated by the tests, and should not be used for other purposes. |
| 111 | +- `test_client` and `tests_unit` use mock server interaction and do not require a ShotGrid instance to be available (no modifications to `tests/config` are necessary). |
| 112 | +- `test_api` and `test_api_long` *do* require a ShotGrid instance, with a script key available for the tests. The server and script user values must be supplied in the `tests/config` file. The tests will add test data to your server based on information in your config. This data will be manipulated by the tests, and should not be used for other purposes. |
113 | 113 | - To run all of the tests, use the shell script `run-tests`.
|
114 | 114 |
|
115 | 115 | ## Release process
|
|
0 commit comments