-
Notifications
You must be signed in to change notification settings - Fork 53
Sip import fix #30
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
base: master
Are you sure you want to change the base?
Sip import fix #30
Conversation
changed compat.py to rely on the qtpy package and deleted some of the files listed in #7
Added qtpy to reqirements, cleaned up compat.py
OK about to test now. |
If anything breaks in your env would you mind listing it here? |
It works OK for me - i get 9 failed tests though and "cannot import sip" still |
test accept/reject for CSVDialogs: qapp = <PySide.QtGui.QApplication object at 0x00000000069AAE08>
E Failed: Qt exceptions in virtual methods: |
same test accept reject Traceback (most recent call last):
E assert True == False test_CSVDialogs.py:269: AssertionError |
F
E Failed: DID NOT RAISE <class 'TypeError'> test_DataFrameModel.py:66: Failed |
HOTTIP: delete one thing at a time Don't be like me if you need to remove somethings do it methodically.
Moved the contents of test/main.py to test/test_DataFrameModelManager.py that way I can actually run the tests after a fresh install. Commented out some requirements in setup.py.
Okay try to do a fresh install of this last commit. I managed to get all of the tests to at least open at last count I have 5 failed, 147 passed, 2 errors. |
@@ -1,4 +1,3 @@ | |||
recursive-include qtpandas *.py | |||
recursive-include qtpandas/_lib * | |||
recursive-include qtpandas/i18n *.qm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted this line b/c I deleted the corresponding directory.
from PySide.QtCore import Slot, Signal | ||
|
||
|
||
QtCore = QtCore_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference b/t _QtCore
and QtCore_
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think there would be any difference just looks like the variable name the author chose.
@@ -8,41 +8,3 @@ | |||
lib = os.path.join(BASEDIR, '_lib', 'magic') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of this should probably be deleted.
I just fetched the latest and im testing it now and failing 9/154. I think we should change the signals to regular python types, right now there are strings like the following: Line 501 qtpandas/qtpandas/views/CSVDialogs.py I want to change 'QBool' to bool on all the signals. Do you know any reason why I shouldn't do that? Error in test: E ________________________________________________________________________________ |
The only reason I can think is that Qbool might be some kind of C++ implementation of a bool. IDK go ahead and try it. I'll poke around and see what I can find about Qbool. |
I realized that I changed 'QBool' to 'bool' when it probably should have been just bool.
@@ -120,7 +120,7 @@ def _initUI(self): | |||
layout.addWidget(self.otherSeparatorLineEdit) | |||
self.setLayout(layout) | |||
|
|||
@Slot('QBool') | |||
@Slot('bool') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant bool as in the python type rather than a string that says 'bool' - sorry lol.. @draperjames
Yeah it has worked pretty well for me. I also went back to the original pandas-qt repo and installed it in a python27 env, ran pytest on tests, it hit error pretty early on in in the cycle and exited pytest. So now I'm thinking that I either cocked-up the install or we have actually made some real improvements! |
@zbarge try testing out this fork when you get the chance and let me know how it work for you. I haven't had any problems.