url = 'https://raw.githubusercontent.com/jbrownlee/Datasets/master/wine.csv'
df = read_csv(url, header=None)
# Mandatory:
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 3.0.4 (OK)
cloudpickle >=0.5.0 : 1.4.1 (OK)
diff_match_patch >=20181111 : 20181111 (OK)
intervaltree : None (OK)
IPython >=4.0 : 7.16.1 (OK)
jedi =0.17.1 : 0.17.1 (OK)
nbconvert >=4.0 : 5.6.1 (OK)
numpydoc >=0.6.0 : 0.9.2 (OK)
paramiko >=2.4.0 : 2.7.1 (OK)
parso =0.7.0 : 0.7.0 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.7.0 (OK)
pygments >=2.0 : 2.6.1 (OK)
pylint >=1.0 : 2.4.4 (OK)
pyls >=0.34.0;<1.0.0 : 0.34.1 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 0.7.0 (OK)
qtconsole >=4.6.0 : 4.7.5 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.8.3 : 0.9.4 (OK)
sphinx >=0.6.6 : 3.0.3 (OK)
spyder_kernels >=1.9.2;<1.10.0 : 1.9.2 (OK)
watchdog : None (OK)
zmq >=17 : 18.1.1 (OK)
# Optional:
cython >=0.21 : 0.29.17 (OK)
matplotlib >=2.0.0 : 3.1.3 (OK)
numpy >=1.7 : 1.18.1 (OK)
pandas >=0.13.1 : 1.0.5 (OK)
scipy >=0.17.0 : 1.5.0 (OK)
sympy >=0.7.3 : None (OK)
Hi @pchristian4481, thanks for the report.
Where are you seeing these messages/errors? Could you paste the full traceback and provide some context?
Thanks!
I've just installed Spyder 4.1.4 and now i've run into the same warning...
After some checking the quickest way to reproduce it on my side is the following:
... simply execute the following lines in a fresh console (e.g. select all + F9 )
# try to import something that can NOT be found
import asdfasdf
def somefunction():
pass
>>> Traceback (most recent call last):
>>>
>>> File "<ipython-input-1-d725d5305948>", line 1, in <module>
>>> import asdfasdf
>>>
>>> ModuleNotFoundError: No module named 'asdfasdf'
>>>
>>>
>>> QSocketNotifier: Multiple socket notifiers for same socket 1948 and type Read
>>>
ok... I've just realized that there's an even simpler way...
(e.g. it also popps up during normal operations)
start a new console, type 1
and hit enter
@impact27 @dalthviz can you reproduce this?
maybe related to https://github.com/vispy/vispy/issues/1787 @raphaelquast do you use vispy?
no, vispy is definitely not part of the environment I'm currently using
by the way... the warning is cumulative... so after 5 minutes I end up having my console flooded with
the same message on and on again...
Can you think of a possible quick-fix? (e.g. can i somehow turn off those warnings?)
(I'd really like to keep using v4.1.4 since it fixes the code-cell issue on separate windows which I tend to use extensively...)
I would use https://python.readthedocs.io/en/latest/library/warnings.html#the-warnings-filter to raise the warning as errors. This would hopefully help us by showing where the warning is raised from.
This is probably a bug that happens on Windows only. I'm taking a look at it right now.
Maybe this is related jupyter/qtconsole#332 but now some how the message is being printed in the actual console?
Edit: I was not able to reproduce this (installed spyder 4.1.4 with pip in a new env). As @impact27 said, maybe a way to check where this warning is being triggered could be setting the filtering warnings to error
. Something like this should made the change:
import warnings
warnings.filterwarnings("error")
and then the stderr should be printed in the console (hopefully with more information).
Thank you.
From: Carlos Cordoba notifications@github.com
Sent: Wednesday, July 15, 2020 11:07 AM
To: spyder-ide/spyder spyder@noreply.github.com
Cc: pchristian4481 pchristian@prc-hsv.com; Mention <
[email protected]>
Subject: Re: [spyder-ide/spyder] QSocketNotifier: Multiple socket
notifiers for same socket 1960 and type Read (#13275)
This is probably a bug that happens on Windows only. I'm taking a look at
it right now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/13275#issuecomment-658843404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUKKMXXH3ZYO442OXZLG4DR3XHZFANCNFSM4OYQWMRQ
.
--
This message is intended for the addressee only and may contain Paragon
Research Corporation (PRC) confidential or privileged information. Use or
distribution of such confidential information is strictly prohibited
without the prior written permission of PRC. If you have received this
message in error, please contact the sender immediately and delete the
message and attachments from your computer.
I found this was an error in the ipykernel
package and submitted ipython/ipykernel#525 to fix it.
@dalthviz, could you test that change locally and let us know if it fixes the problem on your side? Thanks!
@ccordoba12 I was not able to reproduce this in the first place so I'm unsure if checking on my side would have any confirmation effect
I was not able to reproduce this in the first place
Sorry, I thought you were. The steps to do it are:
%gui qt
1
in the console (as shown above by @raphaelquast).@ccordoba12 the fix works :+1:
good news 👍 so the way to go is to revert back to v4.1.3 and wait for v4.1.5 ?
@raphaelquast as a quick fix until the fix is delivered through the updates you can download the fixed file from here: https://github.com/ipython/ipykernel/blob/4a05435220c730605ab454001ac3ecc364299736/ipykernel/eventloops.py
and replace the current file eventloops.py under pathToAnacondaInstallation\envs\yourEnvironment\Lib\site-packagesipykernel
Backup the current file just in case.
That solved it for me.
@raphaelquast, this is not a problem in Spyder but in one of our dependencies (ipykernel
). I hope a new release with my fix will be out soon (we don't have control over that, sorry).
@roteiro
... thanks for the suggestion, however I try to avoid manually changing files in the environment if not absolutely necessary
(and in this case v4.1.3 does it's job well enough 😊)
@ccordoba12
OK, thanks for your (always) awesome support, I'll be patient!
Can't wait for a fix - thank you very much everyone :)
@raphaelquast, nice fix. Thank you.
@pchristian4481 thanks, but the credit should really go to @ccordoba12 and the rest since I haven't done a thing except complaining about the issue 😁
Very good.
From: Raphael Quast notifications@github.com
Sent: Monday, August 3, 2020 10:18 AM
To: spyder-ide/spyder spyder@noreply.github.com
Cc: pchristian4481 pchristian@prc-hsv.com; Mention <
[email protected]>
Subject: Re: [spyder-ide/spyder] QSocketNotifier: Multiple socket
notifiers for same socket and type Read (#13275)
@pchristian4481 https://github.com/pchristian4481 thanks, but the credit
should really go to @ccordoba12 https://github.com/ccordoba12 and the
rest since I haven't done a thing except complaining about the issue 😁
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/13275#issuecomment-668080559,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUKKMV5NUEPO6XYMKUYLA3R63IKVANCNFSM4OYQWMRQ
.
--
This message is intended for the addressee only and may contain Paragon
Research Corporation (PRC) confidential or privileged information. Use or
distribution of such confidential information is strictly prohibited
without the prior written permission of PRC. If you have received this
message in error, please contact the sender immediately and delete the
message and attachments from your computer.
Hello,
I am receiving the same flooding warning in Spyder 4.1.5 .
And I sometimes receive 5 messages at the same time.
Shall I downgrade to 4.1.3 ?
Please update the ipykernel package to its 5.3.4 version to get the fix for this issue.
Most helpful comment
@raphaelquast as a quick fix until the fix is delivered through the updates you can download the fixed file from here: https://github.com/ipython/ipykernel/blob/4a05435220c730605ab454001ac3ecc364299736/ipykernel/eventloops.py
and replace the current file eventloops.py under pathToAnacondaInstallation\envs\yourEnvironment\Lib\site-packagesipykernel
Backup the current file just in case.
That solved it for me.