8000 Specifying output directory and other compilation options for all Coconut files in the project · Issue #768 · evhub/coconut · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Specifying output directory and other compilation options for all Coconut files in the project #768
Closed
@kxmh42

Description

@kxmh42

Say I have two files.
file1.coco:

import file2
file2.func()

file2.coco:

def func():
    pass

Now if I want to run file1.coco, e.g. with coconut-run -l file1.coco, the -l option only applies to file1.coco and I have no way of changing the compilation options for file2.coco, is that right?

Specifically, what I'm seeking is a method to automatically redirect all compiled Python files to a designated subdirectory like __pycache__. By doing so, it would help keep them organized and easy to remove or gitignore. That's similar to the rationale behind placing .pyc files separately in __pycache__ rather than mixing them with the .py files in a single directory.

Not sure if that's one issue, or two related ones.

PS. Thanks for your great work. Coconut is awesome!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0