Re: Using Inline Python to import Python vars
[email protected] (Chris Nighswonger) Mon, 8 Apr 2013 16:25:33 -0400
| Newsgroups | perl.inline |
|---|---|
| Message-ID | <CAP3yOokqcgOMNS7KJ7-oekrnHNxa+3xP1O=5JPxRK+p=dn5cNw@mail.gmail.com> |
On Mon, Apr 8, 2013 at 3:14 PM, Stefan Seifert <[email protected]> wrote: > Hi Chris, > Using perl Makefile.PL -debug when building Inline::Python gives a good > hint. > With this flag it will print loads of information including Python source > code > it compiles to stderr. > > Thanks for that valuable piece of information. I was wondering how to get the XS foo to spit out the Printf's. > I've never used DATA file handles in Perl much less with Inline::Python, so > I'm not exactly sure. But the debug output looks like the Python source > code > ends at __version__. So I guess, the code reading the DATA file processes > everything from __Python__ to the next marker and treats every word > enclosed > in double underscores as such marker. > I really should have thought to look at the compiled module. Here is what it is: namespace : % classes : % functions : @ pykota_version filtered : <<EOV- def pykota_version(): import pykota.version return EOV Clearly the problem is exactly as you point out. I'll see if I can fix it. Kind Regards, Chris