Windows

[mpharrigan]

I can recreate Joy's issue

c:\>msmb
failed to create process.

During install I got the following worrying error message

C:\Users\>conda install msmbuilder
Fetching package metadata: ...
Solving package specifications: .
Package plan for installation in environment C:\Anaconda:

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    conda-3.3.2                |           py27_0         119 KB
    msmbuilder-2.8.2           |       np18py27_0        12.9 MB
    ------------------------------------------------------------
                                           Total:        13.1 MB

The following packages will be UN-linked:

    package                    |            build
    ---------------------------|-----------------
    conda-3.3.1                |           py27_0
    msmbuilder-2.8.1           |       np18py27_0

The following packages will be linked:

    package                    |            build
    ---------------------------|-----------------
    conda-3.3.2                |           py27_0   hard-link
    msmbuilder-2.8.2           |       np18py27_0   hard-link

Proceed ([y]/n)? y

Fetching packages ...
conda-3.3.2-py27_0.tar.bz2 100% |###################| Time: 0:00:00 133.66 kB/s
msmbuilder-2.8.2-np18py27_0.tar.bz2 100% |##########| Time: 0:02:04 108.53 kB/s
Extracting packages ...
[      COMPLETE      ] |#################################################| 100%
Unlinking packages ...
[      COMPLETE      ] |#################################################| 100%
Linking packages ...
[      COMPLETE      ] |#################################################| 100%
The filename, directory name, or volume label syntax is incorrect.

Third thing, the installation is different now. Whereas it used to create a batch file (msmb.bat) that called python on the associated script (msmb-script.py), now it has an *.exe file (msmb.exe) instead, as well as the script (msmb-script.py) All the scripts are like this now, and none of them work

[mpharrigan]

Stack overflow has this to say:

http://stackoverflow.com/questions/17373265/pip-easy-install-failure-failed-to-create-process

Although I did not rename anything

[schwancr]

http://jackguide.com/the-filename-directory-name-or-volume-label-syntax-is-incorrect/

[schwancr]

Where is the script located?

[schwancr]

It could also be a permissions issue. Is there a sudo equivalent in windows?

http://edn.embarcadero.com/article/27550

[schwancr]

Windows 7 has made user privileges a huge hassle. It's intended to protect the average user but gives developers headaches.

Run cmd.exe as Admin (right-click on the .exe and then select "Run as Administrator") and this problem should be solved.

from: http://stackoverflow.com/questions/5494080/how-do-i-force-easy-install-exe-to-print-output-in-the-current-command-window

[mpharrigan]

I tried reinstalling via a "run as administrator" command prompt (equivalent of sudo) and it still doesn't work

I also tried installing it in my python3 environment, and it also didn't work

[mpharrigan]

The scripts are in C:\Anaconda\Scripts, which is in the path

[schwancr]

This might be related:

https://github.com/conda/conda/issues/396

[schwancr]

http://www.maphew.com/Python/python-fixit-snippets/

[rmcgibbo]

Let me boot up my VM. I probably did something dump.

[rmcgibbo]

Can anyone try the conda linux and mac binaries I made from the same release?

[mpharrigan]

@rmcgibbo, is it possible to configure the conda package to use that *.bat scheme instead of *.exe. That seemed to work more robustly

[mpharrigan]

For reference, all the other scripts in anaconda seem to use the .bat paradigm. Except sphinx, which has both, but windows will use the .bat file over the *.exe

[rmcgibbo]

@rmcgibbo, is it possible to configure the conda package to use that .bat scheme instead of .exe. That seemed to work more robustly

Do you have a link or anything? I wasn't explicitly trying to use one over the other...

[rmcgibbo]

[ I can reproduce the problem on my own VM that I built these packages on -- so sorry about that everyone for releasing garbage ]

[rmcgibbo]

FWIW, there are a lot of "reference" conda recipes here:

https://github.com/conda/conda-recipes

[schwancr]

Here's a discussion of all of this: http://matthew-brett.github.io/pydagogue/installing_scripts.html

[rmcgibbo]

yeah, and the msmbuilder setup.py is using the console_scripts part of setuptools. http://matthew-brett.github.io/pydagogue/installing_scripts.html#setuptools-and-console-script-entry-points

[schwancr]

http://matthew-brett.github.io/pydagogue/installing_scripts.html#a-fairly-simple-windows-bat-file-solution

That uses the bat file. It seems fairly simple. I don't really understand why the other one isn't working though, so it's not obvious to me what to do.

Btw, is it possible to remotely access your windows VM @rmcgibbo ?

[rmcgibbo]

So when you install from source (setup.py install) on windows it works. So the conda build step (that runs setup.py and then packages it up) is the problem.

[rmcgibbo]

I don't think so. You can maybe scp the whole virtual disk though?

[schwancr]

We now depend on setuptools at install time to write the console script stuff

So how does conda interact with the console script stuff? If they're actually written during the setup.py install step then conda never rewrites them?

[rmcgibbo]

I just tried rebuilding the package, and it "seems" to work now...

[rmcgibbo]

the binstar upload client doesn't seem to work on windows. it just hangs. I uploaded one of the packages to here: https://drive.google.com/file/d/0BzcoWVF3dFTfRF9DNk4xS3RIdUE/edit?usp=sharing

[rmcgibbo]

if you have windows, try downloading the file and then just conda install it.

[mpharrigan]

I don't have permission to get that file

[rmcgibbo]

you should now.

[mpharrigan]

It still doesn't work for me. I uninstalled, ran conda clean, and installed from the tarbal

[rmcgibbo]

With the same error, or a different one?

[mpharrigan]

Sorry, should have been clear. Same error (Failed to create process). Although there's no "linking errors" anymore from conda during install

[rmcgibbo]

Can you try building the packages on your machine then? Clone https://github.com/rmcgibbo/conda-recipes and run conda install conda-build; python build-all-msmbuilder.py

[mpharrigan]

I'll try that. I just installed from pip and it works fine from that

[mpharrigan]

Wait, where is build-all-msmbuilder.py

[rmcgibbo]

Oops. I forgot it. It's there now.https://github.com/rmcgibbo/conda-recipes/commit/6c54e2509dccce7bed8d2f27dfffb9caa41b3a02

[mpharrigan]

Alright it's taking forever and I have to go to dinner

[mpharrigan]

It looks like it's stuck in a loop?

[rmcgibbo]

I built all four binaries with that script and pushed them to binstar (one of those 4 is the one on google drive). I then deleted all of the packages from my machine and ran conda install msmbuilder, which download the file from binstar and it worked. This was on windows 7.

I also tried installing from binstar on my XP virtual machine, and that failed. With the same original error.

[mpharrigan]

Ok the build finally finished. It l don't know where any of the packages ended up, but it created a virtualenv _build and msmb works after activating that env

[mpharrigan]

I gotta go now though