On 2010-06-15 02:29, moerchendiser2k3 wrote:
> Hi, yes, that was my first idea when I just create an
> external module. I forgot something to say:
>
> In my case the initfoo() function is called on startup
> in my embedding environment, that means I call that
> on startup of my main app.
>
ah. I
Hi, yes, that was my first idea when I just create an
external module. I forgot something to say:
In my case the initfoo() function is called on startup
in my embedding environment, that means I call that
on startup of my main app.
Bye,
moerchendiser2k3
--
http://mail.python.org/mailman/listinfo
On 06/14/2010 02:30 AM, moerchendiser2k3 wrote:
> PyErr_WarnEx(PyExc_DeprecationWarning, "foo deprecated. use fuzz",
> 1);
>
> But where can I write this? With Py_InitModule4 I can just
> pass a list of functions but no real execution part which
> is executed when a module is imported.
This is Py
PyErr_WarnEx(PyExc_DeprecationWarning, "foo deprecated. use fuzz",
1);
But where can I write this? With Py_InitModule4 I can just
pass a list of functions but no real execution part which
is executed when a module is imported.
--
http://mail.python.org/mailman/listinfo/python-list
On 06/13/2010 03:54 PM, moerchendiser2k3 wrote:
> Hi,
>
> can anyone give me a hint how to mark a built-in module as deprecated?
> So mark via warnings... I create a module with Py_InitModule4.
How are modules ever marked as deprecated? I think all there is to it is
issuing a DeprecationWarning..
Hi,
can anyone give me a hint how to mark a built-in module as deprecated?
So mark via warnings... I create a module with Py_InitModule4.
Thanks in advance!!
Bye, moerchendiser2k3
--
http://mail.python.org/mailman/listinfo/python-list
