text:
Spyder does not start after the first time as the spyder-terminal library does not work on my system

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
A fresh install of Spyder 5.4.5 on Windows Server 2016 version 1607 starts the first time with the following error:

It was not possible to load the Terminal plugin. The problem was:
Unfortunately, the library that spyder-terminal uses to create terminals is failing to
work in your system. Therefore, this plugin will be deactivated.
This usually happens on Windows 7 systems. If that's the case, please consider
updating to a newer Windows version.

All fine, I can work without the terminal. Spyder starts up, without a terminal panel and everything seems to work.
However, when I restart Spyder the same error appears, but this time Spyder does not launch and the error disappears quickyl by itself. I can no longer launch Spyder.
What steps reproduce the problem?

Launch freshly installed Spyder (without a ~/.spyder-py3 directory from older versions)
Click OK on the Plguin compatibility check error
Close Spyder
Launch Spyder

What is the expected output? What do you see instead?
I would expect that Spyder starts the second time, without showing the error and without the terminal panel.
Instead, Spyder starts launching, shows the splash screen, shows the error and then crashes.
I cannot launch Spyder, unless I delete the ~/.spyder-py3 directory such that it appears to be a "fresh" install. Then the cycle repeats.
Paste Traceback/Error Below (if applicable)

When launching using the commandline:
PS C:\Program Files\Spyder> .\Python\python.exe .\Spyder.launch.pyw --debug-info verbose

I get the following log (I only included that last few lines before the crash:

Fold out launch log
2023-09-21 14:23:02,918 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio1: 0.9912109375
2023-09-21 14:23:02,918 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio2: 0.9833984375
2023-09-21 14:23:02,919 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> is_likely_binary: True
2023-09-21 14:23:02,920 [DEBUG] [chardet.charsetprober] -> SHIFT_JIS Japanese prober hit error at byte 105
2023-09-21 14:23:02,921 [DEBUG] [chardet.charsetprober] -> EUC-JP Japanese prober hit error at byte 105
2023-09-21 14:23:02,921 [DEBUG] [chardet.charsetprober] -> GB2312 Chinese prober hit error at byte 105
2023-09-21 14:23:02,921 [DEBUG] [chardet.charsetprober] -> EUC-KR Korean prober hit error at byte 105
2023-09-21 14:23:02,922 [DEBUG] [chardet.charsetprober] -> CP949 Korean prober hit error at byte 105
2023-09-21 14:23:02,922 [DEBUG] [chardet.charsetprober] -> Big5 Chinese prober hit error at byte 105
2023-09-21 14:23:02,922 [DEBUG] [chardet.charsetprober] -> EUC-TW Taiwan prober hit error at byte 105
2023-09-21 14:23:02,923 [DEBUG] [chardet.charsetprober] -> Johab Korean prober hit error at byte 105
2023-09-21 14:23:02,925 [DEBUG] [chardet.charsetprober] -> windows-1251 Russian confidence = 0.12799495392693638
2023-09-21 14:23:02,925 [DEBUG] [chardet.charsetprober] -> KOI8-R Russian confidence = 0.01
2023-09-21 14:23:02,925 [DEBUG] [chardet.charsetprober] -> ISO-8859-5 Russian confidence = 0.01
2023-09-21 14:23:02,925 [DEBUG] [chardet.charsetprober] -> MacCyrillic Russian confidence = 0.043998265412384385
2023-09-21 14:23:02,926 [DEBUG] [chardet.charsetprober] -> IBM866 Russian confidence = 0.0
2023-09-21 14:23:02,932 [DEBUG] [chardet.charsetprober] -> IBM855 Russian confidence = 0.01
2023-09-21 14:23:02,932 [DEBUG] [chardet.charsetprober] -> ISO-8859-7 Greek confidence = 0.0
2023-09-21 14:23:02,932 [DEBUG] [chardet.charsetprober] -> windows-1253 Greek confidence = 0.0
2023-09-21 14:23:02,932 [DEBUG] [chardet.charsetprober] -> ISO-8859-5 Bulgarian confidence = 0.0
2023-09-21 14:23:02,932 [DEBUG] [chardet.charsetprober] -> windows-1251 Bulgarian confidence = 0.0
2023-09-21 14:23:02,933 [DEBUG] [chardet.charsetprober] -> TIS-620 Thai confidence = 0.01
2023-09-21 14:23:02,933 [DEBUG] [chardet.charsetprober] -> ISO-8859-9 Turkish confidence = 0.0
2023-09-21 14:23:02,933 [DEBUG] [chardet.charsetprober] -> windows-1255 Hebrew confidence = 0.0
2023-09-21 14:23:02,933 [DEBUG] [chardet.charsetprober] -> windows-1255 Hebrew confidence = 0.0
2023-09-21 14:23:02,933 [DEBUG] [chardet.charsetprober] -> windows-1255 Hebrew confidence = 0.0
2023-09-21 14:23:02,933 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> detected_encoding: {'encoding': 'MacRoman', 'confidence': 0.5153771760154738, 'language': ''}
2023-09-21 14:23:02,934 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> failure: decodable_as_unicode: False
2023-09-21 14:23:02,940 [DEBUG] [spyder.utils.external.binaryornot.check] -> is_binary: 'C:\\Users\\username\\ntuser.pol'
2023-09-21 14:23:02,944 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio1: 0.5302734375
2023-09-21 14:23:02,945 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio2: 1.0
2023-09-21 14:23:02,945 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> is_likely_binary: False
2023-09-21 14:23:02,946 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> detected_encoding: {'encoding': 'utf-16le', 'confidence': 0.85, 'language': ''}
2023-09-21 14:23:02,946 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> failure: decodable_as_unicode: False
2023-09-21 14:23:02,946 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> has nulls:True
2023-09-21 14:23:03,139 [DEBUG] [spyder.utils.external.binaryornot.check] -> is_binary: 'C:\\Users\\username\\pspp.jnl'
2023-09-21 14:23:03,140 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio1: 0.0
2023-09-21 14:23:03,143 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> nontext_ratio2: 1.0
2023-09-21 14:23:03,143 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> is_likely_binary: False
2023-09-21 14:23:03,143 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> detected_encoding: {'encoding': 'ascii', 'confidence': 1.0, 'language': ''}
2023-09-21 14:23:03,144 [DEBUG] [spyder.utils.external.binaryornot.helpers] -> failure: decodable_as_unicode: False
2023-09-21 14:23:03,152 [DEBUG] [spyder.utils.external.binaryornot.check] -> is_binary: 'C:\\Users\\username\\spyder_terminal_err.log'
2023-09-21 14:23:03,174 [DEBUG] [urllib3.connectionpool] -> Starting new HTTP connection (1): 127.0.0.1:8084
2023-09-21 14:23:04,178 [INFO] [spyder.app.mainwindow] -> Loading terminal...
2023-09-21 14:23:04,221 [DEBUG] [spyder.api.plugin_registration.registry] -> Plugin preferences has already loaded
2023-09-21 14:23:04,222 [DEBUG] [spyder.api.plugin_registration.mixins] -> Calling <bound method TerminalPlugin.on_preferences_available of <spyder_terminal.terminalplugin.TerminalPlugin object at 0x00000249D158D5E0>>
2023-09-21 14:23:04,225 [DEBUG] [spyder.api.plugin_registration.registry] -> Plugin editor has already loaded
2023-09-21 14:23:04,225 [DEBUG] [spyder.api.plugin_registration.mixins] -> Calling <bound method TerminalPlugin.on_editor_available of <spyder_terminal.terminalplugin.TerminalPlugin object at 0x00000249D158D5E0>>
2023-09-21 14:23:04,226 [DEBUG] [spyder.api.plugin_registration.registry] -> Plugin project_explorer has already loaded
2023-09-21 14:23:04,226 [DEBUG] [spyder.api.plugin_registration.mixins] -> Calling <bound method TerminalPlugin.on_projects_available of <spyder_terminal.terminalplugin.TerminalPlugin object at 0x00000249D158D5E0>>
2023-09-21 14:23:04,226 [DEBUG] [spyder.api.plugin_registration.registry] -> Plugin workingdir has already loaded
2023-09-21 14:23:04,226 [DEBUG] [spyder.api.plugin_registration.mixins] -> Calling <bound method TerminalPlugin.on_working_directory_available of <spyder_terminal.terminalplugin.TerminalPlugin object at 0x00000249D158D5E0>>
2023-09-21 14:23:04,226 [INFO] [spyder.app.mainwindow] -> Loading old third-party plugins...
2023-09-21 14:23:04,253 [INFO] [spyder.app.mainwindow] -> Creating Menus...
2023-09-21 14:23:04,265 [INFO] [spyder.app.mainwindow] -> Creating toolbars...
2023-09-21 14:23:04,265 [INFO] [spyder.app.mainwindow] -> Setting up main window...
2023-09-21 14:23:04,271 [INFO] [spyder.app.mainwindow] -> Setting up window...
2023-09-21 14:23:04,272 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Spyder Default Layout') (Spyder Default Layout) under context __global for plugin layout
2023-09-21 14:23:04,272 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Rstudio layout') (Rstudio layout) under context __global for plugin layout
2023-09-21 14:23:04,273 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Matlab layout') (Matlab layout) under context __global for plugin layout
2023-09-21 14:23:04,273 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Horizontal split') (Horizontal split) under context __global for plugin layout
2023-09-21 14:23:04,273 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Vertical split') (Vertical split) under context __global for plugin layout
2023-09-21 14:23:05,165 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Spyder Default Layout') (Spyder Default Layout) under context __global for plugin layout
2023-09-21 14:23:05,169 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Rstudio layout') (Rstudio layout) under context __global for plugin layout
2023-09-21 14:23:05,172 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Matlab layout') (Matlab layout) under context __global for plugin layout
2023-09-21 14:23:05,176 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Horizontal split') (Horizontal split) under context __global for plugin layout
2023-09-21 14:23:05,179 [DEBUG] [spyder.utils.registries] -> Registering SpyderAction('Vertical split') (Vertical split) under context __global for plugin layout
2023-09-21 14:23:05,183 [DEBUG] [spyder.plugins.layout.plugin] -> Tabifying new plugins
2023-09-21 14:23:05,184 [INFO] [spyder.plugins.layout.plugin] -> Tabifying terminal plugin for the first time next to [<spyder.plugins.ipythonconsole.plugin.IPythonConsole object at 0x00000249CCC0BCA0>]

If I look in spyder_terminal_err.log which is referred in the log, I see this (the weird characters are there in the actual logfile):
No QCoreApplication instance found. Application patches not applied. You have to call load_stylesheet function after instantiation of QApplication to take effect.
2023-09-21 14:23:05 APP-REKEN05 __main__[32380] INFO Server is now at: 127.0.0.1:8084
2023-09-21 14:23:05 APP-REKEN05 __main__[32380] INFO Shell: C:\Windows\system32\cmd.exe
2023-09-21 14:25:00 APP-REKEN05 __main__[32380] INFO Closing server...

C:\Program Files\Spyder\pkgs\spyder_terminal\server\__main__.py:53: RuntimeWarning: coroutine 'TermManagerBase.shutdown' was never awaited
  application.term_manager.shutdown()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Versions

Spyder version: 5.4.5
Python version: The one shipped with Spyder
Qt version: The one shipped with Spyder
PyQt version: The one shipped with Spyder
Operating System name/version: Windows Server 2016 version 1607

Forgot to mention: a workaround I found is that I can edit ~\.spyder-py3\config\spyder.ini and add
[terminal]
enable = False

However, this is not feasible as many users use this Spyder install and I would then have to set this key for all of them (or instruct them to do it themselves).

Hey @b-a0, thanks for reporting. We're aware of this problem and that's why we decided to stop packaging Spyder-terminal along with our Windows and Mac installers some weeks ago (see pull request #21266).
That change will be available in our next version (5.5.0), to be released next month. In the meantime, please keep using the workaround you found to avoid it.


text:
Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>

Closing because this is empty.

source: gharchive/issue

repo: spyder-ide/spyder

license: MIT

license_type: permissive

license_source: github-api


text:
Cant update conda

Problem Description
What steps will reproduce the problem?
Package Versions

Spyder version: 3.2.8
Python version: 3.6.5
Qt version: 5.9.4
PyQt5 version: 5.9.2
Operating system: Windows 10

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.4.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.23.0 (OK)
numpy >=1.7      :  1.14.3 (OK)
sphinx >=0.6.6   :  1.7.4 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.12.0 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.28.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.4.0 (OK)
pylint >=0.25    :  1.8.4 (OK)

Hello!
I am trying to update conda using anaconda promt : conda update conda. It shows all the packages being downloaded, verified but when it starts to execute - this error occurs.
ERROR conda.core.link:_execute(502): An error occurred while uninstalling package 'defaults::anaconda-5.2.0-py36_3'.
PermissionError(13, 'Access is denied')
it happens on both Mac and Windows. I have full admin rights and I have installed the Anaconda for all users.
Any ideas what can I do here?
thank you
Stan

This is not a problem with Spyder but with Anaconda, so please report it here:
https://github.com/ContinuumIO/anaconda-issues/issues/
The only thing that occurs to me is that you should launch the Anaconda Prompt with admin privileges (on Windows) and run conda update spyder with sudo on macOS.
However, if you're the only user in your computer, you should remove your previous installation and reinstall Anaconda for your user only.

However, if you're the only user in your computer, you should remove your previous installation and reinstall Anaconda for your user only.

That's the recommended installation method because it's less prone to errors.

regarding Windows update - you are right. right click on Anaconda Prompt and run as admin - worked out.


text:
Automatic error report

What steps will reproduce the problem?

1.Tool>preferences>Syntax coloring
2.Selecting spyder dark theme
3.Click ok

This is fixed in our latest version (3.3.0). Please update by opening the Anaconda Prompt and running there
conda update spyder


text:
Improve IPython console Options menu

The Options menu of the IPython console has grown a lot lately:

My idea is to shrink it a bit, like this:
New console
Specialized consoles > Pylab / Sympy / Cython
----
Restart kernel
Connect to an existing kernel
Remove all variables
----
Rename tab
Show env vars
Show sys.path contents
Show elapsed time

Notes:

Specialized consoles would be a submenu but only of the IPython console options menu. The main Consoles menu wouldn't have it.
The last two actions in the screenshot above will be added to all plugins after PR #8192.

@spyder-ide/core-developers, what do you think?

Good thinking; what you have so far is a major improvement. Would these changes also affect the context menu similarly?
A few comments:

Connect to an existing kernel should definitely be in the first group, under Specialized consoles, since it relates to opening a new Console tab (as does the first group) rather than modifying an existing one (as do the other actions in the second group).
Similarly, since Rename Tab modifies the current Console tab, rather than is a general action (like the others in its group), it should go in the second group,
What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Also, a a detail note, I'd suggest naming it something like New IPython console/New specialized console for clarity and parallelism.

Generally I like this.

What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Do we even need a main Console menu? If we do it need it might as well have more things in it.
I've always wondered why the stop command isn't in the menu and the remove variables is.
This might be out of scope but a restart kernel button next to the remove variables could be useful. I've been trapped in a live updating plot and the stop button wouldn't stop it but restart did trick. But it was hard to get focus long enough to click the drop down with a new figure popping up every second :-)

Do we even need a main Console menu?

Yeah, I've always wondered that, since it relates to a particular pane. A few core functions from each pane (run profiler, run static analysis, open project, etc) are present in the menus, but the Consoles pane is the only one that gets its own menu, which is just a curiously abbreviated version of the main Consoles menu. IMO since its dedicated to one and only one pane and is based directly off that pane's menu rather than taking up space in another, we should either just make it identical (ideally sharing the same codebase) to reduce maintenance burden and user confusion, or remove it entirely.

This might be out of scope but a restart kernel button next to the remove variables could be useful.

Maybe out of scope, but agreed—I almost never use Remove Variables but use Restart Kernel all the time.

Ok, so let's go with
New console
Specialized consoles > Pylab / Sympy / Cython
Connect to an existing kernel
----
Restart kernel
Remove all variables
Rename tab
----
Show env vars
Show sys.path contents
Show elapsed time

What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Because the Consoles menu can be much taller than the Options one.

Also, a a detail note, I'd suggest naming it something like New IPython console/New specialized console for clarity and parallelism.

I think that's too detailed and it'd also make the menu too wide.

About your other comments:

I've always wondered why the stop command isn't in the menu and the remove variables is.

I thought it was enough with the stop button. Do you think we should add it? (I'm a bit -1 on it).

This might be out of scope but a restart kernel button next to the remove variables could be useful.

The thing the restart kernel action is blocking (i.e. it freezes the entire interface) so I wouldn't like people to start using it all the time. But if you feel this is important, please open a new issue about it.

I'm confused; that seems backward—you mentioned the Consoles menu wouldn't have it, while the option one would, yet its the Console menu that can be much taller as you say.

Yes, we don't need to create a submenu in the Consoles menu because it can be much taller.

How about New special console

Ok, no problem.

but IMO there should either be a clear rationale for why Remove all variables is in the options menu while the stop button isn't

There's no rationale. I just thought it was not necessary. So let's add it with this work.

@juanis2112, let's go with this for the Options menu:
New console (default settings)
New special console >
    New Pylab console (data plotting)
    New SymPy console (symbolic math)
    New Cython console (Python with C extensions)
Connect to an existing kernel
----
Restart kernel
Interrupt kernel (<- This action will trigger the same action as the stop button)
Remove all variables
Rename tab
----
Show env vars
Show sys.path contents
Show elapsed time

And for the Consoles menu on top, please organize it like this
New console (default settings)
New Pylab console (data plotting)
New SymPy console (symbolic math)
New Cython console (Python with C extensions)
Connect to an existing kernel
----
Restart kernel
Interrupt kernel
Remove all variables

I suggest placing Interrupt kernel above Restart kernel; IMO just seems more intuitive and natural to have interrupt above a complete restart but maybe that's just me.
Is there currently a clear distinction for what goes on the Consoles top-level menu vs. the Consoles pane options menu? If not, I'd consider putting commands that aren't specific to a particular Console sub-tab (e.g. the middle section) only on the Console pane options menu, while including global (first section) or quasi-global (third section) options on both; this also ensures the common sections are identical. Alternatively, if there isn't a clear distinction other than subjection personal perception, since the Consoles menu can be longer anyway I'd just make then identical to be consistent.

Yes, we don't need to create a submenu in the Consoles menu because it can be much taller.

Oh, I see—I interpreted your original comment to mean those options wouldn't be included at all.

There's no rationale. I just thought it was not necessary. So let's add it with this work.

Okay, sure, if you think so.

authors: CAM-Gerlach bcolsen ccordoba12


text:
Receiving error when i try to open table from variable explorer in Spyder3 ide.

Description
What steps will reproduce the problem?

Create a 3 column pandas dataframe with data type: int64 and 60810 rows. (numerical_data)
fit and transform data using sklearn simple imputer
try to open table from variable explorer

What is the expected output? What do you see instead?
I should see the table
Please provide any additional information below
from sklearn.impute import SimpleImputer
import numpy as np
imputer = SimpleImputer(missing_values=np.nan, strategy="most_frequent")
imputer = imputer.fit(numerical_data)
numerical_data = imputer.transform(numerical_data)
File "/usr/lib/python3/dist-packages/spyder/widgets/variableexplorer/collectionseditor.py", line 449, in createEditor
if not editor.setup_and_check(value, title=key, readonly=readonly):
File "/usr/lib/python3/dist-packages/spyder/widgets/variableexplorer/arrayeditor.py", line 619, in setup_and_check
self.data.flags.writeable = True
ValueError: cannot set WRITEABLE flag to True of this array
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.7
Qt Versions: 5.9.5, PyQt5 5.10.1 on Linux

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.3.1 (OK)
pandas >=0.13.1  :  0.23.0 (OK)
numpy >=1.7      :  1.16.2 (OK)
sphinx >=0.6.6   :  1.6.7 (OK)
rope >=0.9.4     :  0.10.5 (OK)
jedi >=0.9.0     :  0.13.3 (OK)
psutil >=0.3     :  5.6.1 (OK)
nbconvert >=4.0  :  5.4.1 (OK)
sympy >=0.7.3    :  None (NOK)
cython >=0.21    :  0.29.7 (OK)
qtconsole >=4.2.0:  4.4.3 (OK)
IPython >=4.0    :  7.3.0 (OK)
pylint >=0.25    :  2.3.1 (OK)

This is fixed in our latest version (3.3.4). Please update.


text:
PR: Move Pylint plugin to new API

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[x] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Took the opportunity to simplify the buttons so that it is similar to find in files (start/stop are the same button)

Issue(s) Resolved

Depends on #11741
Fixes #12183
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @goanpeca

Hello @goanpeca! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/api/widgets.py:

Line 452:80: E501 line too long (82 > 79 characters)
Line 696:80: E501 line too long (85 > 79 characters)

In the file spyder/plugins/ipythonconsole/plugin.py:

Line 423:21: E222 multiple spaces after operator

In the file spyder/plugins/pylint/plugin.py:

Line 72:80: E501 line too long (81 > 79 characters)
Line 102:80: E501 line too long (81 > 79 characters)
Line 129:80: E501 line too long (80 > 79 characters)
Line 201:1: W293 blank line contains whitespace

In the file spyder/plugins/pylint/widgets/pylintgui.py:

Line 173:40: E261 at least two spaces before inline comment
Line 292:71: W291 trailing whitespace
Line 296:71: W291 trailing whitespace

/binder

Some comments about this PR:

The shortcut F8 is not working for running the code analysis
Clicking on an element in the pane (warning, error, message) doesn't go to the line corresponding to this element. However if I close the file and click the error message in the pane it opens the file (but again it doesn't go to the corresponding line) This was a bug that we found and it was fixed by @ccordoba12  in 4.1.4 so not sure why it is not working here. I tested it in 4x and it works fine.
The hamburger menu doesn't have the expand/collapse items that it had before.
When selecting a file in the pane with the "Select python file" button, the analysis doesn't run automatically which it did before. It does display the path of the file selected in the combobox but when pressing analyze, it runs the analysis on the file that is selected in the editor and displays the path of this last file in the combobox.
When reducing the width of the pane it is noticeable that there is some sort of "invisible" item between the analyze button and the hamburger menu button which shouldn't be there. In contrast, the combobox should take the full space when the width is less (as it did before in 4.x)

Hi @juanis2112, thanks for the review:

The shortcut F8 is not working for running the code analysis

I cannot reproduce this. On my Mac pressing Fn+F8 run the analysis as expected.

Clicking on an element in the pane (warning, error, message) doesn't go to the line corresponding to this element.

Fixed

The hamburger menu doesn't have the expand/collapse items that it had before.

Fixed

When selecting a file in the pane with the "Select python file" button, the analysis doesn't run automatically which it did before

Fixed

When reducing the width of the pane it is noticeable that there is some sort of "invisible" item between the analyze button

Fixed

more differences between 4.x and this PR:

Fixed.

/show binder

The shortcut F8 is not working for running the code analysis

This is still a problem on Linux and Windows. Please check it on a virtual machine.
All the other problems reported by @juanis2112 and I are solved now. Great job @goanpeca!

This is still a problem on Linux and Windows. Please check it on a virtual machine.

Could not reproduce but introduced a change that might help. Could you check @juanis2112, @ccordoba12 ?

Could not reproduce but introduced a change that might help.

It's working now. Thanks @goanpeca.
@dalthviz will give this one a final manual review and if he finds everything in order, he'll merge it.

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point):

This one is related to this PR, I will fix!
Thanks @dalthviz :-)

This error is also present in 4.1.4 so I will create an issue or maybe already one is open @ccordoba12 ?

Please open a new issue about this one. I don't remember seeing this reported yet.

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point):

@dalthviz I could not reproduce on Mac, will check on a Win VM and see if it is a windows thing only.

@goanpeca, please address this comment from @dalthviz:

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point)

so we can merge it.

@dalthviz I could not reproduce on Mac, will check on a Win VM and see if it is a windows thing only.

I cannot reproduce this on the windows VM, any particular thing that might be triggering it?

@goanpeca after checking a little bit more seems like the strange behavior is related with the way the toolbars are being contracted (sometimes the resize gets stuck, although I don't now why):

Looking at the code seems like a custom handling is being implemented for the resizeEvent to emit a custom signal: https://github.com/spyder-ide/spyder/blob/a24398264e5cb5dbbb72fda6a35555fd08fb40a4/spyder/api/widgets/init.py#L540-L545. Maybe that could be causing the resize to get stuck?

Thanks for checking @dalthviz. Just to check is it associated to the speed in which you move?

Looking at the code seems like a custom handling is being implemented for the resizeEvent to emit a custom signal:

Correct, that change was needed to be able to have the toolbar items use as much area as possible.
Question: If you do it slowly it does not get stuck, but if you do it faster it does?

@dalthviz made some small changes to see if the situation improves.
Does increasing this number helps?
https://github.com/spyder-ide/spyder/pull/12160/files#diff-f34c043d56467c819418192611e89a6eR421

@goanpeca checked again and seems the problem is still there :/

Question: If you do it slowly it does not get stuck, but if you do it faster it does?

The behavior is the same

Does increasing this number helps?

I'm not sure what number is that, is an option?
From what I'm seeing seems like the resize signal is applying only for the first toolbar that isn't contracted from right to left. So, to contract the rest, you need to again start the resize action. Maybe this GIF illustrates that (first the working directory toolbar needs two resize events to contract - probably do the combobox - and then the rest of the toolbars need one resize event each):

From what I'm seeing seems like the resize signal is applying only for the first toolbar that isn't contracted from right to left. So, to contract the rest, you need to again start the resize action. Maybe this GIF illustrates that (first the working directory toolbar needs two resize events to contract - probably do the combobox - and then the rest of the toolbars need one resize event each)

Thanks @dalthviz, I understand what you mean. However the changes  I made refer to the toolbar in the Docks (each pane has now the options as a toolbar)

But it should now have any effect on the application toolbars. It seems like it is a separate issue. On master you see the same behavior?

Checking with master (3bf92535c) I don't see that behavior:

@dalthviz I cannot reproduce on any of the systems (binder linux) local mac and Win 10 VM. It is going to be really hard to try to fix something I cannot reproduce.
Could we add an item to https://github.com/spyder-ide/spyder/issues/13527 and move forward. Seems like a very minor issue to block this PR from merging.

Could we add an item to #13527 and move forward

I don't agree with this. Please set up a Zoom call with @dalthviz so they two of you can fix this issue.

@ccordoba12 the issue stems from trying to address this comment:

If I revert the "fix", then the problem is gone, but the "invisible" item is back.
That is a problem that affects all plugins that provide a widget inside the Pane (like the combobox in this case) and it deserves a fix that covers all widgets. It is not a problem specific to this Plugin, even if it was a comment that came out of reviewing it.

@dalthviz please create an event whenever it suits you. Available hours are visible on the company calendar.

I don't agree with this. Please set up a Zoom call with @dalthviz so the two of you can fix this issue.

Fair enough, but even if you do not agree with this, @dalthviz should be able to have also an opinion and a vote, after all the question was addressed to him.

@dalthviz please create an event whenever it suits you. My available hours are visible on my company calendar.

Ok :+1: done

@goanpeca please rebase this one to get the changes done in #13600

@goanpeca please rebase this one to get the changes done in #13600

Done @dalthviz.

/show binder

@goanpeca left a question and also I think this plugin should use the spinner. Besides that LGTM 👍

Thanks for the feedback @dalthviz, made the requested fix.

@andfoy @steff456 could you give to this PR a manual test on Linux and Mac? Thanks!

/show binder

Hi @goanpeca and @dalthviz,
With @andfoy we manually review this PR and everything is working as expected.

@goanpeca one last comment, please unify the use of " to enclose strings, there is a mix (as an example the pylint main_widget.py in the setup of the actions) and using just " could improve future readability of the code. Thanks!

Fixed @dalthviz.

Edit: Seems like the Analyze button always triggers the action using the current filename in the Editor

Bug!
Will fix.

Hey @dalthviz, is this one ready for merge?

@ccordoba12 I would say that some testing could be nice, otherwise the missing thing is a squash

source: gharchive/pull-request


text:
Quantities - values & units normalization as calculated element

In the transformation phase, we can precalculate quantity in basic units to be able to compare quantities originally entered in different units. It could be done using UCUM formulas for context-free units and context-dependent algorithms can be applied for specific measurements like Glucose in grams or molls.
valueQuanity:
    value: 97.88
    unit: 'F'
   # calculated
    basicValue: 36.6
    basicUnit: 'C'

Another idea is to change the value and unit to normalized and move original to extension:
valueQuanity:
    extension: [{url: original-quanity, valueQuanityt: {value: 97, unit: 'F'}}]
    value: 36
    unit: 'C'

This will allow:

to be valid FHIR
Do not create extra field if value already in metric system

I like it! Can we say anything about the metric units in lab results? For example, if a result can be represented as milligrams/deciliter or grams/liter, it would be good to standardize on a unit to simplify calculations in queries while retaining the reported units for display.

authors: gotdan niquola

repo: sql-on-fhir/sql-on-fhir


text:
Copy-DbaDatabase fails with Backup Failed | Invalid column name 'State'

Slack Community Channel: https://sqlcommunity.slack.com/messages/C1M2WEASG/ (get an invite: https://dbatools.io/slack/)
Documentation within the module: Get-Help <command>
Database Administrator on Stack Exchange network, dbatools tag: https://dba.stackexchange.com/questions/tagged/dbatools
StackOverflow dbatools tag: https://stackoverflow.com/questions/tagged/dbatools

I'm trying to migrate databases in an instance that has a Japanese collation to a new instance on a  new server. I can't get dbatools commands to backup theses databases.  It works for other instances on the same cluster that have the default collation.

Could you let me have the exact collation you're using please. There's a couple of Japanese ones, and the one I'm using appears to be OK

Stuart,
This is the collation that is being used: Japanese_CS_AS
Dennis
On Tue, Oct 15, 2019 at 10:17 AM Stuart Moore notifications@github.com
wrote:

Could you let me have the exact collation you're using please. There's a
couple of Japanese ones, and the one I'm using appears to be OK
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/6092?email_source=notifications&email_token=ANNG5SYSLL5PL6TUCMXQJJTQOXGHBA5CNFSM4I6DPW5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBI5WVY#issuecomment-542235479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANNG5S4WUK2CL7VYXEQG7T3QOXGHBANCNFSM4I6DPW5A
.

Thanks Dennis.
Looks like it's a Case Sensitivity issue that Shaun fixed in https://github.com/sqlcollaborative/dbatools/pull/6032/
That should be in the latest published version of the module (1.0.53).  If you're not running that, could you update and try it again please.
If you're already on that version, let me know as it'll be something different.
Working ok with my test instance:

Stuart,
Thanks for the update.  I downloaded the latest version and installed it on
my server.  That fixed my issue and worked like a charm.
Is there a command to find out the version of dbatools that is installed?
Dennis
On Wed, Oct 16, 2019 at 3:08 AM Stuart Moore notifications@github.com
wrote:

Thanks Dennis.
Looks like it's a Case Sensitivity issue that Shaun fixed in #6032
https://github.com/sqlcollaborative/dbatools/pull/6032
That should be in the latest published version of the module (1.0.53). If
you're not running that, could you update and try it again please.
If you're already on that version, let me know as it'll be something
different.
Working ok with my test instance:
[image: image]
https://user-images.githubusercontent.com/5613670/66896060-167b2400-efec-11e9-9cf7-0acac51fa4f7.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/6092?email_source=notifications&email_token=ANNG5S3Y4FOPZBNM2XY5PJLQO24WRA5CNFSM4I6DPW5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBLL6UA#issuecomment-542555984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANNG5SZQLGSVFBWVBEBF3JTQO24WRANCNFSM4I6DPW5A
.

You're welcome. The easiest way to check is with:
Get-Module dbatools -ListAvailable
By default PS will load the newest version

repo: sqlcollaborative/dbatools


text:
TrackPad Woes

I don't know if anyone even checks up on this anymore but I've been having so many issues. I finally got a booting system and the screenpad lights up but i cannot get the trackpad to work for the life of me! it boots but then you can't use the trackpad as an actual trackpad. I don't know where to go from here and I hope someone has a solution

only difference is mine is a ux434fac rather than an lc