semvec/pypi-packages huggingface dataset:
piexif 1.1.3
To simplify exif manipulations with python. Writing, reading, and more...
License: MIT
Requires Python: >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*
Keywords: exif,jpeg

Piexif
======

|Build Status| |Windows Build| |Coverage Status| |docs|


To simplify exif manipulations with Python. Writing, reading, and more... Piexif is pure Python. To everywhere with Python.


Document: http://piexif.readthedocs.org/en/latest/

Online demo: http://piexif-demo.appspot.com/demo

Install
-------

'easy_install'::

    $ easy_install piexif

or 'pip'::

    $ pip install piexif

or download .zip, extract it. Put 'piexif' directory into your environment.

Why Choose Piexif
-----------------

- Pure Python. So, it runs everywhere where Python runs.
- Easy exif manipulations. Read, write, remove...
- Documented. http://piexif.readthedocs.org/en/latest/

How to Use
----------

There are only just five functions.

- *load(filename)* - Get exif data as *dict*.
- *dump(exif_dict)* - Get exif as *bytes*.
- *insert(exif_bytes, filename)* - Insert exif into JPEG, or WebP.
- *remove(filename)* - Remove exif from JPEG, or WebP.
- *transplant(filename, filename)* - Transplant exif from JPEG to JPEG.

Example
-------

::

    exif_dict = piexif.load("foo1.jpg")
    for ifd in ("0th", "Exif", "GPS", "1st"):
        for tag in exif_dict[ifd]:
            print(piexif.TAGS[ifd][tag]["name"], exif_dict[ifd][tag])

With PIL(Pillow)
----------------

::

    from PIL import Image
    import piexif

    im = Image.open(filename)
    exif_dict = piexif.load(im.info["exif"])
    # process im and exif_dict...
    w, h = im.size
    exif_dict["0th"][piexif.ImageIFD.XResolution] = (w, 1)
    exif_dict["0th"][piexif.ImageIFD.YResolution] = (h, 1)
    exif_bytes = piexif.dump(exif_dict)
    im.save(new_file, "jpeg", exif=exif_bytes)

Environment
-----------

Tested on Python 2.7, 3.5+ and PyPy3. Piexif would run even on IronPython. Piexif is OS independent and can run on Google App Engine.

License
-------

This software is released under the MIT license, see LICENSE.txt.

.. |Build Status| image:: https://api.travis-ci.org/hMatoba/Piexif.svg?branch=master
   :target: https://travis-ci.org/hMatoba/Piexif
.. |Windows Build| image:: https://ci.appveyor.com/api/projects/status/github/hMatoba/Piexif?branch=master&svg=true
   :target: https://ci.appveyor.com/project/hMatoba/piexif
.. |Coverage Status| image:: https://coveralls.io/repos/hMatoba/Piexif/badge.svg?branch=master
   :target: https://coveralls.io/r/hMatoba/Piexif?branch=master
.. |docs| image:: https://readthedocs.org/projects/piexif/badge/?version=latest
   :target: https://readthedocs.org/projects/piexif/
blockpype 1.0.0a1
Breaks apart input stream into blocks and pipes each block into newly spawned processes
License: MIT
Requires Python: ~=3.6
Keywords: pipe split buffer block streaming

# Blockpype

Breaks apart input stream into blocks and pipes each block into newly spawned processes

## Installing

```
pip install git+https://github.com/kfzteile24/blockpype.git
```

## Testing
Clone the repository and run visual tests that display each started PID and their output:
* `test/by-byte.sh` - should break apart in the middle of the 2-byte character
* `test/by-char.sh` - should break apart in the middle of some numbers
* `test/by-line.sh` - should break apart nicely line by line

## Usage
```
cat content.txt | blockpype -l 10 other-program --arg-for-program --another-arg "argument value"
```

It will cut `content.txt` into blocks of 10 lines, and for each block, a process will be started using the command:

```
other-program --arg-for-program --another-arg "argument value"
```

and the contents of the block will be served to *stdin*

## What's it for?

Whenever you want to break apart a large stream when the `other-program` consumer stores it into memory until EOF, and you don't have enough memory for it.

Similar to `split --filter "other-program --arg-for-program --another-arg \"argument value\""` except less clunky, `other-program` gets launched from current `pwd` with the current user, and with the current environment variables.
crlint 0.1.2
The project copyright linter
License: MIT
Requires Python: >=3.4

# Project copyright linter
A small utility to maintain the copyright status of a project in the correct state.

## Copyright format
* Python copyright format:
```python
# Copyright (c) 20XX Celadon Development LLC, All rights reserved.
# Author Name Surname <name.surname@celadon.ae>
```
* JavaScript copyright format:
```js
// Copyright (c) 20XX Celadon Development LLC, All rights reserved.
// Author Name Surname <name.surname@celadon.ae>
```

## Installation
* install package via pip toolkit: `pip install crtool`
* configure utility use one of [two available methods](##configuration)
* run the project copyright linting: `crtool`

## Configuration
Configuration settings are applied in two ways: by `setup.cfg` file or `.crlintrc` file.
The `setup.cfg` file has more high priority.
To set an exclusion pattern to ignore some file formats, use a unix pattern written in one of the files you selected.

* configuration utility in the `setup.cfg` file must have such format:
```
[crlint]
patterns=*.json, *.txt
```
* configuration utility in the `.crlintrc` file must have such format:
```
[ignore]
patterns=*.json, *.txt
```

## Integration with Bitbucket CI:
Add such step in your `bitbucket-pipelines.yml` file to run checking a project copyright:
```yml
pipelines:
  default:
    - step:
        name: Linting copyright
        image: python:3.7.2
        script:
          - pip install crtool
          - crlint
```

## Update pip package
* Login to the PiPy repository
* Increase version in the setup file
* Create a python package dist
* Update package on the PyPi repository
```bash
# Create a package dist.
python setup.py sdist bdist_wheel

# Upload package to repository.
pip install twine
twine upload -u $CT_PYPI_USERNAME -p $CT_PYPI_PASSWORD  dist/*
```

## Development
Setup git hook to linting the project before commit.
```bash
chmod a+x pre-commit && cp pre-commit .git/hooks
```

To run the test and verify the code, follow the commands below:
```bash
# To run the project linting.
flake8 crlint tests

# To run the project testing.
python -m coverage run -m unittest discover tests/
python -m coverage report -m
```