octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #65057] Byte-code interpreter is not compatibl


From: Hendrik K
Subject: [Octave-bug-tracker] [bug #65057] Byte-code interpreter is not compatible with the pythonic package
Date: Tue, 19 Dec 2023 21:35:10 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?65057>

                 Summary: Byte-code interpreter is not compatible with the
pythonic package
                   Group: GNU Octave
               Submitter: koerhen
               Submitted: Wed 20 Dec 2023 02:35:07 AM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 20 Dec 2023 02:35:07 AM UTC By: Hendrik K <koerhen>
The byte-code interpreter is not compatible with the octave-pythonic package:


pkg install
https://gitlab.com/gnu-octave/octave-pythonic/-/archive/master/octave-pythonic-master.tar.gz

function ret = test2();
  pkg load pythonic;
  py.sys.path.insert (int32 (0), pwd());
  disp("Test2 execution finished.");
endfunction



When now executing test2() with the vm_active, a warning is thrown and test2
is not compiled (but executed though).


__vm_enable__(1);
test2();

warning: auto-compilation of pyobject failed with message classdef
constructors are not supported by the VM yet
warning: called from
    subsref at line 53 column 7
    test2 at line 3 column 3

Test2 execution finished.



Side note: The byte-code interpreter warning(s) should follow the octave
warning naming convention
(https://docs.octave.org/v8.4.0/Issuing-Warnings.html): 

"Note that warning IDs are in the format "NAMESPACE:WARNING-NAME". The
namespace "Octave" is used for Octave’s own warnings"








    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65057>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]