These are chat archives for spyder-ide/public

5th
Apr 2019
Mauricio O Calvao
@mocalvao
Apr 05 15:01
hi there i would like to try Spyder 4. To that end, I have followed the instructions in: https://docs.spyder-ide.org/installation.html under the heading "Installing a development build". I guess step 1 was ok, as well as steps 2 and 3. That is, I do seem ho have a new proper conda environment prepared for Spyder 4 testing, and I did create a cloned spyder directory under my /home/orca account (in a Debian Linux PC). When I tried step 4, to effectively run Spyder 4, via the bootstrap.py script, the following happened:
Executing Spyder from source checkout
Traceback (most recent call last):
File "bootstrap.py", line 122, in <module>
from spyder.utils.vcs import get_git_revision
File "/home/orca/spyder/spyder/utils/vcs.py", line 17, in <module>
from spyder.config.base import running_under_pytest
File "/home/orca/spyder/spyder/config/base.py", line 30, in <module>
from spyder.utils import encoding
File "/home/orca/spyder/spyder/utils/encoding.py", line 23, in <module>
from atomicwrites import atomic_write
ModuleNotFoundError: No module named 'atomicwrites'
What have I done wrong to try Spyder 4?
Carlos Cordoba
@ccordoba12
Apr 05 15:05

@mocalvao, those instructions are not up to date. These are:

https://github.com/spyder-ide/spyder/blob/master/CONTRIBUTING.md

Mauricio O Calvao
@mocalvao
Apr 05 15:25
@cordoba I will try the new instructions. Thanks
jproy
@jproy
Apr 05 16:55
Hi there ! Problem. I made with my Mac terminal and conda a new environment parsing. I activated parsing. Then I installed pip in this env, then with pip installed the package sly, then installed spyder. All ok, Spyder 3.3.3. runs fine with Python 3.7.3 and IPython 7.4.0. With idleI can import sly but not with Spyder. Where is the problem ? I should say that this worked before, but I had to remove the parsing env for a test. Then reinstalled it with the same protocol but now sly cannot be imported from Spyder. Any help ? (maybe IPython version ?...)
CAM Gerlach
@CAM-Gerlach
Apr 05 17:39
@mocalvao Sorry, I really need to update them.
CAM Gerlach
@CAM-Gerlach
Apr 05 17:45
@jproy As we state various places, we aren't usually able to provide individual help for installation issues with pip that aren't fixable on Spyder's end. These sorts of issues are why we recommend always using conda to install Spyder (and other packages, if at all possible). One potential issue to rule out is that if you install pip after you activate the environment, instead of when you create it (with conda create -n python, for example), then pip from base will be used instead of the correct one from that environment and thus install packages incorrectly. To ensure this doesn't happen, always create new environments with the above command to make sure pip is installed from the get-go. In case you have an existing environment and install pip, install it in the env, and then deactive it and re-activate it again and the issue should be avoided.
@jproy Beyond that, please read our guide to working with packages and environments with Spyder for more details about handling this situation with installing packages and multiple environments.
jproy
@jproy
Apr 05 18:27
@CAM-Gerlach Well, I installed pipin the parsingenv, and which pip tells me that the pip used to install slyis /Users/roy/anaconda3/envs/parsing/bin/pip. Moreover the slypackage does not come with any condainstall.
jproy
@jproy
Apr 05 18:34
@CAM-Gerlach OK, I read your Guide, and used the sys.executable trick, which show me that Python was not the one in anaconda3/envs/parsing/bin, I corrected this replacing with default interpreter. Thanks.
Mauricio O Calvao
@mocalvao
Apr 05 19:16
What I did as per Cordoba's suggestion above was: (1) cloned spyder's git repo, right under my user directory /home/orca; (2) created a new conda environment (spyder-dev) with python=3; (3) I activated the new conda env; (4) I changed to the cloned spyder directory, where the file requirements/conda.txt resides; (5) installed the spyder dependencies into the spyder-dev conda environment; (6) installed the Spyder 4 master branch into conda, via spyder-kernels=1.* , and then (7) finally issued python bootstrap.py from the spyder-dev environment, to launch Syper 4 successfully. Thank you all! It is, however, a little bit contrived and I think the directions/instructions should be updated and streamlined
Mauricio O Calvao
@mocalvao
Apr 05 19:21
I would like to take the opportunity and ask whether there is any estimate for the official release of a stable Spyder 4 version?
CAM Gerlach
@CAM-Gerlach
Apr 05 19:25
@mocalvao This is primarily intended for developers only, who are familiar with advanced methods of installing development versions of packages. We should be releasing Spyder 4 beta 2 containing all these fixes and improvements as soon as we have fixed the remaining bugs in the brand new code completion/introspection/help/analysis infrastructure, which should hopefully be very shortly. You'll be able to install it simply by running conda install -c spyder-ide spyder=4 in whatever environment you want to install it in, and run it with the normal spyder, from Navigator or the Start Menu shortcut Spyder creates on Windows.
Mauricio O Calvao
@mocalvao
Apr 05 19:37
@CAM-Gerlach I will guess this still means this first semester, right? Thanks a lot again!
CAM Gerlach
@CAM-Gerlach
Apr 05 19:39
Hopefully...its taken much more time to fix all the bugs than anticipated and it didn't help that the main contributor had to leave the project, but it should hopefull be soon...™