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

Running the tests leaves compiled bytecode in the tools folder #179

Closed
lazka opened this issue Aug 1, 2014 · 1 comment
Closed

Running the tests leaves compiled bytecode in the tools folder #179

lazka opened this issue Aug 1, 2014 · 1 comment
Labels
bug

Comments

@lazka
Copy link
Member

@lazka lazka commented Aug 1, 2014

Originally reported by: Wieland Hoffmann (Bitbucket: mineo, GitHub: mineo)


Running the tests creates tools/{mid3v2,moggsplit,mutagen-{inspect,pony}}c which are compiled Python bytecode. This is annoying because first running the tests and then calling python2 setup.py install will copy those files to to bin/ dir.


@lazka

This comment has been minimized.

Copy link
Member Author

@lazka lazka commented Aug 5, 2014

Original comment by Christoph Reiter (Bitbucket: lazka, GitHub: lazka):


tests: dont write byte code files for tool scripts; setup.py: don't use glob to find scripts to install. (Fixes #179)

@lazka lazka added minor bug labels Apr 7, 2016
@lazka lazka closed this Apr 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.