Skip to content
New issue

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

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

Already on GitHub? # to your account

Resolve long tree string problem on Windows #258 #405

Merged
merged 1 commit into from
Jun 29, 2019
Merged

Resolve long tree string problem on Windows #258 #405

merged 1 commit into from
Jun 29, 2019

Conversation

davidhwyllie
Copy link
Contributor

There is a problem in which large newick trees fail to load from strings in windows, as described in issue #258. This arises because the existing read_newick code code performs os.path.exists() on a string passed to it. This string may either be a path to a file, or a newick file's contents.

On windows, os.path.exists() fails with very long strings, because very long strings causes stat to fail.

This proposed fix
a) includes a self contained unit test demonstrating the problem
b) traps for the ValueError raised when stat fails, and regards such a failure as evidence that the user has supplied a newick tree content, not a file name.

@davidhwyllie
Copy link
Contributor Author

Pull request is at
#405

@jhcepas jhcepas merged commit 068df09 into etetoolkit:master Jun 29, 2019
@davidhwyllie
Copy link
Contributor Author

Dear Jaime

I'm not clear whether these failures are anything to do with the change - e.g.

sh: 0: Can't open /etc/init.d/xvfb
The command "sh -e /etc/init.d/xvfb start" failed and exited with 127 during .

Please let me know if more input would be helpful.
Thank you
David

@jhcepas
Copy link
Member

jhcepas commented Jul 1, 2019 via email

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

Successfully merging this pull request may close these issues.

2 participants