buggnubg - Bugs: bug #54320, How to explicitly import gnubg...


bug #54320: How to explicitly import gnubg modules?

Submitter:  Tom Martin <tom_martin>
Submitted:  Mon 16 Jul 2018 09:03:27 PM UTC
Originator Name:  Tom Martin Item Group:  * Other bug
Category:  * Command line interface Release:  * 1.04-Release
Privacy:  Public Operating System:  * All
Severity:  3 - Normal Open/Closed:  Open
Assigned to:  None Priority:  5 - Normal
Status:  None
* Mandatory Fields

Add a New Comment Rich Markup

Fri 20 Jul 2018 03:22:41 PM UTC, comment #1: 

The solution is to simply add "import gnubg" to any module you plan to import.  It seems this must refer to scripts/gnubg.py but I can't find anything inside of that file that refers to the gnubg functions such as navigate and command.  But it works so I must be overlooking something.

Tom Martin <tom_martin>
Mon 16 Jul 2018 09:03:27 PM UTC, original submission:  

After importing a module via the command line, its functions are unable to call any gnubg function, presumably because they aren't in the namespace of the imported code.

I assume all I need to do is add the appropriate "import" statement but I can't find a way to do so.  The gnubg.py code has several imports but none of them seem to refer to navigate, command, etc.

Tom Martin <tom_martin>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by tom_martin (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-04b1.
    Corresponding source code