semvec/pypi-packages huggingface dataset:
demo-game-guess-number 0.0.7
小游戏演示——猜数字

猜 0-100 中的一个数字：
```
$ 猜数字
我想了个 100 之内的数，猜猜是几？
请猜吧: 50
太大了!
请猜吧: 20
太大了!
请猜吧: 5
太大了!
请猜吧: 2
中了!
```

## 介绍文章

[在 PyPI 发布 Python 纯文字游戏试水——猜数字](https://zhuanlan.zhihu.com/p/141758876)
readPos 0.2
Read plain text file data from csv map

# readPos Package usage

readPos is a package built to work with data files by positions.
So we gonna need some text plain data file and some definition files (csv) to read that data. 

With some methods we can directly work with dataframe objetc (pandas) and a 
definition file to construct the dat file output.

#### IMPORT PACKAGE IN OUT SCRIPTS
The statement to import some objects and methos from readPos Package is like this:
```python
from readPos.readPos import {{METHOD}}
```
Where {{METHOD}} we must indicate which object we gonna import. The most used is:
```python
from readPos.readPos import ReadPos
```
ReadPos class need two params to create an instance:
* <b>file_name</b> = this param will be a string containing the absolute or relative path to data file we wanna work with (if we gonna write some dat file, this gonna be the output name)

* <b>csv_file </b> = this param will be a string containing the absolute or relative path to csv file that contains the definition for each variable we wanna work with. This file must contain 3 fields at least (order not matter but exact column name does):
  * variable: string field that have a value (without spaces and non number starting) used to set column names in read method or to match dataframe columns in write method.
  * initial: integer field. Initial position (not index) where data will be read from input file or where will be writted in output file.
  * end: integer field. Final position (not index) where data will be read from input file or where will be writted in output file.

  Other self information columns (descriptions, length) can be added to csv file, them not gonna do a crash error but can overcharge process time.
  Initial position of the variables could not be in ascending order. The read/write method will order it internally. 



#### HOW TO READ DAT FILES INTO STRUCTURED DATA FRAME

```python
from readPos.readPos import ReadPos

readpos_instance = ReadPos(file_name = 'C:/Users/MyUser/dummy.dat', csv_file = 'definition.csv')

dataframe = readpos_instance.read() # dataframe objetct will be a pandas core dataframe with as many columns as rows you have in your csv file and as many rows as lines you have in your 

```
*Optional "encoding" param with string like 'latin-1' is allowed. Default value = 'UTF-8'*

#### HOW TO ERITE DAT FILES FROM STRUCTURED DATA FRAME
```python
from readPos.readPos import ReadPos

readpos_instance = ReadPos(file_name = 'C:/Users/MyUser/dummy.dat', csv_file = 'definition.csv')

readpos_instance.write(df) # df is a dataframe object with at least all de columns that we have defined in csv file. df can contain more columns than csv, so these columns will be not written in output dat file.

*Optional "encoding" param with string like 'latin-1' is allowed. Default value = 'UTF-8'*

```
loguetools 0.1.4
Korg minilogue family patch manipulation tools
Requires Python: >=3.7

# loguetools

**loguetools** manipulates Korg 'logue'-series synthesizer patch libraries (what Korg calls program collections).

It perform a few tasks:
* Translation of patches from the (original) minilogue to the minilogue xd. See the [translation](#translation) section for a description and limitations.  
(For *minilogue xd*)
* Bulk extraction of all patches in collections to separate patch files.  
(For *minilogue*, *minilogue xd* and *prologue*)
* Readable display of patch contents.  
(For *minilogue* and *minilogue xd*)

There are two versions:
1. A gui-based version (Windows and MacOS)
2. A set of commandline tools written in Python (3.7 or later)

# Installing
## GUI
Just download and run the latest version from [Releases](https://github.com/gazzar/loguetools/releases/latest).  
The files are single-click executables; no need to install. There are Windows (.exe) and macOS (.app.zip) versions.

## Commandline tools
These require Python 3.7 or later.
Install with pip

```bash
pip install loguetools
```

# Using

## GUI

See the wiki.

## Commandline tools
pip will install the script entry points. All tools contain documention for parameters, e.g. **translate --help**

**dump** (For *minilogue* and *minilogue xd*)  
Display the contents of a program or preset pack. -m generates md5 checksums for patches.

**explode** (For *minilogue*, *minilogue xd* and *prologue*)  
Bulk extraction of individual patches from libraries.

**translate** (For *minilogue xd*)  
Translate (original) minilogue patches to the minilogue xd.


# Limitations

The hardware and routing possibilities for the OG and xd differ in significant ways. The translate tool tries to make sensible choices about setting the xd's EG and LFO hardware to match the original patch but the options are limited.

I don't own an original minilogue so I have limited ability to test the translation accuracy. I found [Jeff Kistler's minilogue editor](https://github.com/jeffkistler/minilogue-editor) very helpful for checking some of the parameter translations. Korg's documentation has some errors and omissions and I haven't worked out how to translate everything correctly yet; if you notice a problem, let me know or create an issue!

These are on my radar
* No prologue patch translation yet
* Smarter use of the xd multi-engine to switch between noise and sub oscillator

# Known problems
* I haven't created minilogue patch packs that can be distributed. Thus most unit tests will fail. This may improve in future.

# Licenses
See LICENSE.txt  
Code released under the 3-clause BSD license.  
Application icon "tools by i cons from the Noun Project"

# Development notes
Suggestions and bug reports are welcome. Pull requests will probably be welcome; feel free to create a feature suggestion first to discuss.