# yoloimport
*Never see another ImportError*
Are you tired of seeing ImportErrors? **yoloimport** makes ImportErrors a relic of the past, by installing your dependencies for you whenever you import a missing package. Now you can focus on writing code instead of installing dependencies!
## Installation
To install, just run `pip install yoloimport` and kiss pip goodbye, because yoloimport will deal with pip for you!
## Example
Let's try to use the [itty framework](https://github.com/toastdriven/itty) for the first time!
>>> from itty import get, run_itty
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named itty
Who wants to see that nonsense!? Let's try it after importing **yoloimport**!
>>> import yoloimport
>>> from itty import get, run_itty
Collecting itty
Using cached itty-0.8.2-py2.py3-none-any.whl
Installing collected packages: itty
Successfully installed itty-0.8.2
Collecting -winreg
Could not find any downloads that satisfy the requirement -winreg
No distributions at all found for -winreg
>>> @get('/')
... def index(request):
... return 'Hello World!'
...
>>> run_itty()
itty starting up (using wsgiref)...
Listening on http://localhost:8080...
Use Ctrl-C to quit.
Who knows what that "-winreg" error was all about? I sure don't, but who cares? We got itty working without any pesky ImportErrors getting in our way!
*Happy April 1st!*
*Never see another ImportError*
Are you tired of seeing ImportErrors? **yoloimport** makes ImportErrors a relic of the past, by installing your dependencies for you whenever you import a missing package. Now you can focus on writing code instead of installing dependencies!
## Installation
To install, just run `pip install yoloimport` and kiss pip goodbye, because yoloimport will deal with pip for you!
## Example
Let's try to use the [itty framework](https://github.com/toastdriven/itty) for the first time!
>>> from itty import get, run_itty
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named itty
Who wants to see that nonsense!? Let's try it after importing **yoloimport**!
>>> import yoloimport
>>> from itty import get, run_itty
Collecting itty
Using cached itty-0.8.2-py2.py3-none-any.whl
Installing collected packages: itty
Successfully installed itty-0.8.2
Collecting -winreg
Could not find any downloads that satisfy the requirement -winreg
No distributions at all found for -winreg
>>> @get('/')
... def index(request):
... return 'Hello World!'
...
>>> run_itty()
itty starting up (using wsgiref)...
Listening on http://localhost:8080...
Use Ctrl-C to quit.
Who knows what that "-winreg" error was all about? I sure don't, but who cares? We got itty working without any pesky ImportErrors getting in our way!
*Happy April 1st!*
1 maintainer
Metadata
1 maintainer
Release files for yoloimport 0.1.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 | |
|---|---|---|---|---|
| yoloimport-0.1.0.tar.gz | 2.1 kB | Without provenance | Details |
Release files / yoloimport-0.1.0.tar.gz
| Download URL | yoloimport-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7ff5641cd7d378a0dca761d45b11d579c07a63355998518a2acb07aedcaa0f8
|
|
BLAKE2b-256 checksum How to use checksums |
5e46f351110531ab0be2124e97c95384c3f18e7f2eef73545e40a0f05259513e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for yoloimport 0.1.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.
