Editor autocompletion and help extraction not working in Spyder 3.1.4

[jrast]

I have updated Spyder (pip install -U spyder) to 3.1.4 and the autocompletion in the editor stopped working. In the IPython console it's still working, but not in the editor.

Please provide any additional information below

• Spyder Version: 3.1.4
• Python Version: 3.5.3 32-bit
• Qt Version: 5.8.0
• PyQt Version: 5.8.1
• Operating system: Windows 7

Dependencies

jedi >=0.9.0 : 0.10.2 (OK) matplotlib >=1.0 : 2.0.0 (OK) nbconvert >=4.0 : 5.1.1 (OK) numpy >=1.7 : 1.11.3 (OK) pandas >=0.13.1 : 0.19.2 (OK) pep8 >=0.6 : 1.7.0 (OK) pyflakes >=0.6.0 : 1.5.0 (OK) pygments >=2.0 : 2.2.0 (OK) pylint >=0.25 : 1.7.1 (OK) qtconsole >=4.2.0: 4.3.0 (OK) rope >=0.9.4 : 0.9.4-1 (OK) sphinx >=0.6.6 : 1.5.5 (OK) sympy >=0.7.3 : None (NOK)

[CoderCoderCoder]

Interestingly I noticed the following - even after I got my problem fixed after uninstalling enum34 package, it comes back again after my MacBook goes into a sleep mode. Afterwards only a restart of Spyder helps. I've also tried the workaround described by @minzastro, but it didn't solve the issue.

The workaround itself is the following: "Interestingly, changing spyder/utils/help/conf.py seems to solve the problem:

html_use_smartypants = False # I commented out this

smart_quotes=False # and added that

I run on jedi 0.10.2, will test for jedi 0.11 later."

[ccordoba12]

@CoderCoderCoder, thanks for tip. Good thing we already implemented this fix in PR #6575, which will be part of our 3.2.8 release.

[CoderCoderCoder]

@ccordoba12 You are welcome, all credits go to @minzastro anyway :). Any thoughts why it stops working after a notebook went into a sleep mode, so only a Spyder restart helps? It's really annoying :(..... With both settings (html_use_smartypants and smart_quotes) I have absolutely the same problem.

[cocoaaa]

Great to hear about the fix! @ccordoba12, when do you think 3.2.8 will be released?

[ccordoba12]

@cocoaaa, hopefully tomorrow.

[BRdubW]

I am running spyder 3.2.8 and am still having this problem.

No tab completion, no info, no goto, no help from editor, but these work in console.

Python 2.7.5 64bits, Qt 4.8.5, PyQt4 (API v2) 4.10.1 on Linux (Centos 7.4 64bit)

IPython >=4.0;<6.0: 5.5.0 (OK) cython >=0.21 : 0.27.3 (OK) jedi >=0.9.0 : 0.11.1 (OK) nbconvert >=4.0 : 5.3.1 (OK) numpy >=1.7 : 1.7.1 (OK) pandas >=0.13.1 : 0.17.1 (OK) psutil >=0.3 : 5.4.3 (OK) pycodestyle >=2.3 : 2.3.1 (OK) pyflakes >=0.5.0 : 1.6.0 (OK) pygments >=2.0 : 2.2.0 (OK) pylint >=0.25 : 1.8.2 (OK) qtconsole >=4.2.0 : 4.3.1 (OK) rope >=0.9.4 : 0.10.7 (OK) sphinx >=0.6.6 : 1.7.1 (OK) sympy >=0.7.3 : 1.1.1 (OK)

So I guess mine is a unique enough configuration to not have been solved by 3.2.8.

[cocoaaa]

I upgraded to 3.2.8, but still have the same problem too. The functions start to work again on the editor if I restart spyder, but after running the program for awhile, they stop working. No problem on the console.

python: 3.6.2 64 bits Qt 5.6.2 PyQt 5.5.6 jedit 0.11.1 Mac High Sierra 10.13.3 I installed and upgraded spyder using conda.

[imuhammadjabbar]

Upgraded to 3.2.8(via Anaconda Navigator), autocompletion not working on latest Mac OSX 10.13.4. Tried every solution mentioned in this thread.

[sinapan]

I had the same problem on mac-high sierra-v. 10.13.4, python 3.6 and spyder 3.2.8. Here is what I did to solve it as also mentioned by @halidziya: 1- click on "python" from the toolbox menu on the top 2- click on "PYTHONPATH manager" 3- click on "Add path" 4- navigate to your environment's bin folder (for example: /Users/"username"/anaconda3/envs/"env name"/bin) 5- click "open" and you're done!

[sziem]

Same issue, currently help browser and autocompletion are not working on my system. This has also sometimes occurred in past versions. All packages were installed through conda. The suggested workaround by sinapan does not work.

Edit: Sorry for the noise. Removing enum34 solved it. Check https://github.com/spyder-ide/spyder/issues/5782 for everyone else google brings here...

[ccordoba12]

@BRdubW, @cocoaaa, we're sorry to hear autocompletion is not working for you or stops working after some time. Right now we're working to improve the situation in PR #4751, by using an industry standard architecture for code completion called language server protocol (which is the same one used by the VSCode and Atom editors).

Unfortunately, that will come in Spyder 4, to be released (hopefully) in Q1 of next year. In the meantime, we have to apologize for the inconveniences this is causing you, but there's little we can do to make the situation better in Spyder 3.

[MingboYan]

Same issue with the editor. Mac OS X Yosemite 10.10.5 Spyder 3.2.8 python 3.6.4

alabaster 0.7.10 anaconda-client 1.6.14 anaconda-navigator 1.8.5 anaconda-project 0.8.2 appnope 0.1.0 appscript 1.0.1 asn1crypto 0.24.0 astroid 1.6.3 astropy 2.0.3 attrs 17.4.0 Babel 2.5.3 backports.shutil-get-terminal-size 1.0.0 beautifulsoup4 4.6.0 bitarray 0.8.1 bkcharts 0.2 blaze 0.11.3 bleach 2.1.3 bokeh 0.12.13 boto 2.48.0 Bottleneck 1.2.1 certifi 2018.4.16 cffi 1.11.4 chardet 3.0.4 click 6.7 cloudpickle 0.5.3 clyent 1.2.2 colorama 0.3.9 conda 4.5.3 conda-build 3.4.1 conda-verify 2.0.0 contextlib2 0.5.5 cryptography 2.1.4 cycler 0.10.0 Cython 0.27.3 cytoolz 0.9.0 dask 0.16.1 datashape 0.5.4 decorator 4.3.0 distributed 1.20.2 docutils 0.14 entrypoints 0.2.3 et-xmlfile 1.0.1 fastcache 1.0.2 filelock 2.0.13 Flask 0.12.2 Flask-Cors 3.0.3 gevent 1.2.2 glob2 0.6 gmpy2 2.0.8 greenlet 0.4.12 h5py 2.7.1 heapdict 1.0.0 html5lib 1.0.1 idna 2.6 imageio 2.2.0 imagesize 1.0.0 ipykernel 4.8.0 ipython 6.2.1 ipython-genutils 0.2.0 ipywidgets 7.1.1 isort 4.3.4 itsdangerous 0.24 jdcal 1.3 jedi 0.12.0 Jinja2 2.10 jsonschema 2.6.0 jupyter 1.0.0 jupyter-client 5.2.2 jupyter-console 5.2.0 jupyter-core 4.4.0 jupyterlab 0.31.5 jupyterlab-launcher 0.10.2 lazy-object-proxy 1.3.1 llvmlite 0.21.0 locket 0.2.0 lxml 4.1.1 MarkupSafe 1.0 matplotlib 2.1.2 mccabe 0.6.1 mistune 0.8.3 mpmath 1.0.0 msgpack-python 0.5.1 multipledispatch 0.4.9 navigator-updater 0.1.0 nbconvert 5.3.1 nbformat 4.4.0 networkx 2.1 nltk 3.2.5 nose 1.3.7 notebook 5.4.0 numba 0.36.2 numexpr 2.6.4 numpy 1.14.0 numpydoc 0.8.0 odo 0.5.1 olefile 0.45.1 openpyxl 2.4.10 packaging 17.1 pandas 0.22.0 pandocfilters 1.4.2 parso 0.2.0 partd 0.3.8 path.py 10.5 pathlib2 2.3.0 patsy 0.5.0 pep8 1.7.1 pexpect 4.3.1 pickleshare 0.7.4 Pillow 5.0.0 pip 10.0.1 pkginfo 1.4.1 pluggy 0.6.0 ply 3.10 prompt-toolkit 1.0.15 psutil 5.4.5 ptyprocess 0.5.2 py 1.5.2 pycodestyle 2.4.0 pycosat 0.6.3 pycparser 2.18 pycrypto 2.6.1 pycurl 7.43.0.1 pyflakes 1.6.0 Pygments 2.2.0 pylint 1.8.4 pyodbc 4.0.22 pyOpenSSL 17.5.0 pyparsing 2.2.0 PyQt5 5.9.2 PySocks 1.6.7 pytest 3.3.2 python-dateutil 2.6.1 pytz 2018.4 PyWavelets 0.5.2 PyYAML 3.12 pyzmq 17.0.0 QtAwesome 0.4.4 qtconsole 4.3.1 QtPy 1.4.2 requests 2.18.4 rope 0.10.7 ruamel-yaml 0.15.35 scikit-image 0.13.1 scikit-learn 0.19.1 scipy 1.0.0 seaborn 0.8.1 Send2Trash 1.4.2 setuptools 39.1.0 simplegeneric 0.8.1 singledispatch 3.4.0.3 sip 4.19.8 six 1.11.0 snowballstemmer 1.2.1 sortedcollections 0.5.3 sortedcontainers 1.5.9 Sphinx 1.7.4 sphinxcontrib-websupport 1.0.1 spyder 3.2.8 SQLAlchemy 1.2.1 statsmodels 0.8.0 sympy 1.1.1 tables 3.4.2 tblib 1.3.2 terminado 0.8.1 testpath 0.3.1 toolz 0.9.0 tornado 4.5.3 traitlets 4.3.2 typing 3.6.2 unicodecsv 0.14.1 urllib3 1.22 wcwidth 0.1.7 webencodings 0.5.1 Werkzeug 0.14.1 wheel 0.30.0 widgetsnbextension 3.1.0 wrapt 1.10.11 xlrd 1.1.0 XlsxWriter 1.0.2 xlwings 0.11.5 xlwt 1.2.0 zict 0.1.3

[DougCal]

I'm also getting this problem.

Mac OS High Sierra 10.13.4 Spyder 3.2.8 (latest) Python 3.6.5

I tried versioning back to see if it would work in previous versions, but it just refused.

Object inspection and autocomplete work well in the console, but for whatever reason they refuse to work in the editor. Happy to hear it's being worked on. Thought maybe having another set of specs where the issue is occurring at might help.

[zhouhao27]

Got the same problem without enum34 installed.

[sschuldenzucker]

Same problem, Win 7, Spyder 3.1.4 with conda.

@arman00 , you just saved my day! Was desparate until I saw your comment: This solved the issue, it was all about being in a project. Thank you so much!

I had also tried the tricks around PYTHONPATH above, with no effect.

@anyone: Is it possible to "pin" these workarounds or so, so others with the same issue can find them more easily?

<rant> This was really frustrating to me because it rendered such a beautiful and amazing piece of software basically useless for me. No completion and no help just costs me far too much productivity. I'm sure that many others feel the same way. To make it worse, my organization has very strict IT security rules, so it's by far not as easy as "just try to update all packages" or "just try to downgrade": I have to explain to the IT people which version of which package specifically I need and why.

You guys are doing amazing work: you empower people around the world to do their work better and more easily than they could have wished before and to achieve amazing things. But these people, like, me, now depend on you. And frankly I cannot understand how this problem could slip through before the release, then the bug was incorrectly closed and is still closed even though the issue is clearly not fixed. If you were a company, I'd say you really need to work on your quality control. So perhaps you want to go and look into your processes you do prior to releases, especially testing. Please tell me if I can be of any help. </rant>

[ccordoba12]

To @sschuldenzucker:

You guys are doing amazing work: you empower people around the world to do their work better and more easily than they could have wished before and to achieve amazing things

Thanks.

But these people, like, me, now depend on you

Please read this:

https://mikemcquaid.com/2018/03/19/open-source-maintainers-owe-you-nothing/

We try to do our best to support Spyder users, but you need to be aware that there's no company behind Spyder. Anaconda distributes it but they don't pay us to develop it. And Quansight supports me now to work part time on it, but Spyder is one of many projects they support and Quansight can continue functioning if Spyder would disappear (which is not true for Mathworks in case Matlab would fail as a product).

So we work on Spyder because we really want an IDE like it to do scientific computing. That other people can benefit from our work is great and really rewarding, but we don't have any legal nor any other kind of obligation to support it.

To make it worse, my organization has very strict IT security rules, so it's by far not as easy as "just try to update all packages" or "just try to downgrade": I have to explain to the IT people which version of which package specifically I need and why.

Sorry but this is not our fault. Your company's IT simply don't understand how open source software (OSS) works. They can't treat OSS as commercial products because OSS is evolving constantly (introducing new features and solving old bugs all the time).

And frankly I cannot understand how this problem could slip through before the release, then the bug was incorrectly closed and is still closed even though the issue is clearly not fixed.

This bug was fixed in Spyder 3.2.2 (released in September/2017, i.e. 9 months ago). If you can't update then it's really, really not our problem.

Please tell me if I can be of any help.

Yes, please avoid comments like this in the future, not only here but on any other OSS you use. They are one of the most demotivating things for us developers and maintainers of OSS projects, that mostly contribute our expertise, time and efforts out of good will.

[sschuldenzucker]

@ccordoba12 , thank you for your reply. It seems like we view a few things differently, but I don't think this bug is the right place to discuss this issue. Please feel free to reach out to me directly (steffen.schuldenzucker@gmail.com) in case you want to talk.

Let me just say that I never meant to accuse you or imply that any of this was "your fault". All I wanted to do is present how this issue has affected me and may have affected other users and how one could improve upon it in the future. Re-reading my comment, I see that it could easily be read in a much more negative/aggressive tone. I'm sorry in case I was not clear.

[ccordoba12]

All I wanted to do is present how this issue has affected me and may have affected other users

I understand your frustration, but this bug was fixed a long time ago so your rant is (for me) out of place.

By the way, this bug was caused by trying to address a simple user suggestion. The problem was we were not aware of all the implications that change could have, but we are now.

Sorry for that, but (again) you have to understand this is the nature of OSS.

and how one could improve upon it in the future

We have a lot of tests for code completion and we're moving to a better code completion architecture right now, so the quality assurance part is more or less covered.

You can help us by donating to our Open Collective page.

[CAM-Gerlach]

@sschuldenzucker

Is it possible to "pin" these workarounds or so, so others with the same issue can find them more easily?

Not directly, but they can be added to the Spyder Troubleshooting Guide and FAQ; IIRC I briefly discuss a few code completion issues already.

@ anyone

Just FYI, this doesn't do what you presumably intended—it pings an random user named anyone instead

This was really frustrating to me because it rendered such a beautiful and amazing piece of software basically useless for me.

I'm sorry you had such a rough time with it. Unfortunately, as @ccordoba12 said, we are just a handful of volunteers without institutional support, and between fixing bugs like this in Spyder 3, implementing user-suggested features for Spyder 4, responding to user reports and help requests, and running/managing the broader project and ecosystem, we have nowhere near the funding or resources that would allow for a QA team to fully catch all issues like this (and even QA teams miss features, particularly ones like these that only occur on specific combinations of hardware and software). Furthermore, Spyder 3 is our LTS branch for practical purposes, and thus should always be kept up to date to the latest version to fix critical bugs like this.

As was also mentioned, we have no control over your organization's IT security concerns, valid or not, that prompt them to implement such seemingly draconian practices (that apparently cannot even be worked around by installing Anaconda with non-admin standard user rights). However, we are continuing to improve our test suite to cover more of our code base, and will be deploying a new, proven completion architecture in Spyder 4 based on the same Language Server Protocol as VSCode and Atom, which should make completion, introspection and help more stable, functional, easier to maintain, and make it easy to evolve and support more languages in the future.

Please tell me if I can be of any help.

Besides funding us on OpenCollective, there are many things you can do, even just as a user with no coding, that would really help us out and make Spyder and the community better for you and everyone in the future. Check out our Contributing page for some ideas.

You can also help users troubleshoot their issues (that's how I got started with Spyder), help us expand our docs or our help FAQ, fix one of the many open issues (many of which are quite easy and even have a solution outlined), report other (non-duplicate) bugs, test new releases from Github before they go live, tell your friends about Spyder, write more comprehensive tests for functionality or source code that isn't currently covered, take on a feature or enhancement for Spyder 4, and more. The benefit to being a volunteer project is that anyone is welcome to pitch in, and you seem a knowledgeable and articulate individual who could really be a great help to the project, if you've got some time to spare.

Thanks for sharing your feedback, and hopefully you are able to get this resolved with your IT department and keep on using your favorite IDE. Best of luck!

[Duinobot]

@CoderCoderCoder

The workaround itself is the following: "Interestingly, changing spyder/utils/help/conf.py seems to solve the problem:

html_use_smartypants = False # I commented out this

smart_quotes=False # and added that

Strangely, I commented out #html_use_smartypants = False #, saved, ctrl + I. works but showed version warning. Then I uncommented the above line and it works without any error.

[CAM-Gerlach]

@aisolution Thanks for trying to help. Not sure if you noticed, but the comment you replied to is nearly 5 months old, and as stated in a reply right below that and the user acknowledged, the problem (entirely separate from this one) had already been found (in #6570) and fixed (in #6575) by one of our developers, and released the week after in Spyder 3.2.8.

[Duinobot]

@CAM-Gerlach I'm using Spyder 3.3.0 I found out the object inspector works after I run the script, but it does not work before I press F5.

[CAM-Gerlach]

@aisolution That's a different issue, unless I misunderstand you, Did you try the other solutions on this thread (PYTHONPATH, remove enum34, reset preferences, etc)? Is your help source set to "Console" instead of "Editor" on the top left of the pane?

When sourced from the Console, Spyder looks in memory to find the object you need help on (thus you need to run the file first), while when sourced from the Editor, it statically analyzes the source files without actually running the code. Major improvements in this domain are coming with Spyder 4, specifically with the use of the Language Server Protocol like Atom and VSCode.

[BRdubW]

Spyder/Dev seems to have spun out of control. I've given up on what used to great features that are now failing. Good luck and thanks for all the fish!

On Mon, Jul 23, 2018, 22:02 rtk notifications@github.com wrote:

I also have the same problem - autocomplete working in console, not editor.

conda list:

Name Version Build Channel

_ipyw_jlab_nb_ext_conf 0.1.0 py36he11e457_0 alabaster 0.7.10 py36h306e16b_0 anaconda-client 1.6.14 py36_0 anaconda-navigator 1.8.7 py36_0 anaconda-project 0.8.2 py36h44fb852_0 asn1crypto 0.24.0 py36_0 astroid 1.6.3 py36_0 astropy 3.0.2 py36h3010b51_1 attrs 18.1.0 py36_0 babel 2.5.3 py36_0 backcall 0.1.0 py36_0 backports 1.0 py36hfa02d7e_1 backports.shutil_get_terminal_size 1.0.0 py36hfea85ff_2 beautifulsoup4 4.6.0 py36h49b8c8c_1 bitarray 0.8.1 py36h14c3975_1 bkcharts 0.2 py36h735825a_0 blas 1.0 mkl blaze 0.11.3 py36h4e06776_0 bleach 2.1.3 py36_0 blosc 1.14.3 hdbcaa40_0 bokeh 0.12.16 py36_0 boto 2.48.0 py36h6e4cd66_1 bottleneck 1.2.1 py36haac1ea0_0 bzip2 1.0.6 h14c3975_5 ca-certificates 2018.03.07 0 cairo 1.14.12 h7636065_2 certifi 2018.4.16 py36_0 cffi 1.11.5 py36h9745a5d_0 chardet 3.0.4 py36h0f667ec_1 click 6.7 py36h5253387_0 cloudpickle 0.5.3 py36_0 clyent 1.2.2 py36h7e57e65_1 colorama 0.3.9 py36h489cec4_0 conda 4.5.8 py36_0 conda-build 3.10.5 py36_0 conda-env 2.6.0 h36134e3_1 conda-verify 2.0.0 py36h98955d8_0 contextlib2 0.5.5 py36h6c84a62_0 cryptography 2.2.2 py36h14c3975_0 curl 7.60.0 h84994c4_0 cycler 0.10.0 py36h93f1223_0 cython 0.28.2 py36h14c3975_0 cytoolz 0.9.0.1 py36h14c3975_0 dask 0.17.5 py36_0 dask-core 0.17.5 py36_0 datashape 0.5.4 py36h3ad6b5c_0 dbus 1.13.2 h714fa37_1 decorator 4.3.0 py36_0 distributed 1.21.8 py36_0 docutils 0.14 py36hb0f60f5_0 entrypoints 0.2.3 py36h1aec115_2 et_xmlfile 1.0.1 py36hd6bccc3_0 expat 2.2.5 he0dffb1_0 fastcache 1.0.2 py36h14c3975_2 filelock 3.0.4 py36_0 flask 1.0.2 py36_1 flask-cors 3.0.4 py36_0 fontconfig 2.12.6 h49f89f6_0 freetype 2.8 hab7d2ae_1 get_terminal_size 1.0.0 haa9412d_0 gevent 1.3.0 py36h14c3975_0 gevent 1.3.5 glib 2.56.1 h000015b_0 glob2 0.6 py36he249c77_0 gmp 6.1.2 h6c8ec71_1 gmpy2 2.0.8 py36hc8893dd_2 graphite2 1.3.11 h16798f4_2 greenlet 0.4.13 py36h14c3975_0 gst-plugins-base 1.14.0 hbbd80ab_1 gstreamer 1.14.0 hb453b48_1 h5py 2.7.1 py36ha1f6525_2 harfbuzz 1.7.6 h5f0a787_1 hashids 1.2.0 hdf5 1.10.2 hba1933b_1 heapdict 1.0.0 py36_2 html5lib 1.0.1 py36h2f9c1c0_0 icu 58.2 h9c2bf20_1 idna 2.6 py36h82fb2a8_1 imageio 2.3.0 py36_0 imagesize 1.0.0 py36_0 intel-openmp 2018.0.0 8 ipykernel 4.8.2 py36_0 ipython 6.4.0 py36_0 ipython_genutils 0.2.0 py36hb52b0d5_0 ipywidgets 7.2.1 py36_0 isort 4.3.4 py36_0 itsdangerous 0.24 py36h93cc618_1 jbig 2.1 hdba287a_0 jdcal 1.4 py36_0 jedi 0.12.0 py36_1 jinja2 2.10 py36ha16c418_0 jpeg 9b h024ee3a_2 jsonschema 2.6.0 py36h006f8b5_0 jupyter 1.0.0 py36_4 jupyter_client 5.2.3 py36_0 jupyter_console 5.2.0 py36he59e554_1 jupyter_core 4.4.0 py36h7c827e3_0 jupyterlab 0.32.1 py36_0 jupyterlab_launcher 0.10.5 py36_0 kiwisolver 1.0.1 py36h764f252_0 lazy-object-proxy 1.3.1 py36h10fcdad_0 libcurl 7.60.0 h1ad7b7a_0 libedit 3.1.20170329 h6b74fdf_2 libffi 3.2.1 hd88cf55_4 libgcc-ng 7.2.0 hdf63c60_3 libgfortran-ng 7.2.0 hdf63c60_3 libpng 1.6.34 hb9fc6fc_0 libsodium 1.0.16 h1bed415_0 libssh2 1.8.0 h9cfc8f7_4 libstdcxx-ng 7.2.0 hdf63c60_3 libtiff 4.0.9 he85c1e1_1 libtool 2.4.6 h544aabb_3 libxcb 1.13 h1bed415_1 libxml2 2.9.8 h26e45fe_1 libxslt 1.1.32 h1312cb7_0 llvmlite 0.23.1 py36hdbcaa40_0 locket 0.2.0 py36h787c0ad_1 lxml 4.2.1 py36h23eabaa_0 lzo 2.10 h49e0be7_2 markupsafe 1.0 py36hd9260cd_1 matplotlib 2.2.2 py36h0e671d2_1 mccabe 0.6.1 py36h5ad9710_1 mistune 0.8.3 py36h14c3975_1 mkl 2018.0.2 1 mkl-service 1.1.2 py36h17a0993_4 mkl_fft 1.0.1 py36h3010b51_0 mkl_random 1.0.1 py36h629b387_0 more-itertools 4.1.0 py36_0 mpc 1.0.3 hec55b23_5 mpfr 3.1.5 h11a74b3_2 mpmath 1.0.0 py36hfeacd6b_2 msgpack 0.5.6 msgpack-python 0.5.6 py36h6bb024c_0 multipledispatch 0.5.0 py36_0 navigator-updater 0.2.1 py36_0 nbconvert 5.3.1 py36hb41ffb7_0 nbformat 4.4.0 py36h31c9010_0 ncurses 6.1 hf484d3e_0 networkx 2.1 py36_0 nltk 3.3.0 py36_0 nose 1.3.7 py36hcdf7029_2 notebook 5.5.0 py36_0 numba 0.38.0 py36h637b7d7_0 numexpr 2.6.5 py36h7bf3b9c_0 numpy 1.14.3 py36hcd700cb_1 numpy-base 1.14.3 py36h9be14a7_1 numpydoc 0.8.0 py36_0 odo 0.5.1 py36h90ed295_0 olefile 0.45.1 py36_0 openpyxl 2.5.3 py36_0 openssl 1.0.2o h20670df_0 packaging 17.1 py36_0 pandas 0.23.0 py36h637b7d7_0 pandoc 1.19.2.1 hea2e7c5_1 pandocfilters 1.4.2 py36ha6701b7_1 pango 1.41.0 hd475d92_0 parso 0.3.1 py36_0 partd 0.3.8 py36h36fd896_0 patchelf 0.9 hf79760b_2 path.py 11.0.1 py36_0 pathlib2 2.3.2 py36_0 patsy 0.5.0 py36_0 pcre 8.42 h439df22_0 pep8 1.7.1 py36_0 pexpect 4.5.0 py36_0 pickleshare 0.7.4 py36h63277f8_0 pillow 5.1.0 py36h3deb7b8_0 pip 10.0.1 py36_0 pixman 0.34.0 hceecf20_3 pkginfo 1.4.2 py36_1 pluggy 0.6.0 py36hb689045_0 ply 3.11 py36_0 prompt 0.4.1 prompt_toolkit 1.0.15 py36h17d85b1_0 psutil 5.4.5 py36h14c3975_0 ptyprocess 0.5.2 py36h69acd42_0 py 1.5.3 py36_0 pybars3 0.9.3 pycodestyle 2.4.0 py36_0 pycosat 0.6.3 py36h0a5515d_0 pycparser 2.18 py36hf9f622e_1 pycrypto 2.6.1 py36h14c3975_8 pycurl 7.43.0.1 py36hb7f436b_0 pyflakes 1.6.0 py36h7bd6a15_0 pygments 2.2.0 py36h0d3125c_0 pylint 1.8.4 py36_0 PyMeta3 0.5.1 pyodbc 4.0.23 py36hf484d3e_0 pyopengl 3.1.1a1 py36_0 pyopenssl 18.0.0 py36_0 pyparsing 2.2.0 py36hee85983_1 pyqt 5.9.2 py36h751905a_0 pysocks 1.6.8 py36_0 pytables 3.4.3 py36h02b9ad4_2 pytest 3.5.1 py36_0 pytest-arraydiff 0.2 py36_0 pytest-astropy 0.3.0 py36_0 pytest-doctestplus 0.1.3 py36_0 pytest-openfiles 0.3.0 py36_0 pytest-remotedata 0.2.1 py36_0 python 3.6.5 hc3d631a_2 python-dateutil 2.7.3 py36_0 pytz 2018.4 py36_0 pywavelets 0.5.2 py36he602eb0_0 pyyaml 3.12 py36hafb9ca4_1 pyzmq 17.0.0 py36h14c3975_0 qt 5.9.5 h7e424d6_0 qtawesome 0.4.4 py36h609ed8c_0 qtconsole 4.3.1 py36h8f73b5b_0 qtpy 1.4.1 py36_0 readline 7.0 ha6073c6_4 requests 2.18.4 py36he2e5f8d_1 rope 0.10.7 py36h147e2ec_0 ruamel_yaml 0.15.35 py36h14c3975_1 scikit-image 0.13.1 py36h14c3975_1 scikit-learn 0.19.1 py36h7aa7ec6_0 scipy 1.1.0 py36hfc37229_0 seaborn 0.8.1 py36hfad7ec4_0 selenium 3.13.0 send2trash 1.5.0 py36_0 setuptools 39.1.0 py36_0 simplegeneric 0.8.1 py36_2 singledispatch 3.4.0.3 py36h7a266c3_0 sip 4.19.8 py36hf484d3e_0 six 1.11.0 py36h372c433_1 snappy 1.1.7 hbae5bb6_3 snowballstemmer 1.2.1 py36h6febd40_0 sortedcollections 0.6.1 py36_0 sortedcontainers 1.5.10 py36_0 sphinx 1.7.4 py36_0 sphinxcontrib 1.0 py36h6d0f590_1 sphinxcontrib-websupport 1.0.1 py36hb5cb234_1 spyder 3.2.8 py36_0 sqlalchemy 1.2.7 py36h6b74fdf_0 sqlite 3.23.1 he433501_0 statsmodels 0.9.0 py36h3010b51_0 sympy 1.1.1 py36hc6d1c1c_0 TatSu 4.2.6 tblib 1.3.2 py36h34cf8b6_0 terminado 0.8.1 py36_1 testpath 0.3.1 py36h8cadb63_0 textworld 0.0.3 tk 8.6.7 hc745277_3 toolz 0.9.0 py36_0 tornado 5.0.2 py36_0 tqdm 4.23.4 traitlets 4.3.2 py36h674d592_0 typing 3.6.4 py36_0 unicodecsv 0.14.1 py36ha668878_0 unixodbc 2.3.6 h1bed415_0 urllib3 1.22 py36hbe7ace6_0 urwid 2.0.1 uuid 1.30 wcwidth 0.1.7 py36hdf4376a_0 webencodings 0.5.1 py36h800622e_1 werkzeug 0.14.1 py36_0 wheel 0.31.1 py36_0 widgetsnbextension 3.2.1 py36_0 wrapt 1.10.11 py36h28b7045_0 xlrd 1.1.0 py36h1db9f0c_1 xlsxwriter 1.0.4 py36_0 xlwt 1.3.0 py36h7b00a1f_0 xz 5.2.4 h14c3975_4 yaml 0.1.7 had09818_2 zeromq 4.2.5 h439df22_0 zict 0.1.3 py36h3a3bf81_0 zlib 1.2.11 ha838bed_2

Tried the PYTHONPATH fix mentioned above and enum34 wasn't installed. Help source is set to "Console".

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-407282003, or mute the thread https://github.com/notifications/unsubscribe-auth/AjuRbEoxI0y0aE9r7kna4n6lqvkFouL-ks5uJqp_gaJpZM4NJ7jo .

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

[ccordoba12]

For all people having new problems with this, you need to update jedi and parso:

conda update jedi parso

[BRdubW]

Not everyone uses a conda environment. Is that now the only supported method for using spyder?

On Tue, Jul 24, 2018, 07:40 Carlos Cordoba notifications@github.com wrote:

For all people having new problems with this, you need to update jedi and parso:

conda update jedi parso

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-407431257, or mute the thread https://github.com/notifications/unsubscribe-auth/AjuRbGdgtBWOIx0rCZujYZK9jB4Jowukks5uJzH2gaJpZM4NJ7jo .

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

[CAM-Gerlach]

Spyder/Dev seems to have spun out of control.

What makes you say that, @BRdubW ? Which, features, specifically? The majority of problems here are due to third party libraries that we don't have direct control over? Furthermore, our autocompletion, object inspection, etc. system is poised to become much more stable with the introduction of the new LSP architecture (as used by Atom and VSCode) in Spyder 4.

[ratnadeepb]

I use the miniconda environment and frankly that makes it easier to use Spyder without getting all the overhead of Anaconda.

On Tue, Jul 24, 2018, 21:20 Brian R. W. notifications@github.com wrote:

Not everyone uses a conda environment. Is that now the only supported method for using spyder?

On Tue, Jul 24, 2018, 07:40 Carlos Cordoba notifications@github.com wrote:

For all people having new problems with this, you need to update jedi and parso:

conda update jedi parso

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/spyder-ide/spyder/issues/4410#issuecomment-407431257 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AjuRbGdgtBWOIx0rCZujYZK9jB4Jowukks5uJzH2gaJpZM4NJ7jo

.

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-407455814, or mute the thread https://github.com/notifications/unsubscribe-auth/ALaUSX5KIC1YlUtHCuUcnZIMMHF6B-sXks5uJ0IngaJpZM4NJ7jo .

[CAM-Gerlach]

Not everyone uses a conda environment. Is that now the only supported method for using spyder?

@BRdubW We directly or indirectly provide a large number of install methods and basic documentation on each of them, including Anaconda/Miniconda (recommended), WinPython, Python(x,y) (deprecated), Fink/MacPorts/Brew, many common Linux distribution packages, pip/PyPI, and even running directly from a Github clone. However, for install-related, user-specific issues isolated to a non-conda-based method, we usually recommend that users try installing via conda instead, since those install methods (particularly pip) can sometimes have many pitfalls for non-experts. Furthermore, if an issue affects a large number of users on the platform and we are able to fix it from our end, then we do so (like with an issue with the wheel dependencies for Spyder 3.2.5, solved with a rapid 3.2.6 update, changes to follow the Debian guidelines, or collaboration with the WinPython developers to ensure compatibility).

We have both limited ability (since they are usually user-specific) and limited resources to provide post-install support for those issues since they are often isolated to a specific machine or environment, and if we didn't draw the line somewhere we would have very limited time to develop Spyder itself and fix the bugs we can control. Also, we only have limited control over many of those channels so they may have older versions with bugs that have been fixed in newer Spyder builds.

[BRdubW]

@C.A.M Gerlach It has been well over a year and editor autocompletion issue has not been solved. Sure it works great for some but does not work for all, still. This feature as well as well as the onject inspection feature used to work perfectly but now depending on which machine you are running and what flavor of OS and its standard or additional enabled repos you may have, its anyone's guess if the features work. Sometimes autocompletion works right off the bat and then somehow it stops mid session?! What really makes me think it has spun out of control is the myriad of suggestions, most of which have not seemed to work for all. Yes, third party libraries. Like pulling the rug out from under your feet. They break your code in changing theirs. When is Spyder 4 expected to ne released? I imagine it will be great relief for the Dev team to move away from the plethora of third party adventures and onto better things with LSP. I use Atom editor for several projects and it is quite nice!

On Tue, Jul 24, 2018, 08:51 C.A.M. Gerlach notifications@github.com wrote:

Spyder/Dev seems to have spun out of control.

What makes you say that, @BRdubW https://github.com/BRdubW ? Which, features, specifically? The majority of problems here are due to third party libraries that we don't have direct control over? Furthermore, our autocompletion, object inspection, etc. system is poised to become much more stable with the introduction of the new LSP architecture (as used by Atom and VSCode) in Spyder 4.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-407456351, or mute the thread https://github.com/notifications/unsubscribe-auth/AjuRbPr9TzTmjXb1O001zs3zytmitamPks5uJ0KCgaJpZM4NJ7jo .

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

[CAM-Gerlach]

Thank you for your response, @BRdubW

It has been well over a year and editor autocompletion issue has not been solved.

To be honest, it's sort of a "cure" for cancer (albeit somewhat easier, hopefully :)—a good deal more complicated than it may appear on the surface. There have been many different individual proximate causes for it stopping working (why is exactly why there have been

the myriad of suggestions, most of which have not seemed to work for all.

and furthermore,

because, just like cancer, it isn't a monolithic "disease" with a single treatment effective for all types, and given the fact that, like cancer, the root commonality being at such a low level it cannot be totally cured for all except by a very fundamental overhaul to the architecture of its host. This is far more ambitious than just trying to find band-aid treatments to the individual manifestations of the problem, and requires a lot of development time and commitments that as a volunteer project we don't necessarily have in abundance, and that face much more inertia than the former. Furthermore, with regard to

This feature as well as well as the onject inspection feature

the same underlying issue affects one if it affects the other, at least when used from the Editor, but conversely, the underlying work will improve all our completion/introspection/etc/ facilities.

With regard to

When is Spyder 4 expected to ne released?

Considerable work has been underway for over a year to get this fixed, but our loss of third-party funding has hampered this process. However, with our community and grant funding now in place, we're planning to release Spyder 4 beta 1 on conda-forge, PyPI (?) and Github in the next few weeks with everything implemented thus far, and Spyder 4 beta 2 a couple months after which will merge the LSP improvements you've been waiting for. The first release canidate is planned for the end of December of this year, and the final release for Q1 2019.

[Duinobot]

This problem is resolved now by upgrading all packages, I do not know what the cause is tough. conda -upgrade all

[CAM-Gerlach]

@aisolution Good to hear! This would indeed suggest a third party package was the culprit, probably either parso, jedi or something like that. Unfortunately, as I mentioned there isn't much we can do about that until we overhaul the entire completion infrastructure, which is exactly what #4751 will do once it gets merged to the Spyder 4 branch in the next few weeks/months.

[elinor-lev]

Not sure if this is related, but I have the editor completion issue when I open spyder indirectly, e.g. as an executable or as a MacOS App.

If I start spyder from the command line or with the anaconda navigator, auto-completion works.

[BRdubW]

I find that the anacoda install works very well and have switched away from my linux distro (debian pure, xubuntu, and centos 7) versions of spyder et. al. as they are all outdated and are in various states of broken.

Given the feedback from the developers, the transition to 4.0 ought to address the issues that stem in one or another from the way in which the spyder evolution went for awhile in terms of dependencies on third party components over which they had no control. A total restructuring, which is clearly a monumental undertaking, is the only solution. The fact this is open source and free means a LOT of talented programmers sacrifice much personal time to this effort. I for one, shall be patient, and have always appreciated the utility of spyder, even during these times of odd behavior.

Cheers, Brian

On Thu, Aug 16, 2018 at 11:12 AM, Elinor Medezinski < notifications@github.com> wrote:

Not sure if this is related, but I have the editor completion issue when I open spyder indirectly, e.g. as an executable https://www.youtube.com/watch?v=wSdG8SgVcbA or an MacOS App https://stackoverflow.com/questions/20723977/ways-to-invoke-python-and-spyder-on-osx .

If I start spyder from the command line or with the anaconda navigator, auto-completion works.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-413636385, or mute the thread https://github.com/notifications/unsubscribe-auth/AjuRbJz08lOsJYRWTIqWdNLjcK_780y8ks5uRbXygaJpZM4NJ7jo .

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

[CAM-Gerlach]

@elinor-lev This is because those methods, at least according to the video, haven't been officially supported for a long time except by old versions of Spyder, so either you're getting an old, broken version or the method itself breaks something with the independent threads/processes Spyder launches to run the completion engines. If the latter, there is a chance this may be fixed in Spyder 4, however.

@BRdubW

I find that the anacoda install works very well and have switched away from my linux distro (debian pure, xubuntu, and centos 7) versions of spyder et. al. as they are all outdated and are in various states of broken.

Yes; while we are currently working with their maintainers to try to get them updated as best we can, we recommend you use Anaconda to get the latest versions with fewer stability and install problems.

Given the feedback from the developers, the transition to 4.0 ought to address the issues that stem in one or another from the way in which the spyder evolution went for awhile in terms of dependencies on third party components over which they had no control.

That's the hope, yup. The two biggest areas where we've observed noticed third-party problems are (first and foremost) the autocompletion/help/introspection (rope, jedi, parso), which the major overhaul with LSP should mostly or entirely address, and to a lesser extent issues with the kernel not working in the IPython console (due to ipykernel, tornado, etc) and related issues with managing packages and environments, which already are starting to be addressed with the main focus of the newly released Spyder 3.3.0/3.3.1 with refactoring all the kernel/console code into a modular spyder-kernels package that can easily be installed anywhere to allow Spyder to launch kernels or connect to them remotely, and well as more and better documentation explaining this to avoid missteps, and will see further improvements in Spyder 4.

In any case, we really appreciate your feedback and support, and user requests play a big role in what we prioritize for future versions—the two biggest features for Spyder 4, a new debugger and overhauled completion/introspection—were the top two most requested by users of Spyder 3, and the third biggest, better Projects with easy package and environment management to simplify workflow, stems from both requests and being one of the biggest difficulties new users have reported facing.

[endolith]

@aisolution It's conda update --all, and it downgraded Spyder from 3.3.1 to 3.2.8 and caused Spyder to start having other issues

[CAM-Gerlach]

@endolith This is not really recommended, and updating one or more dependencies to a version not tested together in the anaconda metapackage is the likely reason for this problem in the first place.

However, the fact that updating...something...is requiring Spyder>=3.2.8 is worrisome, and seems to match what was reported on another thread. @endolith can you run conda install spyder=3.3.1 and post your full output here? We need to know what's causing this, thanks.

[endolith]

It's probably my fault for using conda-forge? I don't really understand how channels work.

conda install spyder=3.3.1 says:

The following packages will be UPDATED:

    blas:            1.0-mkl                 conda-forge --> 1.0-mkl
    spyder:          3.2.8-py36_0            conda-forge --> 3.3.1-py36_2         conda-forge

The following packages will be DOWNGRADED:

    clangdev:        6.0.1-default_1         conda-forge [vc14] --> 5.0.0-flang_3        conda-forge [flang,vc14]
    curl:            7.61.0-he44d5f6_2       conda-forge --> 7.60.0-vc14_0        conda-forge [vc14      ]
    freetype:        2.9.1-he8b6a0d_1004     conda-forge --> 2.8.1-vc14_0         conda-forge [vc14      ]
    jpeg:            9c-hfa6e2cd_1001        conda-forge --> 9b-vc14_2            conda-forge [vc14      ]
    libarchive:      3.3.3-hd1ea8e3_1001     conda-forge --> 3.3.2-h1d0d21d_1
    libiconv:        1.15-hfa6e2cd_1003      conda-forge --> 1.14-vc14_4          conda-forge [vc14      ]
    libpng:          1.6.35-h7602738_1002    conda-forge --> 1.6.34-vc14_0        conda-forge [vc14      ]
    libprotobuf:     3.6.1-h1a1b453_1000     conda-forge --> 3.5.2-vc14_0         conda-forge [vc14      ]
    libxml2:         2.9.8-h9ce36c8_1005     conda-forge --> 2.9.5-vc14_1         conda-forge [vc14      ]
    llvmdev:         6.0.1-h1ad3211_1002     conda-forge --> 4.0.0-default_0      conda-forge [vc14      ]
    lxml:            4.2.5-py36heafd4d3_1000 conda-forge --> 4.2.3-py36heafd4d3_0 conda-forge
    matplotlib:      3.0.0-py36h7b168c4_1    conda-forge --> 2.2.2-py36_1         conda-forge
    openblas:        0.3.3-h535eed3_1001     conda-forge --> 0.2.20-vc14_8        conda-forge [vc14      ]
    openmp:          6.0.1-h1ad3211_0        conda-forge --> 5.0.0-vc14_0         conda-forge [vc14      ]
    pillow:          5.3.0-py36h9a613e6_1000 conda-forge --> 5.2.0-py36_0         conda-forge
    protobuf:        3.6.1-py36he025d50_1    conda-forge --> 3.5.2-py36_vc14_0    conda-forge [vc14      ]
    python-crfsuite: 0.9.6-py36he980bc4_1000 conda-forge --> 0.9.2-py36_vc14_0    conda-forge [vc14      ]
    spyder-kernels:  1.1.0-py_0              conda-forge --> 0.2.6-py_1           conda-forge
    sqlite:          3.25.2-hfa6e2cd_1000    conda-forge --> 3.22.0-vc14_0        conda-forge [vc14      ]
    tensorboard:     1.10.0-py36_0           conda-forge --> 1.9.0-py36_0         conda-forge
    tensorflow:      1.10.0-py36_0           conda-forge --> 1.9.0-py36_0         conda-forge

When I then run update all again, I get:

The following NEW packages will be INSTALLED:

    llvmdev:             6.0.1-h1ad3211_1002  conda-forge

The following packages will be UPDATED:

    clangdev:            5.0.0-flang_3        conda-forge [flang,vc14] --> 6.0.1-default_1         conda-forge [vc14]
    curl:                7.60.0-vc14_0        conda-forge [vc14      ] --> 7.61.0-he44d5f6_2       conda-forge
    jpeg:                9b-vc14_2            conda-forge [vc14      ] --> 9c-hfa6e2cd_1001        conda-forge
    keras-preprocessing: 1.0.2-py_1           conda-forge --> 1.0.5-py_0              conda-forge
    libarchive:          3.3.2-h1d0d21d_1                 --> 3.3.3-hd1ea8e3_1001     conda-forge
    libiconv:            1.14-vc14_4          conda-forge [vc14      ] --> 1.15-hfa6e2cd_1003      conda-forge
    libpng:              1.6.34-vc14_0        conda-forge [vc14      ] --> 1.6.35-h7602738_1002    conda-forge
    libprotobuf:         3.5.2-vc14_0         conda-forge [vc14      ] --> 3.6.1-h1a1b453_1000     conda-forge
    libxml2:             2.9.5-vc14_1         conda-forge [vc14      ] --> 2.9.8-h9ce36c8_1005     conda-forge
    lxml:                4.2.3-py36heafd4d3_0 conda-forge --> 4.2.5-py36heafd4d3_1000 conda-forge
    openblas:            0.2.20-vc14_8        conda-forge [vc14      ] --> 0.3.3-h535eed3_1001     conda-forge
    openmp:              5.0.0-vc14_0         conda-forge [vc14      ] --> 6.0.1-h1ad3211_0        conda-forge
    pillow:              5.2.0-py36h08bbbbd_0             --> 5.3.0-py36h9a613e6_1000 conda-forge
    protobuf:            3.5.2-py36_vc14_0    conda-forge [vc14      ] --> 3.6.1-py36he025d50_1    conda-forge
    python-crfsuite:     0.9.2-py36_vc14_0    conda-forge [vc14      ] --> 0.9.6-py36he980bc4_1000 conda-forge
    spyder-kernels:      0.2.6-py_1           conda-forge --> 1.1.0-py_0              conda-forge
    sqlite:              3.22.0-vc14_0        conda-forge [vc14      ] --> 3.25.2-hfa6e2cd_1000    conda-forge
    tensorboard:         1.9.0-py36_0         conda-forge --> 1.10.0-py36_0           conda-forge
    tensorflow:          1.9.0-py36_0         conda-forge --> 1.10.0-py36_0           conda-forge

The following packages will be DOWNGRADED:

    blas:                1.0-mkl                          --> 1.0-mkl                 conda-forge
    keras:               2.2.4-py36_0         conda-forge --> 2.1.6-py36_0            conda-forge
    spyder:              3.3.1-py36_2         conda-forge --> 3.2.8-py36_0            conda-forge

[ccordoba12]

@endolith, please stop doing conda update --all. Instead you need to do

conda remove spyder-kernels
conda install spyder-kernel==0.*
conda update spyder

[ccordoba12]

It's probably my fault for using conda-forge?

No, it's not conda-forge. it's conda update --all, which you need to stop using because it breaks the restrictions imposed by some packages on others.

[BRdubW]

Here's a thought....remove conda update --all option ???? Just sayin'

On Oct 7, 2018 8:04 PM, "Carlos Cordoba" notifications@github.com wrote:

It's probably my fault for using conda-forge?

No, it's not conda-forge. it's conda update --all, which you need to stop using because it breaks the restrictions imposed by some packages on others.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-427711736, or mute the thread https://github.com/notifications/unsubscribe-auth/AjuRbFHhE5viITm8IZhUpdn5mC0OR5V2ks5uisDYgaJpZM4NJ7jo .

-- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records.

[CAM-Gerlach]

@ccordoba12 Well, to be fair @mingwandroid did give some pretty dire warnings against mixing channels. However, if you're pure conda-forge from the start that shouldn't be the issue.

Here's a thought....remove conda update --all option ???? Just sayin'

@BRdubW First of all, that's of course part of conda, not Spyder, so we have zero control over what they do. Second, that option exists for a very specific and valid purpose and nowhere does their user guide recommend it for general use, so there is no reason to remove it, but rather better educate users on appropriate package management strategies (that will incidentally be much easier with Spyder 4, as it will have GUI package and environment management built in as an added feature) and encourage users to carefully read the user guide and documentation before blindly running conda update --all without a clear rationale and understanding of how it works and what to do if a dependency issue arises.

[ccordoba12]

@BRdubW, yeah, that'd be great! Pip stop forcing it on its users since its 10 version, and that's a blessing.

[endolith]

which you need to stop using

Well I didn't do it until this thread told me to. :D

[partha1968]

I generally update using conda update --all. Will this create problem (breaking depedencies) ? If yes, how to update conda? Regards

On 8 Oct 2018 8:34 am, "Carlos Cordoba" notifications@github.com wrote:

It's probably my fault for using conda-forge?

No, it's not conda-forge. it's conda update --all, which you need to stop using because it breaks the restrictions imposed by some packages on others.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/4410#issuecomment-427711736, or mute the thread https://github.com/notifications/unsubscribe-auth/AOhVGaaP7iB4zidDeTQaoOLrPw01Gv4bks5uisDYgaJpZM4NJ7jo .

[ccordoba12]

@partha1968, simply update the packages that you an update for: conda update spyder, conda update pandas, etc.

[CAM-Gerlach]

Will this create problem (breaking depedencies) ?

@partha1968 Yes, that's exactly what has happened here and what @ccordoba12 and myself are saying.

If yes, how to update conda?

conda update conda

Taking your question less literally, if you want to update everything, you can update the anaconda metapackage to do so a few times a year for your base env, and otherwise only updating specific packages with specific things you need (spyder, pandas, qtconsole, etc) when an update comes out you want to use.

[endolith]

@ccordoba12

That doesn't seem to work for me:

λ conda install spyder-kernel==0.*
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - spyder-kernel=0

simply update the packages that you an update for: conda update spyder, conda update pandas, etc.

That's what I had been doing

[ccordoba12]

It's spyder-kernels, not spyder-kernel.