I've updated the Debian packages in the Debian Experimental repository for
testing (just Sip 4.1.5 so far, but I'll upload 4.15.1 shortly). I tried
rebuilding the current Debian PyKDE package (4.10.5) and it failed to build
(last part of the build log attached). I tried locally with 4.15.1
On Saturday, August 24, 2013 06:07:25 Arfrever Frehtes Taifersar Arahesis
wrote:
2013-08-24 05:17 Scott Kitterman napisał(a):
I've updated the Debian packages in the Debian Experimental repository for
testing (just Sip 4.1.5 so far, but I'll upload 4.15.1 shortly). I tried
rebuilding
Shriramana Sharma samj...@gmail.com wrote:
Hello. Trying to compile PyQt5 on my Kubuntu Raring system, I had
problems: the SIP version was too old, backporting the latest from
Debian broke the existing PyQt4 packages because they depend on an
older SIP API, and that removed the existing
Phil Thompson p...@riverbankcomputing.com wrote:
On Tue, 25 Jun 2013 20:46:57 +0530, Shriramana Sharma
samj...@gmail.com
wrote:
On Tue, Jun 25, 2013 at 8:19 PM, Phil Thompson
p...@riverbankcomputing.com wrote:
The code generator is the same for all Python versions.
Hi thanks for this
On Monday, June 17, 2013 10:13:32 AM Phil Thompson wrote:
SIP v4.14.7 has been released. This is a minor functional release but is
required by PyQt v5.
It would be nice if new SIP versions that introduce a new major API version
number weren't described as a minor functional release. It seems
On Tuesday, June 18, 2013 11:21:33 PM Phil Thompson wrote:
On Tue, 18 Jun 2013 16:40:25 -0400, Scott Kitterman deb...@kitterman.com
wrote:
On Monday, June 17, 2013 10:13:32 AM Phil Thompson wrote:
SIP v4.14.7 has been released. This is a minor functional release but
is
required
I'm not if this is an actual bug or a user error, but a PyQt bug was just
filed in Debian:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=702445
The reporter has 4.9.3, but I get the same with 4.9.6 and 4.10:
Python 2.7.3 (default, Jan 26 2013, 15:27:56)
[GCC 4.7.2] on linux2
Type help,
On Wednesday, March 06, 2013 10:14:22 PM Phil Thompson wrote:
On Wed, 06 Mar 2013 14:51:35 -0500, Scott Kitterman deb...@kitterman.com
wrote:
I'm not if this is an actual bug or a user error, but a PyQt bug was
just
filed in Debian:
bugs.debian.org/cgi-bin/bugreport.cgi?bug
/python2.7
Patch by Scott Kitterman sc...@kitterman.com, will be sent upstream
Index: qscintilla2-2.7.1/Python/configure.py
===
--- qscintilla2-2.7.1.orig/Python/configure.py 2013-03-06 16:46:05.860789440 -0500
+++ qscintilla2-2.7.1/Python
You absolutely can as long as you comply with the license.
Scott K
Joe Borġ m...@jdborg.com wrote:
Are you going to sell the product, or use use it as your University
project?
If it's the latter, you're fine. But I don't think you can use PyQt
(or Qt
libraries) for profit.
Regards,
Joseph
On Saturday, October 20, 2012 08:11:29 AM Mark Summerfield wrote:
I have built local versions of Qt 4.8.3, Python, SIP, and PyQt on an
Xubuntu machine which has Qt 4.8.1 as its system Qt:
...
So clearly, despite trying to build using my local Qt, PyQt seems to be
looking at the system Qt.
Starting with python3.3, python will support multiarch [1] in Debian and
Ubuntu. As part of this change, the path for some of the Python header files
has changed, so I need to specify multiple include directories. Here's an
example using pkg-config so show the difference between python3.2 and
On Saturday, October 20, 2012 08:44:25 PM Scott Kitterman wrote:
Starting with python3.3, python will support multiarch [1] in Debian and
Ubuntu. As part of this change, the path for some of the Python header
files has changed, so I need to specify multiple include directories.
Here's
On Saturday, October 20, 2012 10:42:07 PM Scott Kitterman wrote:
On Saturday, October 20, 2012 08:44:25 PM Scott Kitterman wrote:
Starting with python3.3, python will support multiarch [1] in Debian and
Ubuntu. As part of this change, the path for some of the Python header
files has
On Wednesday, October 03, 2012 10:23:16 AM Luca Beltrame wrote:
In data martedì 2 ottobre 2012 12:35:10, Scott Kitterman ha scritto:
Is there a chance you could IFDEF that instead of just removing the
definition so that 4.10 can be backported to releases with the older PyQt?
I'm not sure
On Wednesday, October 03, 2012 03:21:02 PM Luca Beltrame wrote:
In data mercoledì 3 ottobre 2012 14:16:33, Phil Thompson ha scritto:
In your configure.py (or whatever) pass -x PyKDE_UseMyMappedType to sip in
order to *disable* it.
Thanks, I have an idea of how to do this then. Scott, do
On Wednesday, October 03, 2012 09:43:24 PM Luca Beltrame wrote:
In data mercoledì 03 ottobre 2012 09:31:57, Scott Kitterman ha scritto:
Not immediate ones. As long as it gets into 4.10 by it's beta release, it
won't affect anything we have to do.
Turns out it was quite easy to do: try
On Wednesday, October 03, 2012 11:28:48 PM Luca Beltrame wrote:
In data mercoledì 03 ottobre 2012 23:22:46, Luca Beltrame ha scritto:
Can you give me the hex version of PyQt? I'll adjust the check and see
whether it works or not.
I made the check a little less lax. Can you try and see
On Monday, October 01, 2012 11:46:52 AM Rex Dieter wrote:
Get a bunch of these trying to (re)build pykde4 against recent sip/PyQt
release:
sip: /builddir/build/BUILD/pykde4-4.9.2/sip/kdecore/typedefs.sip:955: Mapped
type has already been defined in another module
make[2]: ***
On Tuesday, October 02, 2012 04:32:34 PM Luca Beltrame wrote:
In data martedì 2 ottobre 2012 10:27:33, Scott Kitterman ha scritto:
Same error in Debian with 4.8.2.
I fixed it in PyKDE4's git repository by removing the duplicated definition.
However I can't backport it because it would break
Phil Thompson p...@riverbankcomputing.com wrote:
The current PyQt snapshot has support for the following modules built
against Qt v5-beta1...
QtCore, QtGui, QtHelp, QtNetwork, QtSql, QtSvg, QtWebKit, QtXml
You will also need current SIP and QScintilla snapshots.
Are you planning a new set of
Phil Thompson p...@riverbankcomputing.com wrote:
On Fri, 13 Jul 2012 09:02:30 -0400, Scott Kitterman
deb...@kitterman.com
wrote:
On Friday, July 13, 2012 01:40:38 PM Phil Thompson wrote:
On Wed, 11 Jul 2012 20:07:46 -0400, Scott Kitterman
deb...@kitterman.com
wrote:
If you run pyuic4 -o
On Friday, July 13, 2012 01:40:38 PM Phil Thompson wrote:
On Wed, 11 Jul 2012 20:07:46 -0400, Scott Kitterman deb...@kitterman.com
wrote:
If you run pyuic4 -o video_ui.py video.ui with the two attached files,
it
works fine with 4.9.1, but fails with 4.9.3. The error I get
If you run pyuic4 -o video_ui.py video.ui with the two attached files, it
works fine with 4.9.1, but fails with 4.9.3. The error I get is:
Unknown Qt widget: Phonon.VideoPlayer
Was there a change that weboob (where the two files were taken from) needs to
adapt to?
Scott K# -*- coding: utf-8
On Monday, June 25, 2012 08:55:30 PM Hans-Peter Jansen wrote:
@Scott: here's how I solved this (line 96 ff.):
https://build.opensuse.org/package/view_file?file=python-qt4.specpackage=py
thon-qt4project=home%3Afrispete%3APyQtrev=6161032f9d1629c3293dd3356c02dc49
Thank you. I'll give something
On Sunday, June 24, 2012 06:32:44 PM Phil Thompson wrote:
...
If these flags are Debian standard then why not add them to Qt's spec file
for Debian? PyQt will then pick them up automatically.
Thanks for the suggestion. I'm not the Debian Qt maintainer, so I can't just
do it, but I'll discuss
I tried this out in an 11.04 chroot. Things that get overwritten from the
distributionPyQt package:
/usr/share/sip/PyQt4/
/usr/bin/pyuic4
/usr/bin/pylupdate4
/usr/bin/pyrcc4
/usr/lib/qt4/plugins/designer/libpythonplugin.so (designer plugin)
Except for the designer plugin, these are all
On Saturday, June 23, 2012 10:15:13 AM Phil Thompson wrote:
On Sat, 23 Jun 2012 10:07:02 +0100, Andrew Suffield
asuffi...@suffields.me.uk wrote:
On Sat, Jun 23, 2012 at 09:57:56AM +0100, Phil Thompson wrote:
Why? Does Debian need it to be called CPPFLAGS specifically rather than
the
On Friday, June 22, 2012 09:03:33 AM Phil Thompson wrote:
On Thu, 21 Jun 2012 22:26:37 -0400, Scott Kitterman deb...@kitterman.com
wrote:
PyQt 4.9.1 builds fine with all the Pythons we currently have in Debian
Unstable (2.6/2.7/3.2). PyQt 4.9.2 does fine building with 2.6/2.7, but
fails
On Friday, June 22, 2012 04:14:08 PM Phil Thompson wrote:
On Fri, 22 Jun 2012 10:52:22 -0400, Scott Kitterman deb...@kitterman.com
wrote:
On Friday, June 22, 2012 09:03:33 AM Phil Thompson wrote:
On Thu, 21 Jun 2012 22:26:37 -0400, Scott Kitterman
deb...@kitterman.com
wrote:
PyQt
say much for it beyond that as I'm not sure I've fully
grokked what's going on in siputils.py. If this seams reasonable, I intend to
attack PyQt4 and QScintilla2 also.
Scott K
Description: Extend configure.py and siputils.py to support external
definition of CPPFLAGS
Author: Scott Kitterman sc
This one should have been forwarded as well.
Scott K
Index: python-qt4-4.9.2/configure.py
===
--- python-qt4-4.9.2.orig/configure.py 2012-06-21 15:56:58.711290073 -0400
+++ python-qt4-4.9.2/configure.py 2012-06-21
PyQt 4.9.1 builds fine with all the Pythons we currently have in Debian
Unstable (2.6/2.7/3.2). PyQt 4.9.2 does fine building with 2.6/2.7, but fails
with Python3.2. I've attached the excerpt of the build log relevant to the
3.2 build. I'd appreciate advice on how to troubleshoot this.
As I've mentioned previously, I'm gradually looking at old PyQt bugs in Debian
and Ubuntu and reviewing them.
Looking at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523149 it seems to
be a user misunderstanding the API. It seems this might have been due to
unclear documentation, so I
Phil Thompson p...@riverbankcomputing.com wrote:
On Fri, 13 Apr 2012 11:52:31 -0300, Alejandro J. Cura
al...@canonical.com wrote:
Hi,
first of all, since I'm new to the list I'd like to thank the people
responsible for PyQt a lot for making such a great project.
I'd like to report a
On Saturday, April 14, 2012 06:16:00 PM Phil Thompson wrote:
On Sat, 14 Apr 2012 13:07:58 -0400, Scott Kitterman deb...@kitterman.com
wrote:
Phil Thompson p...@riverbankcomputing.com wrote:
On Fri, 13 Apr 2012 11:52:31 -0300, Alejandro J. Cura
al...@canonical.com wrote:
Hi,
first
Forwarding this suggestion from a Debian user.
Scott K
-- Forwarded Message --
Subject: Bug#667910: python-qt4: Raises underlying C/C++ object has been
deleted while it has not been created
Date: Saturday, April 07, 2012, 03:15:19 PM
From: Valentin Lorentz prog...@progval.net
This is a user reported bug. I get the same segmentation fault. I tried the
sample program with 4.8.5 and 4.9.1 (both python and python3) on Debian and
Ubuntu with the same results.
Scott K
-- Forwarded Message --
Subject: Bug#661854: python-qt4: segfault calling family()
We've run into an issue in Ubuntu where we had Sip4 4.13.1and PyQt 4.9 built
against Qt 4.7.4. PyKDE4 4.8.0 was built using this set of packages. All was
working well.
We rebuilt PyQt 4.9 against Qt 4.8.0 due to some packaging updates and had
problems. The primary Ubuntu bug is:
Luca Beltrame ei...@heavensinferno.net wrote:
In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
but leaves open the question of what caused the incompatiblity and
what
other packages might be affected.
As far as I can see, SIP makes no ABI guarantees between versions, so
Andreas Pakulat ap...@gmx.de wrote:
On 28.01.12 13:01:28, Scott Kitterman wrote:
Luca Beltrame ei...@heavensinferno.net wrote:
In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto:
but leaves open the question of what caused the incompatiblity and
what
other
On Sunday, January 29, 2012 05:00:44 AM Arfrever Frehtes Taifersar Arahesis
wrote:
2012-01-27 11:42:04 Phil Thompson napisał(a):
Try tonight's PyQt snapshot - completely untested.
dbus.cpp: In function ‘dbus_bool_t add_watch(DBusWatch*, void*)’:
dbus.cpp:39:14: warning: ‘int
42 matches
Mail list logo
