semvec/pypi-packages huggingface dataset:
commonsApi 1.0.3
This is a package to automate apis in a simple way by using common reusable functions
License: MIT
Keywords: api automation,api testing,api commons,python api,api automation using python

# API Testing Commons

- This is a package to automate apis in a simple way by using common reusable functions.

- This module containes the major reusable functions which can be imported and accessed directly which will reduce the time and code redundancy.

## Installation
----------------

```
pip install commonsApi
```

## Methods available
---------------------
- > get_api(endpoint, header)
- > post_api(endpoint, request_payload, header)
- > put_api(endpoint, request_payload, header)
- > delete_api(endpoint, data, header)
- > patch_api(endpoint, request_payload, header)
- > validate_status_code(response, expected_status)
- > validate_schema(response, expected_schema)
- > validate_strings(actual_message, expected_message)
- > value_present(response, expected_value)
- > is_json(response)


## Sample code

```python
import commonsApi
url = "https://api.postcodes.io/random/postcodes"
header = {}
resp = commonsApi.get_api(url, header)
print(resp.json())
```

## Raise if any issues/changes needed
 Please raise an issue [here](https://github.com/ManikandanRajendran/python-package-for-api-testing/issues) if anything
readthedocs-custom-steps 0.6.2
A hack to run custom steps when building documentation on Read the Docs.
License: MIT
Requires Python: >=3.5.0,<4.0.0

# readthedocs-custom-steps

A hack to run custom steps when building documentation on Read the Docs.

> __Important__: This module should not be installed outside of a Read the Docs build environment.
> It will rename your Python executable and install a substitute. It does not currently provide an
> automated way to revert this change.

## Installation

This package must be installed only during the Read the Docs build process, for example as an extra
requirement or through an additional requirements file.

__Example:__

```yaml
# .readthedocs.yml
version: 2
mkdocs:
  configuration: "docs/mkdocs.yml"
python:
  version: "3.7"
  install:
  - path: "."
    extra_requirements: [ "rtd" ]
```

## How to use this?

RtdCS overrides your `python` installation with a Bash script that dispatches the
execution of custom steps upon invokation of `python -m mkdocs` or `python -m sphinx`.
The commands to run are either defined in `pyproject.toml` or in a file called
`.readthedocs-custom-steps.yml` (deprecated).

__Example:__

<table>
   <tr>
      <th><code>pyproject.toml</code></th>
      <th><code>.readthedocs-custom-steps.yml</code></th>
   </tr>
   <tr>
      <td>

```toml
[tool.readthedocs-custom-steps]
script = """
bash .scripts/generate-changelog.sh >docs/changelog.md
python -m "$@"
"""
```

</td>
      <td>

```yml
steps:
- bash .scripts/generate-changelog.sh >docs/changelog.md
- python -m "$@"
```

</td>
   </tr>
</table>


Here, `$@` contains the arguments after `python -m` in the Read the Docs build step, for example:

* `mkdocs build --clean --site-dir _site/html --config-file mkdocs.yml`
* `sphinx -T -b html -d _build/doctrees -D language=en . _build/html`

An infinite recursion of this script invoking itself in the example above is prevented automatically
with the `RTD_CUSTOM_ENTRY` environment variable that is set before your script/steps are executed.

## Configuration

If a `pyproject.toml` exists and it contains a `[tool.readthedocs-custom-steps]` section, the configuration
will be read from there. Otherwise, a file called `.readthedocs-custom-steps.yml` must exist and will be
searched for in the following locations:

1. `.readthedocs-custom-steps.yml`
2. `docs/.readthedocs-custom-steps.yml`
3. Relative to any directories from which requirements files are specified in the `.readthedocs.yml` file
   under the `$.python.install[*].requirements` configuration option.

## Environment

In addition to passing the original arguments to the custom steps, RtdCS provides `PYTHON` environment variables
as detected from the `~/.pyenv/shims` folder in the RTD build environment. (e.g. if there is a shim `python3.6` and
`python3.7`, there'll be `PYTHON`, `PYTHON36` and `PYTHON37` environment variables, and `PYTHON` will point to 3.7).

---

<p align="center">Copyright &copy; 2022 Niklas Rosenstein</p>