Python Package Built in Oryx Pointing to Wrong Python Installation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 881
- Forks
- 195
- Avg merge
- 20h 13m
- Merged PRs (30d)
- 13
Description
Hello,
I have been trying to understand this issue.
I am currently running a Azure Python Function App (On a Dedicated Plan). During the build process for the function app, I pip install a package which runs a build itself. The issue here, is that once the build process is run for the package, the package thinks that the Python interpreter location is at /tmp/oryx/platforms/python/3.10.4, rather than the user python location, when run.
Ie.
Source directory :/ tmp/....
Destination directory: /tmp/build/expressbuild
Python Version: **/tmp/oryx/platforms/python/3.10.4/**. [NOTE: This is where the package thinks Python is it seems].....
Running pip install....
Copying files to destination directory 'tmp/build/expressbuild'
Is there a way around this issue?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Azure Python Function App build on a Dedicated Plan, focusing on the package's build step and the interpreter path shown during pip install. Compare the Oryx path /tmp/oryx/platforms/python/3.10.4 with the user Python location; done means the built package uses the correct interpreter when the app runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- build-system, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100