|
1 | | -# fileforge-python-sdk |
| 1 | +<!-- Begin Title, generated by Fern --> |
| 2 | +# Fileforge Python Library |
| 3 | + |
| 4 | +[](https://github.com/fern-api/fern) |
| 5 | + |
| 6 | +The Fileforge Python Library provides convenient access to the Fileforge API from applications written in Python. |
| 7 | +<!-- End Title --> |
| 8 | + |
| 9 | +<!-- Begin Installation, generated by Fern --> |
| 10 | +# Installation |
| 11 | + |
| 12 | +```sh |
| 13 | +pip install --upgrade fileforge |
| 14 | +``` |
| 15 | +<!-- End Installation --> |
| 16 | + |
| 17 | +<!-- Begin Usage, generated by Fern --> |
| 18 | +# Usage |
| 19 | + |
| 20 | +```python |
| 21 | +from fileforge.client import Fileforge |
| 22 | + |
| 23 | +client = Fileforge( |
| 24 | + api_key="YOUR_API_KEY", |
| 25 | + username="YOUR_USERNAME", |
| 26 | + password="YOUR_PASSWORD", |
| 27 | +) |
| 28 | +``` |
| 29 | +<!-- End Usage --> |
| 30 | + |
| 31 | +<!-- Begin Async Usage, generated by Fern --> |
| 32 | +# Async Client |
| 33 | + |
| 34 | +```python |
| 35 | +from fileforge.client import AsyncFileforge |
| 36 | + |
| 37 | +client = AsyncFileforge( |
| 38 | + api_key="YOUR_API_KEY", |
| 39 | + username="YOUR_USERNAME", |
| 40 | + password="YOUR_PASSWORD", |
| 41 | +) |
| 42 | +``` |
| 43 | +<!-- End Async Usage --> |
| 44 | + |
| 45 | +<!-- Begin Status, generated by Fern --> |
| 46 | +# Beta Status |
| 47 | + |
| 48 | +This SDK is in beta, and there may be breaking changes between versions without a major |
| 49 | +version update. Therefore, we recommend pinning the package version to a specific version. |
| 50 | +This way, you can install the same version each time without breaking changes. |
| 51 | +<!-- End Status --> |
| 52 | + |
| 53 | +<!-- Begin Contributing, generated by Fern --> |
| 54 | +# Contributing |
| 55 | + |
| 56 | +While we value open-source contributions to this SDK, this library is generated programmatically. |
| 57 | +Additions made directly to this library would have to be moved over to our generation code, |
| 58 | +otherwise they would be overwritten upon the next generated release. Feel free to open a PR as |
| 59 | + a proof of concept, but know that we will not be able to merge it as-is. We suggest opening |
| 60 | +an issue first to discuss with us! |
| 61 | + |
| 62 | +On the other hand, contributions to the README are always very welcome! |
| 63 | +<!-- End Contributing --> |
| 64 | + |
0 commit comments