Python track: exercise 08 doesn't mention re-running pip install after updating requirements.txt for local testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Open exercises/Python/08-deploy-agent-to-cf.md and review the “Update requirements.txt” section at lines 255-282. Add the local installation step and note that it is needed before testing locally, while Cloud Foundry installs requirements during deployment. Verify that the rendered exercise clearly distinguishes local testing from cf push.
Written by the indexing model from the issue text.
Description
Summary
The "Update requirements.txt" section (08-deploy-agent-to-cf.md:255-282) instructs learners to add crewai[a2a] and a2a-sdk[http-server] to requirements.txt, then moves straight into creating manifest.yml for Cloud Foundry deployment. There's no pip install -r requirements.txt (or equivalent) command shown anywhere in the exercise.
Effect
This works fine for the actual CF deployment, since CF's Python buildpack automatically runs pip install -r requirements.txt during cf push — the deployed app gets the new dependencies without any local action needed.
However, if a learner wants to test the A2A server locally before deploying (a reasonable thing to want to do, and not explicitly discouraged anywhere), editing requirements.txt alone doesn't install anything into their existing venv. Running the server locally at that point fails with ModuleNotFoundError: No module named 'a2a', since the new packages were never actually installed — only added to a text file.
Suggested fix
Add an explicit step after the requirements.txt update, e.g.:
bash pip install -r requirements.txt
with a short note that this is needed if testing locally before cf push (even though CF's buildpack handles it automatically during deployment).
Environment
Reproduced on a personal SAP AI Core tenant, Python (CrewAI + LiteLLM) track, testing the A2A server locally before Cloud Foundry deployment.
- Dominant language
- Python
- Stars
- 54
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from SAP-samples/codejam-code-based-agents
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SAP-samples/codejam-code-based-agents#37 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SAP-samples/codejam-code-based-agents#35 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
All issues in SAP-samples/codejam-code-based-agents
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·