Issue1185

Title Make translator a python package
Priority feature Status resolved
Superseder Nosy List gabi, silvan
Assigned To Keywords translator
Optional summary

Created on 2025-07-14.13:08:06 by gabi, last changed by gabi.

Messages
msg11885 (view) Author: gabi Date: 2025-08-05.14:57:27
We merged the change.

As part of this change, we renamed the earlier module translate.py to main.py.

We also changed the way how (command line) options are handled. These were previously parsed when `options` was (first) imported. Now this parsing must explicitly be initiated by means of options.set_options(). If the package is used within other code, the options can be set by passing them to this method as a list.
msg11877 (view) Author: gabi Date: 2025-07-29.11:55:31
I created a pull request here: https://github.com/aibasel/downward/pull/271
msg11852 (view) Author: gabi Date: 2025-07-14.13:08:06
There is an open issue [1] in the unified-planning library integration of Fast Downward, related to a naming conflict for a 'pddl' module. The integration uses the one stemming from Fast Downward but the core unified planning library now wants to use one of the same name from AI-Planning [2].

I would like to make the translator a proper python package, so that I can reference the pddl part as a submodule (so that names no longer conflict).


[1] https://github.com/aiplan4eu/up-fast-downward/issues/36
[2] https://github.com/AI-Planning/pddl
History
Date User Action Args
2025-08-05 14:57:27gabisetstatus: chatting -> resolved
messages: + msg11885
2025-07-29 11:55:31gabisetstatus: unread -> chatting
messages: + msg11877
2025-07-14 16:21:05silvansetnosy: + silvan
2025-07-14 13:08:06gabicreate