-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AUTOSAR 4.4.0 ? #31
Comments
Hi @renukavinay, I'm fully engaged working on my C-based repositories and will not have time to do any major work on the autosar repo in the next 3-6 months. |
I am new to autosar and found your python package online and wanted to
check for latest release. Thanks for your response, I really appreciate it.
Regards,
Renuka
…On Sat, Jan 5, 2019, 2:21 AM Conny Gustafsson ***@***.*** wrote:
Hi @renukavinay <https://github.com/renukavinay>,
I'm fully engaged working on my C-based repositories and will not have
time to do any major work on the autosar repo in the next 3-6 months.
I do plan to resume working on the autosar repo at some point in the
future and will at that time look into supporting AUTOSAR 4.3 and 4.4 XML.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AQxCswn2H2dI9Y8GocJpqsrL55SYlcnpks5vAHyegaJpZM4Zr2mr>
.
|
hey, I am new to autosar and i saw your python autosar package and i want to use can you tell me how to install this autosar module in python? many thanks in advance. |
This Python module does not yet support AUTOSAR 4.3 or 4.4. |
Hi @cogu, I would like to contribute to your library to bring support for AUTOSAR 4.3 standard, at least. |
@miketsukerman, Thank you for your support.
Starting from AUTOSAR 4.3.1 they are only using the revision number of the release in the XML root element
You can read more about this in chapter 2.2.4 XML Root Element of the AUTOSAR specification AUTOSAR_TPS_ARXMLSerializationRules.pdf Traditionally, a workspace is created by giving the version argument to the workspace method. ws = autosar.workspace(version="4.2.2") That API should continue to work but In addition we need to be able to create workspaces based on release number instead of version. ws1 = autosar.workspace(release=44) #AUTOSAR 4.3.1
ws2 = autosar.workspace(release=46) #AUTOSAR 4.4.0 What I would like to see first is a set of Python unit tests that can demonstrate that the Python module is capable of serializing an (empty) AUTOSAR 4.3.1 workspace into ARXML and then reads it back again using the parser submodule. Sort of like this: def test_write_and_read_empty_autosar_431_file(self):
ws1 = autosar.workspace(release=44)
file_name = 'ar431_empty_workspace.arxml'
generated_file = os.path.join(self.output_dir, file_name)
expected_file = os.path.join( 'expected_gen', 'base', file_name)
self.save_and_check(ws, expected_file, generated_file)
ws2 = autosar.workspace()
ws2.loadXML(os.path.join(os.path.dirname(__file__), expected_file))
self.assertEqual(ws2.release, 44) I also think that release and version should be mutually exclusive in the Workspace object such that: ws1 = autosar.workspace(version="4.2.2")
assert(ws1.release is None)
ws2 = autosar.workspace(release=44)
assert(ws2.version is None) For the above to work, the current implementation needs to change. I do believe that current implementation sets ws.version to Please let me know what you think. |
Hello, Can you please give an estimation? We might support you but if there are no plans we must create an own solution. |
@BR1py, |
|
Hello @cogu
I am new to the AUTOSAR world and was wondering do you have any plans to support AUTOSAR 4.4.0 version? Many thanks in advance.
The text was updated successfully, but these errors were encountered: