Fun fact. Posting so far is just swallowing messages over and over
again. There is no way to check if the message has been posted yet -
please expect changes when implementing the reading feature.
Resigned from the explicit feature test for exiting the application -
had some problems driving it properly from behave and wanted to move
on. The test now exists in the unit test space.
Speaking of unit tests - there are some now - Travis and AppVeyor runs
include them as well.
Settled on Python3, as it has better support for timeouts during
communication with subprocesses.
Standardized on x86 for all projects - no need for > 2/4 GB memory and
avoiding all multiplatform/processor issues here.
Fun fact. Posting so far is just swallowing messages over and over again. There is no way to check if the message has been posted yet - please expect changes when implementing the
readingfeature.Resigned from the explicit feature test for exiting the application - had some problems driving it properly from
behaveand wanted to move on. The test now exists in the unit test space.Speaking of unit tests - there are some now - Travis and AppVeyor runs include them as well.
Settled on Python3, as it has better support for timeouts during communication with subprocesses.
Standardized on x86 for all projects - no need for > 2/4 GB memory and avoiding all multiplatform/processor issues here.