Most of my projects are on Bitbucket at the moment but will be moved to GitHub soon due to the shutdown of mercurial support.
See: https://bitbucket.org/labscript_suite/
Location
Australia
Education
PhD (Physics), BSc Advanced with honours (first class honours in Physics, majors: physics, maths)
Is PySide2 actually ready from primetime use? The list of known issues on the wiki doesn't fill me with confidence and there are a large number of bugs on the tracker.
I'm in agreement that Qt for Python (PySide2) is likely the best option in the long term due to the first party maintenance by Qt, but I'm concerned it's not as stable as PyQt5 yet.
I haven't noticed anything major as of yet, and anyway, you know how it goes: adoption usually speeds up bugfixes.
I'd recommend to start building with PySide2; by time your project is finished, it will be stable. Or else, worse case, you just change your import statements and leave the rest the same. ;)
Most of my projects are on Bitbucket at the moment but will be moved to GitHub soon due to the shutdown of mercurial support.
See: https://bitbucket.org/labscript_suite/
Location
Australia
Education
PhD (Physics), BSc Advanced with honours (first class honours in Physics, majors: physics, maths)
I already have a large project that was ported from PySide1 to PyQt and it was non-trivial to do (sure most of it was the same but that couple of percent difference was a pain to find and update), so I'm not keen to repeat that experience until it's worth it. Sounds like maybe I should wait a bit longer or look into using qtpy as an abstraction layer.
I think that was a newer thing about Qt5...that PySide2 and PyQt5 had identical APIs. But I could be wrong. The abstraction layer sounds wise in any case.
Define "very much maintained". PySide2 regularly releases updates at roughly the same frequency as PyQt5. In fact, if you look at the dates, PySide2 usually releases a few days before PyQt5!
People make mistakes. He learned something and recanted. That's praiseworthy, not something to condemn for. Or have you never misspoken in your entire life?
Please don't attack someone for recanting ever again. That sort of hateful reaction is why people are afraid to admit mistakes. Respond to others the same way you'd want them to respond to you.
Point well taken. Without the necessary information, my response was unwarranted. That leads me into my question for you: do you think he made a mistake, though? You did seem to ask him for clarification on the matter, but then you immediately countered his claim. Puzzling.
I read again, and I don't see where I asked for clarification. I was countering amohgyebi at the end there, not the earlier person/people in the thread, in any case.
Did you not write "define not very much maintained", and then in the same post counter the very statement you quoted? Both of us are in the wrong. Peace.
Uhm, no. I countered the common meaning of "not very much maintained" to save time, but left room for him to correct his meaning if I missed it. It wasn't aggressive. So no, we're not "both in the wrong." You attacked someone, unbidden, for apologizing for a mistake he made months ago, which none of the people originally party to felt the need to continue.
But whether you choose to learn from this is up to you.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
LMAO, if you think that my asking if he normally goes around posting negative reviews. Stop playing the victim card. I have no idea as to how old you are, but in the real world you DON'T get to run around dismissing this or that, and NOT get called out for it. You have NO IDEA what an "attack" is. Grow up, and good day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is PySide2 actually ready from primetime use? The list of known issues on the wiki doesn't fill me with confidence and there are a large number of bugs on the tracker.
I'm in agreement that Qt for Python (PySide2) is likely the best option in the long term due to the first party maintenance by Qt, but I'm concerned it's not as stable as PyQt5 yet.
I haven't noticed anything major as of yet, and anyway, you know how it goes: adoption usually speeds up bugfixes.
I'd recommend to start building with PySide2; by time your project is finished, it will be stable. Or else, worse case, you just change your import statements and leave the rest the same. ;)
I already have a large project that was ported from PySide1 to PyQt and it was non-trivial to do (sure most of it was the same but that couple of percent difference was a pain to find and update), so I'm not keen to repeat that experience until it's worth it. Sounds like maybe I should wait a bit longer or look into using qtpy as an abstraction layer.
I think that was a newer thing about Qt5...that PySide2 and PyQt5 had identical APIs. But I could be wrong. The abstraction layer sounds wise in any case.
Pyside2 is still not very much maintained like PyQt5
Define "very much maintained". PySide2 regularly releases updates at roughly the same frequency as PyQt5. In fact, if you look at the dates, PySide2 usually releases a few days before PyQt5!
ok my bad
Do you normally just go around posting negative reviews and saying "ok my bad" when you've been called out? Enough already.
That was uncalled for.
It's been edited, but clearly the guy was accusing the product of not doing something, and only recanted when you corrected him.
People make mistakes. He learned something and recanted. That's praiseworthy, not something to condemn for. Or have you never misspoken in your entire life?
Please don't attack someone for recanting ever again. That sort of hateful reaction is why people are afraid to admit mistakes. Respond to others the same way you'd want them to respond to you.
Point well taken. Without the necessary information, my response was unwarranted. That leads me into my question for you: do you think he made a mistake, though? You did seem to ask him for clarification on the matter, but then you immediately countered his claim. Puzzling.
I read again, and I don't see where I asked for clarification. I was countering amohgyebi at the end there, not the earlier person/people in the thread, in any case.
Did you not write "define not very much maintained", and then in the same post counter the very statement you quoted? Both of us are in the wrong. Peace.
Uhm, no. I countered the common meaning of "not very much maintained" to save time, but left room for him to correct his meaning if I missed it. It wasn't aggressive. So no, we're not "both in the wrong." You attacked someone, unbidden, for apologizing for a mistake he made months ago, which none of the people originally party to felt the need to continue.
But whether you choose to learn from this is up to you.
LMAO, if you think that my asking if he normally goes around posting negative reviews. Stop playing the victim card. I have no idea as to how old you are, but in the real world you DON'T get to run around dismissing this or that, and NOT get called out for it. You have NO IDEA what an "attack" is. Grow up, and good day.