semvec/pypi-packages huggingface dataset:
django-icons-bootstrap-icons 1.0.1
Bootstrap Icons renderer for django-icons
Requires Python: >=3.10
Keywords: bootstrap, bootstrap-icons, django, django-icons, icons

# django-icons-bootstrap-icons

This project provides a renderer for [Bootstrap Icons](https://icons.getbootstrap.com) utilizing [django-icons](https://django-icons.readthedocs.io/en/latest/index.html).

## Installation

[PyPI](https://pypi.org/project/django-icons-bootstrap-icons/)

Just run:

```
pip install django-icons-bootstrap-icons
```

## To use

In your settings.py file:

```py

DJANGO_ICONS = {
  "DEFAULT": {
    "renderer": "django_icons_bootstrap_icons.BootstrapIconRenderer"
  }
}
```

Then just use the `{% icon %}` tag as normal!

## Extra features

This renderer includes a very neat feature over the default `IconRenderer`, which is support for custom attributes.

For instance, to add an aria-label to your icon, you can do the following:

`{% icon "person" aria_label="person icon" %}`

Note that while attributes in HTML are `-`, separated, this isn't possible in Django templates due to Python. Therefore, write the keys with `_` instead, and the renderer will autoconvert them for you.

This also works with attributes that do not have `-`es in them, such as `tabindex`.

Aside from this, `BootstrapIconRenderer` supports all features of the default renderer as it is just a superclass of `IconRenderer`.

## Contributing

I welcome all contributions! Just fork and then send a PR.

## License

This work is licensed under the MIT license.
hopfield-memory 0.0.2
A Hopfield Network for associative memory tasks, specifically focusing on retrieving images even when they are blurred or corrupted.
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/hopfield
touch src/hopfield/__init__.py
touch src/hopfield/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/
liquid-memory 0.0.1
A Hopfield Network for associative memory tasks, specifically focusing on retrieving images even when they are blurred or corrupted.
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/hopfield
touch src/hopfield/__init__.py
touch src/hopfield/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/
j2o 0.0.7
Converter from Jupyter notebook format to Org format (Emacs text editor), without requirements for any libraries.
Requires Python: >=3.10


# Table of Contents

1.  [j2o](#org0f5b20b)
2.  [Command line usage](#org849eb57)
3.  [How this works](#org03a1552)
4.  [Info: Other useful projects](#org70dde9a)
5.  [Info: Format of ipynb](#org5aa75ac)
6.  [features](#orgbd220b4)

    ![badge](https://github.com/Anoncheg1/j2o/actions/workflows/python-test.yml/badge.svg?event=push)
    ![badge](https://github.com/Anoncheg1/j2o/actions/workflows/python-publish.yml/badge.svg?event=release)


<a id="org0f5b20b"></a>

# j2o

Converter from Jupyter to Org file format without any dependencies.

Without this package your only alternative is to use nbconver or pandoc with 164
 dependencies just to be able to convert simple JSON format.

TODO: make reverse convrter.

<https://pypi.org/project/j2o/>


<a id="org849eb57"></a>

# Command line usage

    usage: j2o myfile.ipynb [-w] [-j myfile.ipynb] [-o myfile.org]

    Convert a Jupyter notebook to Org file (Emacs) and vice versa

    positional arguments:
      jupfile_              Jupyter file

    options:
      -h, --help            show this help message and exit
      -j JUPFILE, --jupfile JUPFILE
                            Jupyter file
      -o ORGFILE, --orgfile ORGFILE
                            Target filename of Org file. If not specified, it will
                            use the filename of the Jupyter file and append .ipynb
      -w, --overwrite       Flag whether to overwrite existing target file.


For Linux add this line to ```~/.bashrc```
```sh
  export PATH=$PATH:/home/youruser/.local/bin
```
<a id="org03a1552"></a>

# How this works

1.  Loops through "cells".
2.  Extract "source"
3.  add Org header and tail around source ("#+begin\_src python &#x2026;", "#+end\_src")


<a id="org70dde9a"></a>

# Info: Other useful projects

-   p2j <https://pypi.org/project/p2j/> <https://github.com/remykarem/python2jupyter>
-   <https://github.com/jkitchin/ox-ipynb>


<a id="org5aa75ac"></a>

# Info: Format of ipynb

JSON

    {
      cells: [
        cell_type: "code/markdown",
        source: ["\n","\n",""],
        outputs: [{
          text: ["\n", "\n"],
          data: {
            image/png: "base64....",
            text/plain: "image description"}
          }
        ]
      ],
      metadata: {
        kernelspec: {
          language: "python"
        }
      }
    }


<a id="orgbd220b4"></a>

# features

-   in markdown cells conversion: source blocks, ‘#’ to ‘\*’.
-   code cells: images
-   Tested for nbformat: 4.2.
domika-ha-framework 0.0.5
Domika integration module framework.

![GitHub License](https://img.shields.io/github/license/DevPocket/domika-ha-framework)
![PyPI - Version](https://img.shields.io/pypi/v/domika-ha-framework)

# Domika haomeassistant framework

Domika integration framework library.

## Development

### Create new database revision

```bash
cd src
DOMIKA_DB_URL="Put database url here" alembic -c domika_ha_framework/alembic.ini revision -m "Put revision message here"
```

### Upgrade head

```bash
cd src
DOMIKA_DB_URL="Put database url here" alembic -c domika_ha_framework/alembic.ini upgrade head
```
thl-phonetic-transliteration 0.2.4
The goal of this code is to provide a library to convert Tibetan unicode and Wylie transliterations to THL Simplified Phonetic Transliteration.
Requires Python: >=3.8

# thl_phonetic_transliteration

## Description

This project has been renamed [mlotsawa](https://pypi.org/project/mlotsawa/). The version here is deprecated. Please use [mlotsawa](https://pypi.org/project/mlotsawa/) instead.

The goal of this code is to provide a library to convert Tibetan unicode and Wylie transliterations to THL Simplified Phonetic Transliteration.
This project was inspired by the similar Perl module created by Roger Espel Llima and the pyewts module for converting between Tibetan unicode
and Wylie transliterations.

This package is part of the larger MLotsawa project for machine translation of Literary Tibetan. The code for the entire project, 
including this package is [available on GitHub here.](https://github.com/billingsmoore/MLotsawa)

## Installation

```
pip install thl-phonetic-transliteration
```

## Examples

```python
from thl_phonetic_transliteration.transliterator import Transliterator 

tibetan_text = '<your Tibetan text>'

transliterator = Transliterator()

thl_phonetics = transliterator.convert(tibetan_text)
```
## License

Shield: [![CC BY-NC-SA 4.0][cc-by-nc-sa-shield]][cc-by-nc-sa]

This work is licensed under a
[Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License][cc-by-nc-sa].

[![CC BY-NC-SA 4.0][cc-by-nc-sa-image]][cc-by-nc-sa]

[cc-by-nc-sa]: http://creativecommons.org/licenses/by-nc-sa/4.0/
[cc-by-nc-sa-image]: https://licensebuttons.net/l/by-nc-sa/4.0/88x31.png
[cc-by-nc-sa-shield]: https://img.shields.io/badge/License-CC%20BY--NC--SA%204.0-lightgrey.svg

## Owner

[@billingsmoore](https://github.com/billingsmoore)
hopfield-net 0.0.1
A Hopfield Network for associative memory tasks, specifically focusing on retrieving images even when they are blurred or corrupted.
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/hopfield
touch src/hopfield/__init__.py
touch src/hopfield/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/