semvec/pypi-packages huggingface dataset:
dawatoma 0.2.2
DAW Automation - music idea generation software

**DAWATOMA** stands for **D**igital **A**udio **W**orkstation
**A**u**TOMA**tion.

dawatoma allows the acceleration of creative tasks that often take place in a
DAW. It allows the generation of derived melodies given a 'fingerprint' melody
upon which the derived ones are based. The way my creative process often works
when producing music is that I have one main melody, and I build the song
around that, and a lot of that involves composing additional melodies that go
well with the main one. A portion of this is algorithmic and can be outsourced
to computational algorithms. There is, of course, already software out
there like arpeggiators and such that can do such things, but I wanted to
build a package that is built entirely around the idea of deriving melodies
from base melodies, with an easily expandable list of derivation protocols
that other developers can contribute to. The derived note sequences, as well
as the original, can be written to MIDI (.mid) format.

This package utilizes the plain text ".dawa" format to represent note
sequences. .dawa format looks as follows and contains all relevant information
about a note sequence:\n
tempo_in_BPM # Commment\n
note1 time duration\n
note2 time duration\n
...\n
noteN time duration\n

Where time and duration are in beats, and time is the point in time in the
sequence that a note begins, and duration is how long the note lives. The
initial strings "not1e1", "note2", etc are strings like "C5" which will be
interpreted with the NoteDict, also included in this package.

This package depends on MIDIUtil.
cmdfile 1.2.2
cmdfile runs annoying commands automatically.
Requires Python: >=3.9

# cmdfile
cmdfile runs annoying commands automatically.

# Docs

## Installation

Run `python -m pip install cmdfile` in your terminal.

## Usage

You can use cmdfile as a command, or as a module.

Example for using as a command:
```
> python -m cmdfile build
Hello
```
You can specify cmdfile filename with the following: `python -m cmdfile tablename filename`

(By default, if you simply run `python -m cmdfile`, it will run the `main` table of the `cmdfile` file)

This will run the `hello` table of the cmdfile, note that the cmdfile must be in the directory you're running the script from, example cmdfile:

```
(hello)
echo Hello
```

---

`python -m cmdfile check temp` is the equivalent of this:

```py
import cmdfile

cmdfile.run("check", filename="temp")
```

---

### Variables

You can declare variables in the cmdfile using:
```
# You can declare variables outside of tables
# some_variable = "I'm not in any table!"

(table)
variable = "some text"

echo {{variable}}
```
`some text`

You can also declare variables through code like this:
```py
import cmdfile

cmdfile.add_var("variable", "some text")
cmdfile.run("table")
```

And then this will also output `some text`:
```
(table)
echo {{variable}}
```

---

### Changing the shell

You can change what shell to use by changing the `shell` variable:
```
shell = "powershell.exe -c"

[main]
echo 'Hello' # Executes "powershell.exe -c echo 'Hello'"
```

---

### Requirements

Requirements are tables that run before the main table, example:
```
[main] a_requirement another_requirement
# This will call a_requirement, another_requirement and main, respectively


[a_requirement]
# ...

[another_requirement]
# ...
```

---

# 1.2.2 Bugfix
- Fixed cmdfile giving error when directly calling without args

# Changelog for 1.2.0
- Added "requirements", this calls other tables before running the current table, example:

```
[main] a_requirement another_requirement
# This will call a_requirement, another_requirement and main, respectively


[a_requirement]
# ...

[another_requirement]
# ...
```

- You can now select the shell to use to run commands like this:
```
shell = "powershell.exe -c"

[main]
echo 'Hello' # Executes "powershell.exe -c echo 'Hello'"
```

- Changed variable usage from `{_varname_}` to `{{varname}}`
web-express-py 0.0.10
Webserver written as express.js
Requires Python: >=3.7

# [express.py](https://pypi.org/project/web-express-py/)
Python implementation of the widely used express.js

# Why
Going to answer this first: because yes. More out of boredom and wanting to do something with my time rather than playing games. But oh well, here it is.

# Installation
Install this package with a very very very very very simple command:
```sh
# Unix / macOS:
python3 -m pip install --upgrade web-express-py

# Windows:
py -3 -m pip install --upgrade web-express-py
```

After this, you can just import `express` into any of your projects using:
```py
from express import express
```

## Ok here comes stealing examples from express.js

# Hello world example
```py
from express import express

app = express()

@app.get("/")
def helloWorld(req, res):
    res.send("Hello World!")

app.listen(3000)
```

# Basic routing
```py
from express import express

app = express()

@app.get("/")
def helloWorld(req, res):
    res.send("Hello World!")

@app.post("/")
def aPostRequest(req, res):
    res.send("Got a POST request")

@app.put("/user")
def updateUser(req, res):
    res.send("Got a PUT request at /user")

def deleteUser(req, res):
    res.send("Got a DELETE request at /user")
app.delete("/user", deleteUser)

app.listen(3000)
```

# More routing info
If you want to read **all** of the routing API through the guide???? [click here](https://github.com/Hattorius/express.py/wiki/Guide---Routing)

If you want to read **all** about how to setup middleware, [read this](https://github.com/Hattorius/express.py/wiki/Writing-middleware)