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

File paths do not always work for Windows. #82

Open
marcverhagen opened this issue Mar 8, 2018 · 0 comments
Open

File paths do not always work for Windows. #82

marcverhagen opened this issue Mar 8, 2018 · 0 comments

Comments

@marcverhagen
Copy link
Member

marcverhagen commented Mar 8, 2018

This is a more general issue than #42.

There are know problems in Windows with file paths. Spaces in paths have been an issue and it looks like dashes in paths are a problem too, even though the way the problem manifests itself seems to be different across Windows versions (which I actually don't believe, but that is what first experiments show).

One reported problem is that if the name of the repository is ttk-master you can get an error reading the config.txt file:

capture1

I could not replicate this on a Windows 7 laptop, but I did get a classifier error:

ERROR: CLASSIFIER error:
        <type 'exceptions.IndexError'>
        pop from empty list

Also, on Windows a command line invocation requires for example the input file to have forward slashes, which is not the natural windows way.

In general all code dealing with input and output needs to be reviewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant