fix: replace debug print() statements with logger.debug() in metric modules

[Balamuralikrishna123]

hi, i was going through the codebase and noticed issue #71
about replacing print() statements with proper logging.
i went through all the metric modules and replaced the debug
print() calls with logger.debug() and added the logger
setup at the top of each file where it was missing.
files changed:

• feature_relevance.py
• class_imbalance.py
• conditional_demo_disp.py
• correlation_score.py
• privacy_measure.py
  this fixes the issue and makes the debug output properly
  controllable through python logging levels instead of
  always printing to stdout.
  also working on the zarr reader in PR feat: add Zarr file format support #76 and planning
  to tackle the ROOT reader from issue Add root file reader #49 next.

[Balamuralikrishna123]

the lint failure appears to be related to the deprecated Node.js 20 GitHub Actions ) rather than the code changes. the same warning appears across other PRs in the repo as well

[Aman-Cool]

Hey @Balamuralikrishna123, thanks for the contribution, but the PR needs a cleanup before we can merge.

The zarr reader changes (zarr_reader.py, file_parser.py) don't belong here, that's PR #76. Not sure how they ended up in this branch, but please rebase and drop those commits. Also, the branch currently has merge conflicts that need to be resolved, resolving them after dropping those commits should clean things up.

One thing I'd encourage, make sure you're reading through the changes before submitting. It's easy to miss things like bundled unrelated code, and we want contributors who are comfortable owning their changes. So just a quick sanity check:

• Why logger.debug() and not logger.info()?
• Why define the logger at module level?

Answer those, clean up the branch, and we'll get this merged!

[Aman-Cool]

@kaveenh, please have a look!

[Balamuralikrishna123]

Hey @Balamuralikrishna123, thanks for the contribution, but the PR needs a cleanup before we can merge.

The zarr reader changes (zarr_reader.py, file_parser.py) don't belong here, that's PR #76. Not sure how they ended up in this branch, but please rebase and drop those commits. Also, the branch currently has merge conflicts that need to be resolved, resolving them after dropping those commits should clean things up.

One thing I'd encourage, make sure you're reading through the changes before submitting. It's easy to miss things like bundled unrelated code, and we want contributors who are comfortable owning their changes. So just a quick sanity check:

• Why logger.debug() and not logger.info()?
• Why define the logger at module level?

Answer those, clean up the branch, and we'll get this merged!

Hey @Balamuralikrishna123, thanks for the contribution, but the PR needs a cleanup before we can merge.

The zarr reader changes (zarr_reader.py, file_parser.py) don't belong here, that's PR #76. Not sure how they ended up in this branch, but please rebase and drop those commits. Also, the branch currently has merge conflicts that need to be resolved, resolving them after dropping those commits should clean things up.

One thing I'd encourage, make sure you're reading through the changes before submitting. It's easy to miss things like bundled unrelated code, and we want contributors who are comfortable owning their changes. So just a quick sanity check:

• Why logger.debug() and not logger.info()?
• Why define the logger at module level?

Answer those, clean up the branch, and we'll get this merged!

hi @Aman-Cool , thanks for pointing that out , yeah i noticed the zarr files got bundled in by mistake, i will clean that up and push a fix shortly.
for your questions:

1. i went with logger.debug() because these print statements looked like they were there for debugging purposes, not for regular info output. debug level only shows up when someone explicitly sets logging to DEBUG so it wont clutter normal output.
2. module level logger is the standard way i have seen it done in most python projects. using name gives each module its own logger which is cleaner than defining it inside every function separately.will clean up the branch now and push. Thank you.

[Aman-Cool]

@Balamuralikrishna123, I noticed this bundling in #82 too...have a look.

[Balamuralikrishna123]

opened a clean version without the zarr changes in PR #83, please review that one instead. sorry for the mess.

[kaveenh]

@Balamuralikrishna123 Thanks for your contributions! Please avoid creating multiple PRs for the same changes. Please update or close existing PRs so maintainers can manage the repository efficiently.

[Balamuralikrishna123]

@Balamuralikrishna123 Thanks for your contributions! Please avoid creating multiple PRs for the same changes. Please update or close existing PRs so maintainers can manage the repository efficiently.

hey @kaveenh understood, sorry for the confusion! PR #83 is the clean version with only the logging changes.