semvec/pypi-packages huggingface dataset:
libraryshad 1.1.3
Another example of the library making the shad's robot
License: MIT
Keywords: rubika,bot,robot,library,rubikalib,rubikalib.ml,rubikalib.ir,rubika.ir,Rubika,Python,rubiran,pyrubika,shad,telebot,twine



## An example:
``` python
from libraryshad import Bot
import asyncio

bot = Bot(auth="Auth Account",key="Key Account")

gap = "guids"
async def main():
	data = await bot.sendMessage(gap,"mamadcodrr")
	print(data)
asyncio.run(main())
```


## An example:
``` python
from libraryshad import asyncio,Bot

bot = Bot(session="session")
async def main():
	data = await bot.getChats()
	print(data)
asyncio.run(main())

```


### How to import the shad's library

``` bash
from libraryshad import Bot
```

### How to install the library

``` bash
pip install libraryshad==1.1.3
```

### My ID in Rubika

``` bash
@professor_102
```
## And My ID Channel in Rubika

``` bash
@python_java_source 
```
sonosaudioservicelib 0.3.0
A template for Sonos Audio services
License: MIT
Keywords: sonosaudioservicelib

====================
sonosaudioservicelib
====================

A template for Sonos Audio services


* Documentation: https://sonosaudioservicelib.readthedocs.org/en/latest


Development Workflow
====================

The workflow supports the following steps

 * lint
 * test
 * build
 * document
 * upload
 * graph

These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.

The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project

Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call

    $ _tag --minor

which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.


So the full workflow after git is initialized is:

 * repeat as necessary (of course it could be test - code - lint :) )

   * code
   * lint
   * test
 * commit and push
 * develop more through the code-lint-test cycle
 * tag (with the appropriate argument)
 * build
 * upload (if you want to host your package in pypi)
 * document (of course this could be run at any point)


Important Information
=====================

This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of this **do not** simple call

    $ python setup.py sdist bdist_egg

**as this will produce an unusable artifact with files missing.**
Instead use the provided build and upload scripts that create all the necessary files in the artifact.



Project Features
================

* TODO




History
-------

0.0.1 (07-11-2023)
---------------------

* First code creation


0.1.0 (08-11-2023)
------------------

* Initial release


0.2.0 (22-12-2023)
------------------

* Added aggregated service


0.3.0 (24-12-2023)
------------------

* Changed favorites into a property
vizmyip 0.1.2
Visualizes public IP information of your system.
License: MIT
Keywords: python,flask,ip,public ip

# vizmyip
Visualizes public IP information of your system.

## Installation
Install `vizmyip` with pip3
```bash
$ pip3 install --user vizmyip
```

## Run Locally
After the installation,
```bash
$ vizmyip
```

## Feedback and Contributing
Contributions are always welcome! And, if you have any feedback or query, please reach out to me at hello@amaharjan.de.

## Related
Here are some related links for this project:
- https://amaharjan.de/what-is-my-ip-a-simple-flask-project/

## License
[MIT](./LICENSE)
aio-dtls 0.0.4
asyncio implementation of the dtls protocol in python
License: MIT
Requires Python: >=3.9
Keywords: python tls dtls mbed asyncio

# aio_dtls

[![img lib ver](https://img.shields.io/pypi/v/aio_dtls.svg "")](https://pypi.python.org/pypi/aio_dtls)
[![img python ver](https://img.shields.io/pypi/pyversions/aio_dtls.svg "")](https://pypi.python.org/pypi/aio_dtls)
[![img license](https://img.shields.io/pypi/l/aio_dtls.svg "")](https://pypi.python.org/pypi/aio_dtls)

The implementation of dtls was made to connect to the iotivity which uses the mbedtls and not the standard cipher.

Handshake dtls and tls for ECDHE_ANON is working now

A simple example of use can be seen in example.py

An example implementation of the COAPS protocol in Bubot_CoAP