@/all 0.12.7 has been released with recent important fixes. Please see the release notes: https://pybuilder.io/release-notes/v0.12.x#version-0127
looks like PIP install for packaged pip now works much faster too for venv generation
but I no longer use it work work
@/all FYI new feature disabling VEnv management in PyBuilder: https://pybuilder.io/articles/news/no-virtualenv-option
/exit
good luck!
Hi all, I have a python package that relies on ad-hoc machine-learning models. I would like to have these models built while packaging so that the models stay up-to-date with the code at each release. How can I achieve this through pybuilder ? I created a task that "imports mypackage" but mypackage (which is being built) is not available at build-time. Any hint ?
1 task generates files
1 task imports those files
there are more intricate details there of course
you train the model in one task, which you can put prior to packaging
now your generated packaging will be available in integration tests phase
so @mazancourt_twitter if you create "integration tests" and train your model there, this will work
if you want to train your model prior to packaging proper
the package is not yet created but the sources are available to you at that phase
you can generate the files in the compile phase
one sec, I'll give you an example
This is for PyBuilder itself
$ pyb -T
Tasks that will be executed for project "pybuilder":
prepare - Prepares the project for building. Creates target VEnvs
compile_sources - Compiles source files that need compilation.
depends on tasks: prepare
run_unit_tests - Runs all unit tests. Runs unit tests based on Python's unittest module
depends on tasks: compile_sources
analyze - Execute analysis plugins.
depends on tasks: run_unit_tests prepare
package - Packages the application. Package a python application.
depends on tasks: compile_sources run_unit_tests(optional)
run_integration_tests - Runs integration tests on the packaged application. Runs integration tests based on Python's unittest module
depends on tasks: package
verify - Verifies the project and possibly integration tests.
depends on tasks: run_integration_tests(optional)
coverage - <no description available>
depends on tasks: verify
compile_docs - Generates HTML documentation tree with pdoc
depends on tasks: compile_sources verify
publish - Publishes the project.
depends on tasks: package verify(optional) coverage(optional) compile_docs(optional)
you can create a task that depends on compile_sources and makes run_unit_tests a dependent