* Add basic pypi upload CI action.
For now I propose a simple trigger using a commit tag "[bcf release]". I think this is just as well since we do not (yet) have an automatic versioning for the bcf package
* add correct subfolder (point to bcf) to ci recipe
* Refactored the BCF dir into a "src-layout" which I am more comfortable with. We can likely change this back if it is not compatible with other development
* I added a few setup files for the bcf package (setup.cfg, pyproject.toml and a MANIFEST.in file)
* Added two __init__.py files in the v2 and v3 subfolders for them to be picked up during package compilation
Not much, but still small improvement:
6 upgraded, 138 newly installed, 0 to remove and 43 not upgraded.
6 upgraded, 135 newly installed, 0 to remove and 43 not upgraded.
* Initial commit for suggested blenderbim github actions setup
* Changed the github repo address from fork to main repo for clarity
* Include python version info to appear on asset name. Consider using additional matrix loop on python versions 37 and 39. Currently hardcoded py37 for testing
* Cleanup of "python_fcl" files in dist/working before compiling BIMTester
* Loop over python 3.7 and 3.9 for all platforms and build 6 releases
* Set the correct repository name in the trigger. Also make the trigger only run when "[release]" is added in the commit message.
Dion Moult