feat: add example using rich and pixi-build-python and remove flask
#2638
Conversation
The other examples where not actually building a Python package with `pixi-build-python`
|
Wouldnt it make more sense to adapt the |
Yeah, probably. Let me have a look! |
|
@baszalmstra I think having both would be good, because the flask example is more or less building kind of a script workspace in a way or what uv calls an |
Hofer-Julian
changed the title
rich and pixi-build-pythonrich and pixi-build-python and remove flask
|
As discussed with @baszalmstra and @tdejager, I removed the broken flask examples |
|
looks cleaner and easier to understand. I've also tested |
|
blocked on windows by missing entry points https://github.com/prefix-dev/rattler-build/blob/cff5ca53751d348a469bfbf9577e970d6797bdc5/docs/tutorials/python.md?plain=1#L101-L105. |
## Description This adds proper unit testing, for PyPI installations and adds a test harness to test these things. This is a much more efficient and smaller way of testing the functionality, specifically the need to install/re-install then doing full integration tests. ## Checklist - [x] Tests for direct url archives - [x] Test for vcs installs. - [x] See if we need to remove integration tests, because some of it is tested here. --------- Co-authored-by: Bas Zalmstra <bas@prefix.dev>
- move test data to common directory - move helper functions to fixtures
I need to expose these public methods so I could access manifest table from pixi-build-backend. necessary for this PR: https://github.com/prefix-dev/pixi-build-backends/compare/main...nichmor:pixi-build-backends:fix/add-entry-points-in-recipe?expand=1
The other examples where not actually building a Python package with
pixi-build-python