Added the ability to pass arguments to as a string

[Neizvestnyj]

Previously, if you read dependencies from a file and passed "$requirements" from toolchain build, then the script accepted dependencies with one line (['kivy python3']), now this is fixed

Example:

we have file requirements.txt with (python3, kivy, openssl pillow)
although we have double spaces and commas in the file, the libraries are read and assembled correctly

requirements="$(cat requirements.txt)"
toolchain build "$requirements"
toolchain pip install ecdsa, bcrypt, cryptography

req = 'python3 kivy, openssl   pillow'
recipe = ''.join(req).replace(',', '').replace('  ', ' ').split()
print(recipe)  # ['python3', 'kivy', 'openssl', 'pillow']

test_req.txt

[misl6]

Left a couple of comments.

[misl6]

_pip is a "redirector" to an actual pip, so the arguments should be pip-compatible.

Why not using a requirements.txt file here?
toolchain pip install -r app-req.txt, would just work 😃

(Maybe we want to document it?)

[Neizvestnyj]

hm, yes, it must be documented

[misl6]

Easy and effective, but looks quite hacky and I don't feel super-confident about merging it. (And should be handled on the argparser side instead)

How about an argument -r or --requirement which parses a requirements.txt file as pip does ?

[Neizvestnyj]

Sounds good, why not, I'll try to implement

[Neizvestnyj]

Look, maybe we can change the argument parser, now it works like this: toolchain build '' --r "$build_requirements"