Re: conda/anaconda and pip3 (pip)
Às 17:39 de 03/12/18, Paulo da Silva escreveu: Well ... further clarification ... > Hi! > > I have an environment created with conda (anaconda3). > There is a package that is unavailable in conda. The package is sklearn (import sklearn). - Look below before comment pls. > Installing it with pip3, with conda env activated, the installation goes > to .local/bin and .local/lib in my home dir (BTW I'm running linux > kubuntu 18.04). This is because I used pip3. pip3 is from the system. Inside conda MyPy (my conda environment) only pip is available. This "pip" works with python3. So: - I uninstalled sklearn using pip3 and installed it with pip. - This sucessfully installed sklearn (a very small bunch of small files). import sklearn didn't work! I uninstalled sklearn with pip. Then I searched for sklearn from the top level of anaconda3 dir. I find few of them, all global to anaconda3 but out of the environment. This means that these packages are not seen from the environment. Besides sklearn was inside the scikit-learn package. So I activated MyPy (my environment) and did conda install scikit-learn Now everything is working and coherent. Still confused, however ... Thank you all. Regards. --- news://freenews.netfront.net/ - complaints: n...@netfront.net --- -- https://mail.python.org/mailman/listinfo/python-list
Re: conda/anaconda and pip3 (pip)
Às 19:39 de 02/01/19, Hartmut Goebel escreveu: > Am 03.12.18 um 18:39 schrieb Paulo da Silva: >> This also has a bad side effect! It reinstalls there some depedencies >> already installed in the conda created environment! >> >> Is there a way to avoid this situation? > > Try whether `pyvenv --system-site-packages` suites you. > I need to use conda for this. I need anaconda because it has all stuff to work with GPUs. Otherwise I'd need to install lots of SW. One package, for example, requires registration at Nvidia. It also difficult to determine a common base of compatible versions. Thanks for responding. -- https://mail.python.org/mailman/listinfo/python-list
Re: conda/anaconda and pip3 (pip)
Às 19:54 de 09/12/18, Tim Williams escreveu: > On Saturday, December 8, 2018 at 10:13:14 PM UTC-5, Monte Milanuk wrote: >> Did you find any solution(s)? > > I usually just lurk and read on this list. I don't reply since there's > usually more competent people that regularly post helpful answers. (I lurk to > learn from them!) > > If no one's replied yet, I'll give it my 2 cents ... > > Without being a pip expert, I see from 'pip install -h' that you can specify > where you want the package to be installed. > > Install Options: ... > path or a VCS url. > -t, --target Install packages into . By default this > will not replace existing files/folders in > . Use --upgrade to replace existing > packages in with new versions. ... > > I'm thinking the the --target option may be the solution. > I don't think this is a solution. It seems that there is no really solutions at all. (ana)conda has its own dependencies management. Playing with pip just seems to cause dependencies problems, eventually. So far, I have not found any problems, probably because the newer modules are backwards compatible. Thanks for responding. -- https://mail.python.org/mailman/listinfo/python-list
Re: conda/anaconda and pip3 (pip)
Am 03.12.18 um 18:39 schrieb Paulo da Silva: > This also has a bad side effect! It reinstalls there some depedencies > already installed in the conda created environment! > > Is there a way to avoid this situation? Try whether `pyvenv --system-site-packages` suites you. -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: https://www.goe-con.de/blog/das-fass-ist-voll-grunde-linux-201asystemd2018-zu-meiden Kolumne: https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2011-10-aus-der-schublade-in-die-koepfe -- https://mail.python.org/mailman/listinfo/python-list
Re: conda/anaconda and pip3 (pip)
On Saturday, December 8, 2018 at 10:13:14 PM UTC-5, Monte Milanuk wrote: > Did you find any solution(s)? I usually just lurk and read on this list. I don't reply since there's usually more competent people that regularly post helpful answers. (I lurk to learn from them!) If no one's replied yet, I'll give it my 2 cents ... Without being a pip expert, I see from 'pip install -h' that you can specify where you want the package to be installed. Install Options: -r, --requirement Install from the given requirements file. This option can be used multiple times. -c, --constraint Constrain versions using the given constraints file. This option can be used multiple times. --no-deps Don't install package dependencies. --pre Include pre-release and development versions. By default, pip only finds stable versions. -e, --editableInstall a project in editable mode (i.e. setuptools "develop mode") from a local project path or a VCS url. -t, --target Install packages into . By default this will not replace existing files/folders in . Use --upgrade to replace existing packages in with new versions. --user Install to the Python user install directory for your platform. Typically ~/.local/, or %APPDATA%\Python on Windows. (See the Python documentation for site.USER_BASE for full details.) --root Install everything relative to this alternate root directory. --prefix Installation prefix where lib, bin and other top-level folders are placed -b, --buildDirectory to unpack packages into and build in. Note that an initial build still takes place in a temporary directory. The location of temporary directories can be controlled by setting the TMPDIR environment variable (TEMP on Windows) appropriately. When passed, build directories are not cleaned in case of failures. --src Directory to check out editable projects into. The default in a virtualenv is "/src". The default for global installs is "/src". -U, --upgrade Upgrade all specified packages to the newest available version. The handling of dependencies depends on the upgrade-strategy used. --upgrade-strategy Determines how dependency upgrading should be handled [default: only-if-needed]. "eager" - dependencies are upgraded regardless of whether the currently installed version satisfies the requirements of the upgraded package(s). "only-if-needed" - are upgraded only when they do not satisfy the requirements of the upgraded package(s). --force-reinstall Reinstall all packages even if they are already up-to-date. -I, --ignore-installed Ignore the installed packages (reinstalling instead). --ignore-requires-pythonIgnore the Requires-Python information. --no-build-isolationDisable isolation when building a modern source distribution. Build dependencies specified by PEP 518 must be already installed if this option is used. --install-option Extra arguments to be supplied to the setup.py install command (use like --install- option="--install-scripts=/usr/local/bin"). Use multiple --install-option options to pass multiple options to setup.py install. If you are using an option with a directory path, be sure to use absolute path. --global-optionExtra global options to be supplied to the setup.py call before the install command. --compile Compile Python source files to bytecode --no-compileDo not compile Python source files to bytecode --no-warn-script-location Do not warn when installing scripts outside PATH --no-warn-conflicts Do not warn about broken dependencies --no-binary Do not use binary packages. Can be supplied multiple times, and each time adds to the existing value. Accepts either :all: to disable all binary packages, :none: to empty the set, or one or more package names with commas between them. Note that some packages are tricky to compile and may fail to install when this option is used on them. --only-binary Do not use source packages. Can be supplied multiple times, and each time adds to the existing value. Accepts either :all: to disable a
Re: conda/anaconda and pip3 (pip)
Did you find any solution(s)? -- https://mail.python.org/mailman/listinfo/python-list
conda/anaconda and pip3 (pip)
Hi! I have an environment created with conda (anaconda3). There is a package that is unavailable in conda. Installing it with pip3, with conda env activated, the installation goes to .local/bin and .local/lib in my home dir (BTW I'm running linux kubuntu 18.04). This also has a bad side effect! It reinstalls there some depedencies already installed in the conda created environment! Is there a way to avoid this situation? Thanks for any help. -- https://mail.python.org/mailman/listinfo/python-list
