On Wed, May 10, 2006 at 09:46:58PM -0400, bulia byak wrote:
As someone suggested, my problem of effects not working on Windows was indeed due to another Python installed in the PATH. After I removed that, it picked up Inkscape's own python and all worked fine.
Therefore, I suggest that we do three things:
- Designate this as a mustfix bug for the release: Inkscape must
always use its own python, not something in PATH. Certainly I'm not the only one with Python installed on Windows, so this issue is bound to happen to other people.
Sounds good. Who would be the owner for this? Do you have an idea of what other mustfix bugs there are?
- Enable extensions/effects by default and remove the prefs setting.
I don't know of anything that prevents us from doing that.
This probably should have been done earlier, to give additional time for testing, but you're right that now's the time to turn it on by default.
- Release a 0.44pre0.
Let's hold off on pre-releases until we've achieved feature freeze (planned for the 15th).
Bryce