build-system | fork from aosp , branch gradle_3.4.0 | Plugin library

I am trying to use build-pyarmored-wheel to build a company project, I am following steps as described in 

https://pyarmor.readthedocs.io/en/latest/build-wheel.html?highlight=pyproject.toml#build-pyarmored-wheel

content of pyproject.toml

I am attempting to convert a working Makefile into a CMake and need a little assistance. I am trying to cross compile a small program for a yocto device from a Ubuntu20 machine that is trying to link to the devices shared object file with cmake. I have a working Makefile that builds a working program. However, when I try and do this with a CMakeList file it fails at the make stage linking to the shared objects linker flag.

The file structure of the code is as follows;

When a project is specified only via pyproject.toml (i.e. no setup.{py,cfg} files), how can it be installed in editable mode via pip (i.e. python -m pip install -e .)?

I tried both setuptools and poetry for the build system, but neither worked:

What is the correct format for supplying a name to a python package in a pyproject.toml?

pyproject.toml file

I am looking at https://github.com/pypa/setuptools_scm

and I read this part https://github.com/pypa/setuptools_scm#version-number-construction

and i quote

Semantic versioning for projects with release branches. The same as guess-next-dev (incrementing the pre-release or micro segment) if on a release branch: a branch whose name (ignoring namespace) parses as a version that matches the most recent tag up to the minor segment. Otherwise if on a non-release branch, increments the minor segment and sets the micro segment to zero, then appends .devN.

How does this work?

Assuming my setup is at this commit https://github.com/simkimsia/test-setup-py/commit/5ebab14b16b63090ad0554ad8f9a77a28b047323

and the same repo, how do i increment the version by branching?

I updated some files on main branch.

Then i did the following

I'm trying to build a Python Plugin for Saleor using Poetry and I'm having issues installing the plugin on Saleor. I run poetry add ../social_auth to install the plugin on saleor and it succeeds but when I try to run Saleor I get this Error:

I am running into an error when trying to run my container where it is saying it can't find a module while trying to import. Specifically:

ModuleNotFoundError: No module named 'sentry_sdk'

The following is my DockerFile which is a multistage build, it seems to install all the packages according to the console output.

After a system upgrade (Arch linux) I couldn't compile my project anymore. One of the problems was that there isn't a -pthread flag passed to the compiler anymore.

I managed to write a minimal test case:

The CMakeLists.txt file contains:

Does it make sense to use Conda + Poetry for a Machine Learning project? Allow me to share my (novice) understanding and please correct or enlighten me:

As far as I understand, Conda and Poetry have different purposes but are largely redundant:

• Conda is primarily a environment manager (in fact not necessarily Python), but it can also manage packages and dependencies.
• Poetry is primarily a Python package manager (say, an upgrade of pip), but it can also create and manage Python environments (say, an upgrade of Pyenv).

My idea is to use both and compartmentalize their roles: let Conda be the environment manager and Poetry the package manager. My reasoning is that (it sounds like) Conda is best for managing environments and can be used for compiling and installing non-python packages, especially CUDA drivers (for GPU capability), while Poetry is more powerful than Conda as a Python package manager.

I've managed to make this work fairly easily by using Poetry within a Conda environment. The trick is to not use Poetry to manage the Python environment: I'm not using commands like poetry shell or poetry run, only poetry init, poetry install etc (after activating the Conda environment).

For full disclosure, my environment.yml file (for Conda) looks like this: