-
Notifications
You must be signed in to change notification settings - Fork 15
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
new dot release please? #21
Comments
Sorry for noise in other issue. I've since deleted the comment, and am now bumping here -- however I just this moment found another bug which should be fixed first. Opening mew issue in a few secs. |
@maphew very sorry for the long delay. I will tag and push 1.7.1. Honestly, I'm not sure we have the best solution for handling conda systems that refuse to run with a non-base environment. It's sort of unclear what pyshortcuts should do with respect to environments - one specifies a python executable, but there really isn't much more we can really do beyond that if the environment changes. I'm also somewhat unsure about #20. Ideas, PRs, etc greatly appreciated! |
totally up to up you of course, but I'd appreciate a new dot release so that a project I'm using pyshortcuts as a dependency in can take advantage of the recent conda envrunner and base-name-agnostic env fix. v1.7.1 would be fine (ie: wouldn't need to be 1.8)
If there's something else you'd like to put in before a new one, let me know how I can help. :-)
The text was updated successfully, but these errors were encountered: