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

Sugar would not start when a file new.py was present #893

Open
1 task
quozl opened this issue Dec 11, 2019 · 2 comments
Open
1 task

Sugar would not start when a file new.py was present #893

quozl opened this issue Dec 11, 2019 · 2 comments

Comments

@quozl
Copy link
Contributor

quozl commented Dec 11, 2019

When a user had a file new.py in home directory containing an import that could not be satisfied, Sugar would not start. This was because Xapian was imported by Sugar, and Xapian had a "from new import something".

  • check the Python module search path for Sugar; should it really search the home directory for modules?
@srevinsaju
Copy link
Member

Tested, I couldn't reproduce the error. The paths did not include the home directory, maybe, the Xapian package got updated to fix the error.

@quozl
Copy link
Contributor Author

quozl commented Feb 10, 2020

I was able to reproduce. The Python path included the current working directory, which when Sugar starts is the home directory. If you think Xapian was changed, please find the change in Xapian.

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

2 participants