Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support compiling to arbitrary file names #382

Closed
evhub opened this Issue Jan 4, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@evhub
Copy link
Owner

evhub commented Jan 4, 2018

Want to be able to compile OriginalName.coco to OriginalName_coco.py. Current proposed implementation would be to support accomplishing that via coconut OriginalName.coco OriginalName_coco.py.

@evhub evhub added the enhancement label Jan 4, 2018

@evhub evhub added this to the v1.3.2 milestone Jan 4, 2018

evhub added a commit that referenced this issue Jan 4, 2018

@ArneBachmann

This comment has been minimized.

Copy link
Contributor

ArneBachmann commented Jan 4, 2018

Very good point! This would allow to track pure Python files while not tracking Coco-generated python files.

@evhub

This comment has been minimized.

Copy link
Owner Author

evhub commented Jan 4, 2018

@ArneBachmann That's the idea, though the big remaining problem is that if you do that you have to import everything with import file_coco as file instead of import file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.