is. Now I get it, it makes perfect sense.
Looks like I'll have to stick to the usual mechanisms!
Thanks everyone!
---
João Neves
--
http://mail.python.org/mailman/listinfo/python-list
On 2 Abr, 21:38, "Chris Mellon" <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 2:33 PM, João Neves <[EMAIL PROTECTED]> wrote:
> > On Apr 2, 5:41 pm, "Dan Upton" <[EMAIL PROTECTED]> wrote:
> > > > The thing I've been wondering
On Apr 2, 5:41 pm, "Dan Upton" <[EMAIL PROTECTED]> wrote:
> > The thing I've been wondering is why _is_ it read-only? In what
> > circumstances having write access to co_code would break the language
> > or do some other nasty stuff?
>
>
of this moment, I get a TypeError exception, because
co_code is read-only.
The thing I've been wondering is why _is_ it read-only? In what
circumstances having write access to co_code would break the language
or do some other nasty stuff?
João Neves
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 2, 3:06 pm, Thomas Guettler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I looked for a solution to talk to a web service which
> offers its signature with a wsdl file.
>
> I googled for 'wsdl python' and found ZSI.
>
> This project uses code generation. That's something
> I don't like.
>
> The book
ange a function at runtime, he could do so
at his own risk.
If there is a higher reason behind the read-only property of co_code,
I definitely fail to see it, and would like to know what it is. If
not, why aren't we allowed to write into it?
Thanks in advance,
João Neves
--
http://mail.python.org/mailman/listinfo/python-list
