Pictures
Image to Gif
Dependencies
pillow
Ipython
pathlib
Example :
>>from pictures import imgtogif
>>imgtogif.convert(path="./",file_name="mine.gif")
Default parameters values:
convert (path="./",file_name="imgtogif.gif",to="./",
img_format="all",duration=400,loop=0,
number_sort="n",string_sort="n",
gif_width=510,gif_height=310 )
Parameters:
path:
Path to the source of the image files
file_name:
File name for the gif to be saved
to:
Destination of the gif file
img_format:
In which format of images are need to be converted to gif
Formats are : png , jpg , jpeg or all
duration:
Duration of the gif
loop:
0 for gif to play again and again
1 for play 1 time
number_sort:
[Sorting image files numerically]
Example:
images=[2.png,34.png,1.png]
if number sort is yes means:
this will be sorted as [1.png,2.png,34.png]
and gif will be created
string_sort:
[sorting image files alphabetically]
Example:
images=[c.png,b.png,a.png]
if string sort is yes means:
this will be sorted as [a.png,b.png,c.png]
and gif will be created
gif_width:
width of the gif
gif_height:
Height of the gif```
Metadata
Release files for pictures 0.7
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 | |
|---|---|---|---|---|
| pictures-0.7.tar.gz | 765.5 kB | Without provenance | Details |
Release files / pictures-0.7.tar.gz
| Download URL | pictures-0.7.tar.gz |
|---|---|
| Size | 765.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1aa44aec8d8a4c15bec61baa57b11946724e3935a6af1167d9a72784af90fa64
|
|
BLAKE2b-256 checksum How to use checksums |
8b725acec6dd54d846f6a577d5a395a3b29036861de0c649664c8ffa41e232bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.8
|
Security for pictures 0.7
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.