Problem setting up development build

[Jukka Lehtniemi]

Hello!

I'm trying to setup development build as instructed in:
https://github.com/conda/conda/blob/master/README.rst#contributing

I have a fresh Miniconda2 install (Linux 64). The setup seems to run ok but then when I am running any conda command it will raise the following error:
    ImportError: Entry point ('console_scripts', 'conda') not found

I wonder if anybody knows what the problem might be. Full install log and error trace below.

Best regards,

Jukka

        $ ~/miniconda2/bin/python setup.py develop
        running develop
        running egg_info
        writing conda.egg-info/PKG-INFO
        writing top-level names to conda.egg-info/top_level.txt
        writing dependency_links to conda.egg-info/dependency_links.txt
        writing entry points to conda.egg-info/entry_points.txt
        reading manifest file 'conda.egg-info/SOURCES.txt'
        reading manifest template 'MANIFEST.in'
        warning: no previously-included files matching '*' found under directory 'tests'
        writing manifest file 'conda.egg-info/SOURCES.txt'
        running build_ext
        Creating ~/miniconda2/lib/python2.7/site-packages/conda.egg-link (link to .)
        Adding conda 4.2.12.dev562+08d71a7 to easy-install.pth file
        Installing conda script to ~/miniconda2/bin
        Installing conda-env script to ~/miniconda2/bin
        Installing activate script to ~/miniconda2/bin
        Installing activate.sh script to ~/miniconda2/bin
        Installing activate.csh script to ~/miniconda2/bin
        Installing deactivate script to ~/miniconda2/bin
        Installing deactivate.sh script to ~/miniconda2/bin
        Installing deactivate.csh script to ~/miniconda2/bin
        Installing whichshell_args.bash script to ~/miniconda2/bin
        Installing whichshell_ps.bash script to ~/miniconda2/bin
        Installing whichshell.awk script to ~/miniconda2/bin
        Installing envvar_cleanup.bash script to ~/miniconda2/bin

        Installed ~/repos/conda
        Processing dependencies for conda==4.2.12.dev562+08d71a7
        Finished processing dependencies for conda==4.2.12.dev562+08d71a7

        $ conda
        Traceback (most recent call last):
          File "~/miniconda2/bin/conda", line 11, in <module>
            load_entry_point('conda', 'console_scripts', 'conda')()
          File "~/miniconda2/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/pkg_resources/__init__.py", line 565, in load_entry_point
          File "~/miniconda2/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/pkg_resources/__init__.py", line 2597, in load_entry_point
        ImportError: Entry point ('console_scripts', 'conda') not found

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.

[Jukka Lehtniemi]

Thank you Martin. However, I'm not quite sure how this script would help to solve the problem. I thought that the Conda install should be self-containing and also based on the README the only extra requirement was git. Isn't that the case?

Also to me the error does not look like a missing requirement but rather setuptools version mismatch or something alike. Maybe the setuptools version (27.2.0) that comes with current Miniconda installation is not compatible with the development version? If so, what version should I use?

 BR, Jukka

On Wed, Nov 30, 2016 at 2:40 PM, martin <martin.de...@gmail.com> wrote:

If you have root access to the machine and you're using a debian variant then have a look at this.

https://github.com/kirk86/devdotfiles/tree/master/ubuntu

It creates a development environment probably with more than what you need, but you can always comment parts that you don't need.

The downside is that you need to have root privileges on the machine, it is required for installing some packages unfortunately.

--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/CAGzU5MWr-DZEbJAooGH0EEhJquafc7B%3DbsqPK1WoVEA5%2Bhw8uA%40mail.gmail.com.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

[Ray Donnelly]

You probably need to activate your root environment:

source ~/miniconda2/bin/activate

.. ensure it worked by:

which python

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/CAGzU5MXpUKi1q-1h-Fkev7vuiMD4vNqaHzw5v-R_s%3DEaf7rDQg%40mail.gmail.com.

[Jukka Lehtniemi]

Thanks for the suggestion but unfortunately it seems that sourcing the activate script fails with the very same import error.

However, I managed to fix the problem by using older Miniconda installer and using pip to install package "enum" that was missing:

    $ bash Miniconda2-4.1.11-Linux-x86_64.sh -f

    $ export PATH=~/miniconda2/bin:$PATH
    $ python setup.py develop
    $ pip install enum

BR, Jukka