inincompatibility
A dependency-free, code-less socket-based solution for resolving (Python / conda) environment incompatibilities.
Usage Guidelines
Installation:
To install the inincompatibility package, run:
pip install inincompatibility
Example: Making Your LLMs Callable Like an API:
First, make your LLMs (e.g., Llama-3.2-1B) callable functions:
# your_llm.py
import torch
from transformers import pipeline as pl
m = "meta-llama/Llama-3.2-1B"
p = pl("text-generation", model=m, device="cuda")
def llm_qa(msg: list) -> dict:
return p(msg)[0]["generated_text"]
Next, create another Python file (e.g., to_import_ori.py) to import the LLM function:
# to_import_ori.py
from your_llm import llm_qa
Then, use the inincompatibility CLI to generate the necessary importable code and then run the LLM in its (Python / conda) environment:
conda activate llama
pip install inincompatibility
python -m inincompatibility -i to_import_ori.py -o to_import.py
A file named to_import.py (specified by the -o argument) will be generated as follows:
# Generated by `inincompatibility`.
# **Not** depend on `incompatibility`. :)
# You can directly `import` this file in another environment.
import socket
import pickle
BUFFER_SIZE = 65536
client = socket.socket(2, socket.SOCK_STREAM)
client.connect(('127.0.0.1', 57849))
def _func_eval(func, args, kwargs):
data = pickle.dumps((func, args, kwargs))
client.sendall(data)
return pickle.loads(client.recv(BUFFER_SIZE))
def _inincompatibility_remote_eval(*args, **kwargs):
return _func_eval('_inincompatibility_remote_eval', args, kwargs)
def _inincompatibility_remote_exec(*args, **kwargs):
return _func_eval('_inincompatibility_remote_exec', args, kwargs)
def llm_qa(*args, **kwargs):
return _func_eval('llm_qa', args, kwargs)
Now, you can directly import the generated code in another (Python / conda) environment:
# main.py
from to_import import llm_qa
print(llm_qa('The key to life is'))
Run your main script (e.g., main.py) in the target environment:
conda activate blackbox
python main.py
For more details, check out the sample-llama directory on GitHub.
Example: Additional Samples:
For more usage examples, visit the sample-local directory on GitHub.
Metadata
Release files for inincompatibility 0.0.8
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 |
|---|---|---|---|---|
| inincompatibility-0.0.8.tar.gz | 8.1 kB | Without provenance | Details for inincompatibility-0.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| inincompatibility-0.0.8-py3-none-any.whl | Python 3 | none | any | Details for inincompatibility-0.0.8-py3-none-any.whl |
Total release size: 16.2 kB
Release files / inincompatibility-0.0.8.tar.gz
| Download URL | inincompatibility-0.0.8.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84c95f125965e7982c1deca6feb306df4fe7015011faf24d78d2bd99a5a43e42
|
|
BLAKE2b-256 checksum How to use checksums |
1524ec33f59b9b29bb84c66e0c788f3989399a79eb06a905c4af1fdf0d8b9257
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.7
|
Release files / inincompatibility-0.0.8-py3-none-any.whl
| Download URL | inincompatibility-0.0.8-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b344df1072073489fb2906311fdd87b8ff4f8d6c952b1086c7598ad2b68c46cd
|
|
BLAKE2b-256 checksum How to use checksums |
3248ec8c337595171e5141350e8d87027c981967280adf85ae3afd0589f3c5af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.7
|
Security for inincompatibility 0.0.8
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.