faker_vehicle
faker_vehicle is a provider for the Faker Python package.
It provides vehicle and machinery related fake data for testing purposes:
Vehicle Make
Vehicle Model
Vehicle Make / Model
Vehicle Make / Model / Year
Vehicle Make / Model / Category
Vehicle Year
Vehicle Object (you can format)
Machine Make
Machine Model
Machine Make / Model
Machine Make / Model / Year
Machine Make / Model / Category
Machine Year
Machine Object (you can format)
Usage
Install with pip:
pip install faker_vehicleOr install with setup.py
git clone https://github.com/kennethwsmith/faker_vehicle.git
cd faker_vehicle && python setup.py installAdd the VehicleProvider to your Faker instance:
from faker import Faker
from faker_vehicle import VehicleProvider
fake = Faker()
fake.add_provider(VehicleProvider)
fake.vehicle_year_make_model()
# 2014 Volkswagen Golf
fake.vehicle_year_make_model_cat()
# 1996 Dodge Ram Wagon 1500 (Van/Minivan)
fake.vehicle_make_model()
# Volvo V40
fake.vehicle_make()
# BMW
fake.vehicle_model()
# SL
fake.vehicle_year()
# 2008
fake.vehicle_category()
# Wagon
json.dumps(fake.vehicle_object())
# {"Year": 1996, "Make": "Chrysler", "Model": "New Yorker", "Category": "Sedan"}
fake.machine_year_make_model()
# 2008 Caterpillar 5511C
fake.machine_year_make_model_cat()
# 2008 Caterpillar 5511C (Feller Buncher)
fake.machine_make_model()
# Caterpillar 5511C
fake.machine_make()
# Caterpillar
fake.machine_model()
# 5511C
fake.machine_year()
# 2008
fake.machine_category()
# Feller Buncher
json.dumps(fake.machine_object())
# {"Year": 2008, "Make": "Caterpillar", "Model": "5511C", "Category": "Feller Buncher"}1 maintainer
Metadata
1 maintainer
Release files for faker-vehicle 0.2.0
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 |
|---|---|---|---|---|
| faker_vehicle-0.2.0.tar.gz | 149.6 kB | Without provenance | Details for faker_vehicle-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| faker_vehicle-0.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for faker_vehicle-0.2.0-py2.py3-none-any.whl |
Total release size: 312.0 kB
Release files / faker_vehicle-0.2.0.tar.gz
| Download URL | faker_vehicle-0.2.0.tar.gz |
|---|---|
| Size | 149.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a7f1065da54b998f8875785282d3b1da4a422bc14fe0776a4a4ff4c1872a3b5
|
|
BLAKE2b-256 checksum How to use checksums |
a3f93432a540a3b6599b7365190df1030aaf93cb7c0113d2528b55511c6a48de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0
|
Release files / faker_vehicle-0.2.0-py2.py3-none-any.whl
| Download URL | faker_vehicle-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 162.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
30fa5eb81da17d6483be545431a9b51f76f2b6731ac3ee9c2e038560fca58e4a
|
|
BLAKE2b-256 checksum How to use checksums |
1292906adbed8dd2a240ecd878032be13a754df53b0389e9825cd557814c7f60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0
|
Security for faker-vehicle 0.2.0
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.
