[BUG] Build is not working about security_content HOT 6 CLOSED

it is definetly a more active project since we publish our active detection development there, but the tooling for it now lives on contentctl.

from security_content.

as i may understand, this is due to python 3.10.
and it is strange, why venv using 3.10, or what is wrong?

(venv) user@star:~/security_content-4.21.0$ which python
/home/user/security_content-4.21.0/venv/bin/python
(venv) user@star:~/security_content-4.21.0$ python --version
Python 3.10.12
(venv) user@star:~/security_content-4.21.0$ /home/user/security_content-4.21.0/venv/bin/python --version
Python 3.10.12

from security_content.

so, i had to update some ~20 py files with Import from collections and changed it to Import from collections.abc and it started to work.

but this is not expected way to solve it.

from security_content.

Hey @yaroslav-nakonechnikov I believe you might be using an old version of our tooling, we migrated all these tools over to https://github.com/splunk/contentctl .. give those a try, I will work on updating our README here so it won't mislead other users. Thank you for raising!

from security_content.

@josehelps but according to releases and timestamps for it - there is a feel, that security_content is more active project.

from security_content.

thanks!

from security_content.