semvec/pypi-packages huggingface dataset:
libCAF 0.1.0b0
Parser and Builder classes related to Apple's Core Audio Format (.caf).

# Core Audio Format Parser

[![PyPI](https://img.shields.io/pypi/v/libCAF.svg)][pypi status]
[![Status](https://img.shields.io/pypi/status/libCAF.svg)][pypi status]
[![Python Version](https://img.shields.io/pypi/pyversions/libCAF)][pypi status]
[![License](https://img.shields.io/pypi/l/libCAF)][license]

[![Black](https://img.shields.io/badge/code%20style-black-000000.svg)][black]
[![Build and Deploy Sphinx Documentation](https://github.com/JustHexData/CAF/actions/workflows/python-sphinx.yml/badge.svg)](https://justhexdata.github.io/CAF)


[pypi status]: https://pypi.org/project/libCAF/
[black]: https://github.com/psf/black

Parser and Builder classes related to Apple's Core Audio Format (.caf).

_**NOTE: This is a work in progress**_

## Core Audio Format

> _"Apple’s Core Audio Format (CAF) is a file format for storing and transporting digital audio data. It simplifies the management and manipulation of many types of audio data without the file-size limitations of other audio file formats."_

* [MusicAudio/Reference/CAFSpec](https://developer.apple.com/library/archive/documentation/MusicAudio/Reference/CAFSpec/CAF_intro/CAF_intro.html)

## Installation

You can install _libCAF_ via [pip] from [PyPI]:

```console
$ pip install libcaf
```

and to build the docs you need `make` to be installed:
```console
$ pip install -r docs/requirements.txt
$ cd docs && make html
```

## Usage

The python package provided within this repository supports parsing ``caf`` archives into an object model. More detailed information about the implementation and fields of each class, please refer to the documentation available on [Github-Pages].

### Parsing CAF Files

```python
>>> from libcaf import *
>>> data = caf.parse_file("file.caf")
>>> data
caf_t(m_header=caf__header_t(m_file_type=b'caff', m_file_version=1, m_file_flags=0), ...
```

## Contributing

Contributions are very welcome.
To learn more, see the [Contributor Guide].

## License

Distributed under the terms of the [MIT license][license],
_Core Audio Format Parser_ is free and open source software.

## Issues

If you encounter any problems,
please [file an issue] along with a detailed description.

[pypi]: https://pypi.org/
[file an issue]: https://github.com/JustHexData/CAF/issues
[pip]: https://pip.pypa.io/


<!-- github-only -->

[Github-Pages]: https://justhexdata.github.io/CAF
[license]: https://github.com/JustHexData/CAF/blob/main/LICENSE
[contributor guide]: https://github.com/JustHexData/blob/main/CONTRIBUTING.md
cloudsculpter 0.0.2
A package to deploy cloudformation resources with natural language instructions, automatically healing failed deployments with OpenAI troubleshooting
Requires Python: >=3.6

# DevOps Guru
DevOps Guru is a python package that provides a simple interface for creating and deploying cloudformation templates to AWS.

## Installation
```python
pip install devops-guru
```

## Usage
```python
devops-guru --help
```

## Commands
```python
devops-guru create
```

```python
devops-guru deploy
```

```python
devops-guru delete
```

```python
devops-guru list
```

```python
devops-guru update
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License
[Apache License 2.0](https://choosealicense.com/licenses/apache-2.0/)
generate-dockerignore-from-gitignore 0.1.3
.dockerignore file generator based on .gitignore file(s)

# generate-dockerignore-from-gitignore

As the name implies, this package generates a `.dockerignore` for you based on `.gitignore` rules
found in your source tree.

Why generate this file, you ask? Because there are a number of differences between
`.dockerignore` and `.gitignore` rule processing which can make it non-trivial to make
your Docker file tree match your local git tree.

Generating your `.dockerignore` file based on your configured `.gitignore` rules means you only have
to think about which files should not be distributed with your project only once. This also can
promote reproducible builds by ensuring that the only files your Docker context has access to are
those files that are tracked by your git repository.

The following differences between `.dockerignore` vs `.gitignore` processing are handled by this tool:

| behavior                                    | .gitignore            | .dockerignore             |
| ------------------------------------------- | --------------------- | ------------------------- |
| plain patterns without slashes or wildcards | ⏬️ match recursively  | ⬆️ match top-level only   |
| separate per-directory ignore files         | ✅ allowed            | ❌ not allowed            |
| local .git/info/exclude file                | ✅ included           | -                         |
| global core.excludesFile file               | ✅ included           | -                         |

The code's handling of these behavioral differences is [tested](test/cases) using actual
git and Docker calls, followed by validation that the resultant git source trees are
equal to the Docker build contexts.

References:
- https://git-scm.com/docs/gitignore
- https://docs.docker.com/engine/reference/builder/#dockerignore-file

## Installation

```
pip install generate-dockerignore-from-gitignore
```

## Usage

<!--[[[cog
  os.environ['COLUMNS'] = '100'
  print('```')
  print(sp.check_output(['generate-dockerignore', '--help'], text=True, stderr=sp.STDOUT))
  print('```')
]]]-->
```
usage: generate-dockerignore [-h] [-C DOCKER_ROOT] [-v] [-o OUTPUT] [PATH ...]

.dockerignore file generator based on .gitignore file(s)

positional arguments:
  PATH                  gitignore file(s), or directories under git source control (which will be
                        searched for **/.gitignore).

options:
  -h, --help            show this help message and exit
  -C DOCKER_ROOT, --docker-root DOCKER_ROOT
                        Docker context directory to chdir into before continuing
  -v, --verbose         Output per-file logging to stderr
  -o OUTPUT, --output OUTPUT
                        File path for generated .dockerignore rule output, or - for stdout
                        (default: .dockerignore)

```
<!--[[[end]]] (checksum: 66f0bbbfd94d6d5536e726e18f537585)-->