Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PR: Add explicit imports to QtSvg module #55

Merged
merged 2 commits into from Aug 20, 2016
Merged

Conversation

goanpeca
Copy link
Member

@goanpeca goanpeca commented Aug 3, 2016

@ccordoba12, @Nodd should we delete PYQT4, PYQT5, PYSIDE, PythonQtError from the module at the end?

del PYQT4, PYQT5, PYSIDE, PythonQtError ?

@ccordoba12 ccordoba12 added this to the v1.2 milestone Aug 3, 2016
@ccordoba12
Copy link
Member

should we delete PYQT4, PYQT5, PYSIDE, PythonQtError

I don't think so because they don't belong to the module itself. @Nodd?

@goanpeca
Copy link
Member Author

goanpeca commented Aug 3, 2016

Ehh ??
precisely because they dont belong and would remain in the namespace is that I am asking if we should delete them.

@ccordoba12
Copy link
Member

I really don't see the need of it. That's normally how Python works, i.e. imported symbols remain in the namespace.

@goanpeca
Copy link
Member Author

goanpeca commented Aug 3, 2016

Yes, I know how it works... this not about how python works or does not, but a user would be able to import PYQT4 from QtCore module and it should not, cause those symbols live in qtpy. not int qtpy.QtCore. We should not encourage that use

@ccordoba12
Copy link
Member

I doubt anyone would confuse our constants with proper Qt objects, but I'm neutral about removing or leaving them.

Besides, this needs a rebase now ;-)

@Nodd
Copy link
Contributor

Nodd commented Aug 9, 2016

I think that deleting them is indeed cleaner. I don't hink that many users would import it from here, but for example vars(QtSvg) shouldn't show it.

@ccordoba12
Copy link
Member

@goanpeca, would you mind to rebase and finish this one so we can merge it?

I agree with @Nodd on removing the PY* constants on every qtpy module :-)

@goanpeca
Copy link
Member Author

ok , will do :-)

@goanpeca goanpeca self-assigned this Aug 16, 2016
@goanpeca
Copy link
Member Author

@ccordoba12, see :-p, its the fastest by far

image

@ccordoba12
Copy link
Member

This looks good to me :-)

@ccordoba12 ccordoba12 merged commit a4cc859 into master Aug 20, 2016
@ccordoba12 ccordoba12 deleted the feature/import-qtsvg branch August 20, 2016 15:36
ccordoba12 added a commit that referenced this pull request Jan 2, 2017
Use star imports in QtSvg again instead of direct ones (reverts PR #55)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants