Py-trans

- Optimized for better performance (Removed unnecessary features and nested function calls)
- Simplified functions (Instead of passing engine through variables in `translate` function, you can now just use the engine name itself. [More...](https://github.com/Itz-fork/py-trans#usage))
- Removed libre translate as it requires an API Key

py-trans-pypi-v0.5.5
- Fixed google translate
- Removed libre translate due to low translation accuracy and API changes
- Fixed initializing aiohttp clients without any particular reason

**Full Changelog**: https://github.com/Itz-fork/py-trans/compare/py-trans-pypi-v0.5...py-trans-pypi-v0.5.5

py-trans-pypi-v0.5
- Added Asynchronous version
- Fixed translate.com translator

py-trans-pypi-v0.4

The new version (v0.4) of py-trans is just released with some newly added features and bug fixes!

What's new.
- Added new translation engine
- Added function to get language name / code (ISO 639-1)
- Added source language detection to translate.com engine
- Added option to select full form of source language or language code of source language in language detection function

Fixes,
- Fixed attribute error while translating with LibreTranslate

py-trans-pypi-v0.3
[py-trans](https://pypi.org/project/py-trans/) Now Supports for 4 engines :partying_face:
Currently Supported Engines (Providers) are,
- [Google Translate](https://translate.google.com/) - "google"
- [LibreTranslate](https://libretranslate.com/) - "libre"
- [translate.com](https://www.translate.com/) - "translate.com"
- [MyMemory](https://mymemory.translated.net/) - "my_memory"

<li><samp>Added New Provider (MyMemory)</samp></li>
<li><samp>Returns data as dict</samp></li>
<li><samp>translation engine and origin lanfuage are now included in return dict</samp></li>

py-trans-pypi
Pypi release of py-trans library.

Supported Translation Engines:
- Google translate - "google"
- LibreTranslate - "libre"
- translate.com - "translate.com"