You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, compiling a Chapel module into a Python module will always generate an a_out.py file which the user must move to a different filename if they don't like the name a_out.py. It would be nice to be able generate a user-defined name from the pych command, so that this step can be skipped.
First idea, should it look like this? What would be better syntax?
pych --compile blah.chpl -o blah.py
The text was updated successfully, but these errors were encountered:
What if the default name was the same as the chapel file replacing .chpl with .py? It probably should do some name massaging to ensure the python module name is valid and importable (e.g. substitute _ for .). For example:
At the moment, compiling a Chapel module into a Python module will always generate an a_out.py file which the user must move to a different filename if they don't like the name a_out.py. It would be nice to be able generate a user-defined name from the pych command, so that this step can be skipped.
First idea, should it look like this? What would be better syntax?
pych --compile blah.chpl -o blah.py
The text was updated successfully, but these errors were encountered: