gignore
Overview
gignore Get .gitignore files from github/gitignore.
CLI
gignore comes with a Command Line Interface and works just like any other unix based command line application.
The output of gignore will be echo out to command line and can be simply pipe to other applications.
Usage
CLI
$ gignore Python # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] ....
Backend
>>> from gignore import Gignore
>>> gig = Gignore('Python')
>>> gig.get_gitignore_file()
>>> print(gig.get_file_content())
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
# C extensions
*.so
# Distribution / packaging
.Python
# ....
>>>
Supported Python Versions
gignore currently can be run on multiple python versions:
Python 2 (2.7)
Python 3 (3.2, 3.3, 3.4)
PyPy
Installation
gignore is available on pypi
http://pypi.python.org/pypi/gignore
So easily install it by pip
$ pip install gignore
Or by easy_install
$ easy_install gignore
Another way is by cloning python-gignore’s git repo
$ git clone git://github.com/Alir3z4/python-gignore.git
Then install it by running:
$ python setup.py install
License
gignore is distributed under the terms of BSD license.
Metadata
Release files for gignore 2014.10.28
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gignore-2014.10.28.tar.gz | 4.7 kB | Without provenance | Details for gignore-2014.10.28.tar.gz |
Release files / gignore-2014.10.28.tar.gz
| Download URL | gignore-2014.10.28.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0daca3a9eb425bd0beebe7c9fdfd67a4f0f25549a7dfec2286abceb251c21cc8
|
|
BLAKE2b-256 checksum How to use checksums |
955ecb00de06f0429cd7bae8f05c5d4f7609cedd664b846df614e8df28756eff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gignore 2014.10.28
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.