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.

Sign up for GitHub

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

Jump to bottom

Re-spawning after update uses different python executable #8

Open
imagejan opened this issue Jun 15, 2021 · 0 comments
Open

Re-spawning after update uses different python executable #8

imagejan opened this issue Jun 15, 2021 · 0 comments

Comments

@imagejan
Copy link
Member

I noticed that after the auto-updater re-spawns the FAIM-robocopy process, it seems to run on a different Python executable. On my system, I got a SyntaxWarning: "is not" with a literal. (see #7) after the updater fetched the latest version. That warning was introduced with Python 3.8, while the python version of my conda environment is supposed to be 3.6.
@imagejan imagejan changed the title Re-spawing after update uses different python executable Re-spawning after update uses different python executable Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@imagejan