chore: Log versions and locations when loading environment

[tpoliaw]

Second part of #1457

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.23%. Comparing base (217d907) to head (cda0734).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1486   +/-   ##
=======================================
  Coverage   95.23%   95.23%           
=======================================
  Files          43       43           
  Lines        3145     3151    +6     
=======================================
+ Hits         2995     3001    +6     
  Misses        150      150           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[oliwenmandiamond]

Could you please copy and paste a snippet of logging that that will output so i can see how it looks?

[tpoliaw]

Running with the system-test config

2026-04-14 16:05:50,731     INFO blueapi.core.context Including devices from 'deviceManager' source dodal.beamlines.adsim:devices (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/beamlines/adsim.py])
2026-04-14 16:05:50,753     INFO blueapi.utils.connect_devices 2 devices connected:
2026-04-14 16:05:50,753     INFO blueapi.utils.connect_devices  det
    stage
2026-04-14 16:05:51,029     INFO blueapi.core.context Including plans from dodal.plans (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/plans/__init__.py])
2026-04-14 16:05:51,041     INFO blueapi.core.context Including plans from dodal.plan_stubs.wrapped (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/plan_stubs/wrapped.py])
2026-04-14 16:05:51,048     INFO blueapi.core.context Including plans from sample_plans (blueapi[version: 1.12.2.dev9+g8e9ce20ea.d20260312, location: /dls/athena/blueapi/src/sample_plans.py])

[oliwenmandiamond]

Running with the system-test config

2026-04-14 16:05:50,731     INFO blueapi.core.context Including devices from 'deviceManager' source dodal.beamlines.adsim:devices (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/beamlines/adsim.py])
2026-04-14 16:05:50,753     INFO blueapi.utils.connect_devices 2 devices connected:
2026-04-14 16:05:50,753     INFO blueapi.utils.connect_devices  det
    stage
2026-04-14 16:05:51,029     INFO blueapi.core.context Including plans from dodal.plans (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/plans/__init__.py])
2026-04-14 16:05:51,041     INFO blueapi.core.context Including plans from dodal.plan_stubs.wrapped (dls-dodal[version: 2.2.1, location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/plan_stubs/wrapped.py])
2026-04-14 16:05:51,048     INFO blueapi.core.context Including plans from sample_plans (blueapi[version: 1.12.2.dev9+g8e9ce20ea.d20260312, location: /dls/athena/blueapi/src/sample_plans.py])

Although I would rather have too much information than not enough, this is very verbose. When including the plans, we don't need the dodal version for every plan it uses because it would use the same dodal version? It only needs to be included once. I also think showing the full path is slight overkill because that is basically the same as the python import? For example
dodal.plan_stubs.wrappedand location: /dls/athena/blueapi/.venv/lib/python3.11/site-packages/dodal/plan_stubs/wrapped.py basically convey the same information.

I think the ideal logging would be something like this:

2026-04-14 16:05:50,731     INFO Using bluesky[version: XXX]
2026-04-14 16:05:50,731     INFO Using blueapi[version: 1.12.2.dev9+g8e9ce20ea.d20260312]
2026-04-14 16:05:50,731     INFO Using dls-dodal[version: 2.2.1]
2026-04-14 16:05:50,731     INFO Using ophyd-async[version: 0.17]
2026-04-14 16:05:50,731     INFO Using daq-config-server[version: XXX]
...

These are probably the five most import things we need to know versions of to help find conflicts or behaviour changes (probably missed some). It would be good if it include either these important ones only (+ any others we can think of) or just log the version of every dependency in a list like a CI job does. My preference is probably just log every dependency to be honest and then we can very quickly check exactly what the server is using.

Any thoughts on this though?

[tpoliaw]

I don't want to be hardcoding packages into blueapi logging. We can deduplicate the packages reported if it would be clearer but only packages included in the environment (as plans or devices) would be included.

The idea of the path was to differentiate which packages were installed in the venv vs the scratch space.

For a full version breakdown you can always use the /python_environment endpoint.

[tpoliaw]

Logging now reduced to single version report of each package being used for plans or devices

2026-04-15 11:05:43,850     INFO blueapi.core.context Using package blueapi[1.12.2.dev9+g8e9ce20ea.d20260312]
2026-04-15 11:05:43,850     INFO blueapi.core.context Using package dls-dodal[2.2.1]

[oliwenmandiamond]

Yes I think this is an improvement, thank you!