Cannot run hvcc with only patch name.
Borey345 opened this issue · 4 comments
I have installed the 0.10.0 release of hvcc, Python 3.9.18
Trying to run 'hvcc D:\work\PCG\pdPatches\nr_main.pd'
It gives:
**Traceback (most recent call last):
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\lib\runpy.py", line 197, in run_module_as_main
return run_code(code, main_globals, None,
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\Scripts\hvcc.exe_main.py", line 7, in
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\lib\site-packages\hvcc_init.py", line 350, in main
results = compile_dataflow(
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\lib\site-packages\hvcc_init.py", line 186, in compile_dataflow
subst_name = re.sub(r'\W', '_', patch_name)
File "C:\Users\rWX1203416\Anaconda3\envs\heavy\lib\re.py", line 210, in sub
return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or bytes-like object
After looking at init.py, I discovered that patch_meta_file is None, thus patch_name is None. Then on line 186 it fails.
Am I doing something wrong? Is the '--meta' parameter mandatory?
Hmm, shouldn't be. You do have to give the patch name using the -n
flag.
However I'm considering to just use the default name heavy
or something when it is not supplied.
I've also ran into the issue of forgetting the name flag and sometimes I just really don't care to name the export I'm working on or testing.
Thank you for the report to remind me to find a permanent fix ;)
Ok setting a default name for the arguments now.
This will be available in pip on the next release. Until then you will have to give -n <somename>
argument when compiling.
Ok, great! It is just a bit discouraging, when you start using the tool and it gives you some python error with the simplest patch and command from the documentation :-)
Just use it with the -n/--name
flag for now :)