[PyKDE] PyKDE Change in Plans
Following up on Phil's "Incompatible SIP Change" message, I've decided to make a slight change in the PyKDE release schedule. Within the next couple of days, I'll release a snapshot of the next PyKDE release. This snapshot will be based on sip 3.5. If you're using sip 3.5 it will build as delivered. To use it with the "incompatible" sip snapshot you'll need to do the following before building: 1. grep the sip files for "sipName": grep sipName .../sip/*.sip There are only 7 occurances 2. Replace all occurances of "sipName_module_something" with "sipName_something". For example sipBadVirtualResultType(sipName_kdeui_KDateValidator, sipName_kdeui_validate); becomes: sipBadVirtualResultType(sipName_KDateValidator, sipName_validate); 3. Build as usual This seems much easier than having two different snapshot versions of PyKDE. For packagers: rather than send out tarballs, you can (if you want to) package the snapshot release - your call. There are two reasons for the delay in the "official release": 1. sip 3.6 isn't that far away, but will have the "incompatibility" noted above and some other fixes that require minor code changes. 2. I'd really like to spend more time on the final release version (I expect some bugs and want to add more features - better docs, more demos, program templates, and some other stuff), but I don't want to delay getting at least something usable out there, so this seems like a good compromise. I don't know of any major bugs, but that may only be because I haven't tested for them. The majority of stuff actually used in PyKDE works very well (I've been playing with it for a while now), but some of the more esoteric stuff needs some testing. Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE Change in Plans
On Tuesday 01 April 2003 13:23, Jim Bublitz wrote:
> Following up on Phil's "Incompatible SIP Change" message, I've
> decided to make a slight change in the PyKDE release schedule.
>
> Within the next couple of days, I'll release a snapshot of the next
> PyKDE release. This snapshot will be based on sip 3.5. If you're
> using sip 3.5 it will build as delivered.
>
> To use it with the "incompatible" sip snapshot you'll need to do the
> following before building:
>
> 1. grep the sip files for "sipName":
>
> grep sipName .../sip/*.sip
three dots?
>
> There are only 7 occurances
>
> 2. Replace all occurances of "sipName_module_something" with
> "sipName_something". For example
>
> sipBadVirtualResultType(sipName_kdeui_KDateValidator,
> sipName_kdeui_validate);
>
> becomes:
>
> sipBadVirtualResultType(sipName_KDateValidator, sipName_validate);
Hmm if you have the appropriate commands installed:
grep -l "sipName" ../sip/*.sip | xargs -n 1 -i sed -r -i
"s/(sipName_)([a-zA-Z]+_)/\1/g" {}
Which will do it in one commandline (but with only seven occurences it might
be overkill - however, I've used that to replace defines, code, etc. many
times).
The basic command is:
sed -r -i "s/(sipName_)([a-zA-Z]+_)/\1/g"
which will take:
[EMAIL PROTECTED] kibab $ cat mytestfile
sipName_kdeui_KatePart sipName_kdeui_Mytest
and turn it into:
sipName_KatePart sipName_Mytest
This, of course, assumes that no underscore will be present in module names.
Finally, if I'm wrong and this kills your system, well, oops ;)
--Kaleb
pgp0.pgp
Description: signature
Re: [PyKDE] PyKDE Change in Plans
On 01-Apr-03 Kaleb Pederson wrote:
> On Tuesday 01 April 2003 13:23, Jim Bublitz wrote:
>> Following up on Phil's "Incompatible SIP Change" message, I've
>> decided to make a slight change in the PyKDE release schedule.
>> Within the next couple of days, I'll release a snapshot of the
>> next PyKDE release. This snapshot will be based on sip 3.5. If
>> you're using sip 3.5 it will build as delivered.
>> To use it with the "incompatible" sip snapshot you'll need to do
>> the following before building:
>> 1. grep the sip files for "sipName":
>> grep sipName .../sip/*.sip
> three dots?
As in "something else probably goes there depending on where you
put PyKDE and what the current working directory is and what the
top level PyKDE directory is".
>> There are only 7 occurances
>> 2. Replace all occurances of "sipName_module_something" with
>> "sipName_something". For example
>> sipBadVirtualResultType(sipName_kdeui_KDateValidator,
>> sipName_kdeui_validate);
>> becomes:
>> sipBadVirtualResultType(sipName_KDateValidator,
>> sipName_validate);
> Hmm if you have the appropriate commands installed:
> grep -l "sipName" ../sip/*.sip | xargs -n 1 -i sed -r -i
> "s/(sipName_)([a-zA-Z]+_)/\1/g" {}
> Which will do it in one commandline (but with only seven
> occurences it might be overkill - however, I've used that to
> replace defines, code,etc. many times).
> The basic command is:
> sed -r -i "s/(sipName_)([a-zA-Z]+_)/\1/g"
> which will take:
> [EMAIL PROTECTED] kibab $ cat mytestfile
> sipName_kdeui_KatePart sipName_kdeui_Mytest
>
> and turn it into:
> sipName_KatePart sipName_Mytest
> This, of course, assumes that no underscore will be present in
> module names.
Correct.
> Finally, if I'm wrong and this kills your system, well, oops ;)
I always keep the original tarball as a backup because I don't
these very well.
Jim
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE Change in Plans
Hmm..., I was wondering if it is possible to introduce a feature %feature SIP_FOOLS_DAY where build.py (or my distutils scripts) have to figure out if sip predates 2003-04-01 or not. Gerard On Tue, 01 Apr 2003 13:23:15 -0800 (PST) Jim Bublitz <[EMAIL PROTECTED]> wrote: > Following up on Phil's "Incompatible SIP Change" message, I've > decided to make a slight change in the PyKDE release schedule. > > Within the next couple of days, I'll release a snapshot of the next > PyKDE release. This snapshot will be based on sip 3.5. If you're > using sip 3.5 it will build as delivered. > > To use it with the "incompatible" sip snapshot you'll need to do the > following before building: > > 1. grep the sip files for "sipName": > > grep sipName .../sip/*.sip > > There are only 7 occurances > > 2. Replace all occurances of "sipName_module_something" with > "sipName_something". For example > > sipBadVirtualResultType(sipName_kdeui_KDateValidator, > sipName_kdeui_validate); > > becomes: > > sipBadVirtualResultType(sipName_KDateValidator, sipName_validate); > > 3. Build as usual > > This seems much easier than having two different snapshot versions > of PyKDE. > > For packagers: rather than send out tarballs, you can (if you want > to) package the snapshot release - your call. > > There are two reasons for the delay in the "official release": > > 1. sip 3.6 isn't that far away, but will have the "incompatibility" > noted above and some other fixes that require minor code changes. > > 2. I'd really like to spend more time on the final release version > (I expect some bugs and want to add more features - better docs, > more demos, program templates, and some other stuff), but I don't > want to delay getting at least something usable out there, so this > seems like a good compromise. I don't know of any major bugs, but > that may only be because I haven't tested for them. The majority of > stuff actually used in PyKDE works very well (I've been playing > with it for a while now), but some of the more esoteric stuff needs > some testing. > > Jim > > > ___ > PyKDE mailing list[EMAIL PROTECTED] > http://mats.gmd.de/mailman/listinfo/pykde > -- Gerard Vermeulen Tel: 33(0)476881253 Fax: 33(0)476875060 ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE Change in Plans
On 02-Apr-03 Gerard Vermeulen wrote: > Hmm..., > I was wondering if it is possible to introduce a feature > %feature SIP_FOOLS_DAY > where build.py (or my distutils scripts) have to figure > out if sip predates 2003-04-01 or not. Sure - Take the output of sip -V and test it to determine if you need the old style or new style naming, then pass a -D define to your code when compiling or set a feature conditional (<= 3.5 or < snapshot-20030401 for old style). There is a #define Phil referenced (SIP_MAJOR_NR) that you can test in C++ code (it's in the 3/15 snapshot), but I think you'll only be able to distinguish 3 from 4, and the incompatibility will be in later versions of 3 already. It's in siplib/sip.h. I'm resistant to doing it for PyKDE because it adds some other complications and it appears at the moment that PyKDE for 3.6 (when 3.6 is released) won't be backwards compatible with PyKDE for 3.5. It's easy to add the #ifdefs if you need them (all the changes are in C++ code in %VirtualCode blocks). PyQt shouldn't have a problem as long as you match the PyQt and sip versions. I like the feature name though :) Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
