semvec/pypi-packages huggingface dataset:
tinc 0.9.56
TINC python module
Requires Python: >=3.6

# TINC python module and tools

This is the python module for TINC. It can be used standalone, or in conjunction with a C++ application written with TINC to provide a TINC server:

https://github.com/AlloSphere-Research-Group/tinc

tinc-python depends on numpy, matplotlib, netcdf4, filelock and jsonschema. If ipywidgets is available, tinc-python can provide interactive widgets for the jupyter notebook.

To tinc for python:
```
pip install tinc
```

To install ipywidgets for jupyter widget support:
```
pip install ipywidgets
```
# Documentation

The TINC python documentation is available at: https://tinc-python.readthedocs.io/en/latest/

A set pf tutorials for tinc-python can be found in the documentation.

Try out TINC:

https://colab.research.google.com/drive/1XO-babUACUdeyp8YikofT6ySJAdjG1e8?usp=sharing#scrollTo=15R56pWsdSvg

https://colab.research.google.com/drive/1jjJhJHVvunEOXf3bUHmLNVMm_cKqls26?usp=sharing 

# Installing jupyterlab on macOS Through homebrew
There are many ways to install jupyterlab. Here is one we have tested to work with TINC.
```
brew install jupyterlab
```

When brew installs jupyter lab and installs python3.8, it mentions it is keg only, so need to follow brew's instructions:
```
Python has been installed as /usr/local/opt/python@3.8/bin/python3
You can install Python packages with /usr/local/opt/python@3.8/bin/pip3 install <package>
They will install into the site-package directory
/usr/local/opt/python@3.8/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
python@3.8 is keg-only, which means it was not symlinked into /usr/local,
because this is an alternate version of another formula.
If you need to have python@3.8 first in your PATH run:
echo 'export PATH="/usr/local/opt/python@3.8/bin:$PATH"' >> /Users/cannedstar/.bash_profile
For compilers to find python@3.8 you may need to set:
export LDFLAGS="-L/usr/local/opt/python@3.8/lib"
For pkg-config to find python@3.8 you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/python@3.8/lib/pkgconfig"
```

To install additional dependencies for tinc-python for the jupyter python:
```
/usr/local/opt/python@3.8/bin/pip3 install filelock matplotlib ipywidgets
```
text-to-tweets 0.1.1
Split a chunk of text into 280-character blocksAttempting to split at the end of sentences etc.

# Text to tweets

This small package simply splits a large block of text into 280 character chunks.

The code is lifted wholesale from https://github.com/NaruBeast/tweet-splitter.

## Install

``` bash
pip3 install text-to-tweets
```

## Usage

``` python3
from text_to_tweets import tweet_splitter

tweets = tweet_splitter(
    article_text,
    counter=True  # Add counters to tweets - e.g. "(3/10)"
)
```
witchui 0.1.0
Helpful tools for designing text-based interfaces, based on curses.
Requires Python: >=3.7,<4.0

# Witchui

Helpful utilities for designing text-based interfaces on top of curses.


## Usage

See an example below, showing usage of some of the tools provided.


```python
import curses
from witchui import (
    setup_curses_colors,
    WindowPrinter,
    TitleText,
    SelectionDropdown,
    InputText,
)

def main(window):
    curses.curs_set(0)
    setup_curses_colors()

    window.clear()
    wprinter = WindowPrinter(window)
    wprinter.print(TitleText("My title"))
    wprinter.print("Choose from the list below:")

    possible_choices = ["apples", "bananas", "oranges"]
    selection = SelectionDropdown(window, possible_choices, line=2, col=4)
    selected_option = selection.run()

    input_text = InputText(window, line=6, col=2).run()

curses.wrapper(main)
```
helpmepack 0.0.2
Python Package helper CLI
Requires Python: >=3.7

# Python Packaging helper
A Python Packaging helper CLI

### LEARN

[Learn about Python packaging](https://packaging.python.org/en/latest/)

[Simple packaging tutorial](https://packaging.python.org/en/latest/tutorials/packaging-projects/)


## Installation

using pip command line:
```
pip install helpmepack
```

OR

Download Build file:

[Source Distribution](https://files.pythonhosted.org/packages/b7/ce/5a49fd3a2c51701a469d75b7ee12ac16529513ad2dcd7c68933772c97d04/helpmepack-0.0.1.tar.gz)

[Built Distribution](https://files.pythonhosted.org/packages/b3/0e/b613098ff9e22176ff7c0681c4b7bccbe36cb2cd2540e43da32ec0f7325a/helpmepack-0.0.1-py3-none-any.whl)

## Usage

Please make sure you have your '.git' folder, and README.md, .gitignore, requirments.txt, LICENSE files - in your project directory.

All the other project files will be moved to the 'src' folder.

Make sure you running in the Project Main Directory.


## 
Run Python (in cmd/bash) in your project directory

```
from helpmepack import helpmepack 
```

```
helpmepack.main()
```
publish-markdown 0.2.1
Publish articles written in Markdown files to medium.com, dev.to, hashnode and twitter

# Publish markdown

Publish articles written in Markdown files to the following platforms:

- medium.com
- dev.to
<!--
- hashnode.com
- twitter.com
-->

Markdown files should include YAML frontmatter with at least a `title`. Adding `tags` will help your posts reach a wider audience on the target platforms:

```
---
title: Some title or other
tags: ["webdev", "writing"]
---

{content in Markdown}
```

I wrote this to cross-post article from [my own Jekyll blog](https://robinwinslow.uk), in a GitHub workflow (which I may yet publish as an action).

## Installation

``` bash
$ pip3 install publish-markdown
```

## Publishing to medium.com

``` bash
$ export MEDIUM_TOKEN={your-integration-token}
$ publish-to-medium _posts/2022-01-01-my-first-post.md --canonical-url="https://my-blog.com/2022/01/02/my-first-post"
Found user ID: {your-user-id}
- Article published at https://medium.com/@auser/my-first-post-50134f3aeba0
- Added 'medium.com' to 'published_to' metadata
```

### Optimisations

You can avoid the code having to retrieve your user ID every time by setting it as an environment variable as well:

``` bash
export MEDIUM_USER_ID={your-user-id}
```

## Publishing to dev.to

``` bash
$ export DEV_TO_TOKEN={your-api-token}
$ publish-to-DEV _posts/2022-01-01-my-first-post.md --canonical-url="https://my-blog.com/2022/01/02/my-first-post"
- Article published at https://dev.to/auser/my-first-post-74n
- Added 'dev.to' to 'published_to' metadata
```

## Is cross-posting allowed / a good idea?

Cross-posting to extra platforms gets your post to be seen by more communities. This is mostly a good thing - people in one community are unlikely to also be in another simultaneously. 

While plainly duplicating content on the internet is not generally a good idea, cross-posting or syndicating is fine where it's done right. Dev.to, Medium and Hashnode all explicitly support cross-posting, by providing the ability to set a `rel=canonical` meta tag inside their posts. And [Google explicitly mention](https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls) syndication of articles as a legitimate use of the `rel=canonical` tag.

So yes, cross-posting is a good idea.
wfaccountmanager 0.0.7
Python Wrapper library for Warface that allows you to login and manage data
Requires Python: >=3.6

# Warface Account Wrapper

## Usage

from wfaccountmanager import WFAccountManager

wf = WFAccountManager("west")
wf.login("email","password")

Full documentation available here: https://github.com/seanwlk/wfaccountmanager