> Unfortunately, I observed during a few runs on my test system
> that the displayed record sets can vary. Thus I guess that this approach
> (which works together with Python multi-threading functionality) will need
> further software adjustments.
I stumbled on general software development
> connecting
…
> File "", line 35, in store_statements
> socket.gaierror: [Errno -2] Name or service not known
> Error in Python script, line 56, file …
It seems that the attached adjusted data processing approach can produce
an usable analysis result.
> File "", line 35, in store_statements
> socket.gaierror: [Errno -2] Name or service not known
> Error in Python script, line 56, file …
It seems that the attached adjusted data processing approach can produce
an usable analysis result.
elfring@Sonne:~/Projekte/Coccinelle/janitor> time
>> File "", line 34, in store_statements
>> AttributeError: __exit__
>> Error in Python script, line 55, file …
>
> I have no idea. It looks like a python problem.
Partly, yes (of course).
> If you want help, you will have to construct a script
> that exhibits the error with print statements
> Is there still a need to perform parallelisation for the mentioned software
> components by other approaches?
The multi-processing support by the Coccinelle software triggers some
development challenges.
If data should be shared between started (background) processes,
an external system need to
