Bug 363607

Summary:	Import statements pollute the variable model
Product:	[Applications] cantor	Reporter:	Alexander Semke <alexander.semke>
Component:	python2-backend	Assignee:	Alexander Semke <alexander.semke>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alexanderrieder
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:	https://commits.kde.org/cantor/b9233f89861069bad0db8b6a134f6fd2786e806e	Version Fixed/Implemented In:	18.03
Sentry Crash Report:

Description Alexander Semke 2016-05-27 21:00:58 UTC

Importing of python modules leads to new entries in the variable model. Looks like an entry is created for each addition import within the modules being imported. The user expects to see in the variable model only variables created by himself. Any internal details of used modules are of interest or of any usage here.

Reproducible: Always

Steps to Reproduce:
1. create a python session and do "import numpy"
2. in the variable manager observe new variables with the names "numpy", "sys", "scipy" and "matplotlib"

Comment 1 Alexander Semke 2018-01-13 13:25:51 UTC

Git commit b9233f89861069bad0db8b6a134f6fd2786e806e by Alexander Semke.
Committed on 13/01/2018 at 13:24.
Pushed by asemke into branch 'master'.

Don't add imported python module names to the variable model and manager.
FIXED-IN: 18.03

M  +7    -10   src/backends/python/pythonsession.cpp

https://commits.kde.org/cantor/b9233f89861069bad0db8b6a134f6fd2786e806e