#202 python bytecode mystery ...

closed-works-for-me
python (259)
5
2003-02-19
2002-08-21
Anonymous
No

I'm using Python 2.1 and SWIG 1.3.14.

I used SWIG on a pretty big project and it worked out
fine. I can use all methods of the C++-classes I want.

But after I imported the wrapper-module and it got
compilated into bytecode, and I use it a second time,
so that the bytecode is used, I get wrong
variable-values ( strange values - looks like they're
not initialised, but they are !) for the variables in
the C++-classes. It's nothing wrong with the mechansim
of getting the variables into python, 'cause I print'em
out in the C++ methods.

When deleting the wrapper-bytecode before using the
wrapper (and force it to use the real code) everything
works fine again.

Something wrong with the bytecode ?

Discussion

  • David M. Beazley

    Logged In: YES
    user_id=7557

    Need a more specific example to know what might be wrong.

     
  • David M. Beazley

    • labels: --> python
    • assigned_to: nobody --> beazley
     
  • David M. Beazley

    • status: open --> closed-works-for-me
     
  • David M. Beazley

    Logged In: YES
    user_id=7557

    No ideas. No followup so I'm closing.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks