On Thu, Jan 15, 2009 at 09:05:24PM +0100, Dirk Meyer wrote:
> we are wondering if we can make Python 2.5 a requirement for Freevo 1.8?
> It would make things a lot easier in kaa.base (signal handler) and
> kaa.metadata (relative imports). So how many users still use Python 2.4
> and why?
My freevo
On Thu, 2009-01-15 at 21:56 +0100, Torsten Kurbad wrote:
> Anyway, Gentoo makes it relatively easy to have several Python versions
> installed at the same time. Thus, no objection in general.
I think it's the case that most distros allow multiple python versions
to coexist fairly easily.
---
Hi Dischi,
> So how many users still use Python 2.4 and why?
I for my part still prefer Python 2.4, since I'm involved in some
projects that are based on Zope3 releases, which don't run on Python
2.5.
Anyway, Gentoo makes it relatively easy to have several Python versions
installed at the same t
Adam Charrett a écrit :
> On Wed, 2009-01-14 at 15:42 -0500, Jason Tackaberry wrote:
>
>> Is there anything in your code that optionally uses kaa.display if it's
>> available?
>
> Yes, the new dialog module uses kaa.display if available to display
> dialogs/OSDs over video.
>
Could that be a
Hi,
we are wondering if we can make Python 2.5 a requirement for Freevo 1.8?
It would make things a lot easier in kaa.base (signal handler) and
kaa.metadata (relative imports). So how many users still use Python 2.4
and why?
Dischi
--
It's not Area 51 I'm worried about- it's Areas 1 through 50
Jason Tackaberry wrote:
> Hi all,
>
> I have just committed a change that moves kaa/base/src/notifier/* up a
> level to kaa/base/src, effectively removing the kaa.notifier submodule.
>
> If you are using any code that references kaa.notifier explicitly, it
> will now break. (Note that this has b
Jason Tackaberry wrote:
> On Wed, 2009-01-14 at 21:50 +, Adam Charrett wrote:
>> Yes, the new dialog module uses kaa.display if available to display
>> dialogs/OSDs over video.
>
> Ok. It's not clear to me where things could be going wrong.
>
> Duncan, was SystemExit raised in the main proce
On Thu, 2009-01-15 at 11:37 -0500, Jason Tackaberry wrote:
> If you are using any code that references kaa.notifier explicitly, it
> will now break. (Note that this has been deprecated for a long time.)
I wanted to add: we'll be experiencing a bit more pain as we make
several more API changes: ma
Hi all,
I have just committed a change that moves kaa/base/src/notifier/* up a
level to kaa/base/src, effectively removing the kaa.notifier submodule.
If you are using any code that references kaa.notifier explicitly, it
will now break. (Note that this has been deprecated for a long time.)
More
