The best place to ask for help with any of Riverbank's software is one of the mailing lists. However, there are steps you can take first to help people on the lists to help you.
Read Mike Ash's Getting Answers.
Unless you are a commercial customer, do not email Riverbank directly.
Search the mailing list archives to see if your question has already been answered.
Consider if the question is specific to PyQt or is a general Qt question. There are more C++ programmers using Qt than there are Python programmers, so if it's a general Qt question then you may be better using QtCentre, the KDE Forum or one of the KDE mailing lists.
When faced with a problem in your code it may seem that posting the fragment of your code that you think is causing the problem is the right thing to do. However this is rarely the case. If somebody is to help you then the first thing they will want to do is to reproduce the problem, so a code fragment is no good. Don't be surprised if you are asked to post a small but complete example that demonstrates the problem. Another reason for asking for this is that, in many cases, you will realise what the problem is while you are producing the example and wont need to ask a question at all.
If you are having a problem with the code generated by
then post the
.ui file that is causing the problem.
If you are posting code then do so as an attachment and do not embed it as part of your message. This will prevent mail systems from wrapping long lines or messing with the indentation.