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

Windows error messages: how to help? #61

Closed
ijstokes opened this issue Nov 13, 2018 · 4 comments
Closed

Windows error messages: how to help? #61

ijstokes opened this issue Nov 13, 2018 · 4 comments
Labels
locked [bot] locked due to inactivity

Comments

@ijstokes
Copy link

ijstokes commented Nov 13, 2018

I realize conda-pack claims that it doesn't support Windows, however I noticed enough on_win entries in the code that I thought I'd give it a go. I have latest conda-pack installed from source, which I believe means that thanks to #12 and #48 should have a reasonable chance of working. However I get the errors below:

> conda pack -n test -o test-deps.zip
Collecting packages...
CondaPackError: Failed to determine path to environment: 'test'. This may be due to conda not being on your PATH. The full error is below:

b''

I can tell you conda is definitely on my path:

>where conda
C:\Users\USERNAME\AppData\Local\Continuum\anaconda3\Library\bin\conda.bat
C:\Users\USERNAME\AppData\Local\Continuum\anaconda3\Scripts\conda.exe

>conda -V
conda 4.5.11

One possibility: USERNAME has a space in it. That is, unfortunately, unavoidable.

@jcrist
Copy link
Collaborator

jcrist commented Nov 13, 2018

Windows support was added in #48, and will be part of the next release. Since you're using master, things should have worked fine. I suspect you're right about the issue being how we're shelling out to conda. Does it work if you pass the path to your environment?

conda-pack -p relative_or_absolute_path

cc @mcg1969.

@jcrist
Copy link
Collaborator

jcrist commented Nov 30, 2018

@ijstokes, any update on this?

@mcg1969
Copy link
Contributor

mcg1969 commented Jul 3, 2020

Now that the Windows support seems to be in moderately common use I'm going to close this, because I think it's likely stale. But please feel free to reopen or file a new issue if we can get a reproducible case.

@mcg1969 mcg1969 closed this as completed Jul 3, 2020
@rhilker
Copy link

rhilker commented Oct 7, 2021

I also still have the same issue here.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Oct 8, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

No branches or pull requests

4 participants