Skip to content

Conversation

@ypriverol
Copy link
Contributor

@ypriverol ypriverol commented Jan 23, 2026

Summary

Removing plot capabilities of pridepy. Updated the plotly dependency constraint from a caret requirement (^5.18.0) to a minimum version requirement (>=5.18.0), allowing installation of newer plotly versions while maintaining compatibility with 5.18.0 and above.

Changes

  • Modified pyproject.toml to change plotly dependency from ^5.18.0 to >=5.18.0

Details

This change relaxes the version constraint on plotly, which previously restricted installations to versions within the 5.18.x range (due to the caret operator). The new constraint allows any version 5.18.0 or higher, enabling users to benefit from plotly updates and bug fixes without waiting for a new release of this project.

This is a non-breaking change that improves dependency flexibility while maintaining a minimum version guarantee for compatibility.

ypriverol and others added 6 commits October 22, 2025 14:46
version bump 0.0.9 -> 0.0.10
The code was looking for 'aspera_tokenauth_id_rsa' but the actual
key file is named 'asperaweb_id_dsa.openssh'. This caused authentication
failures when downloading files via Aspera protocol.

Fixes authentication prompt issue when using aspera protocol.
Fix Aspera key filename to match actual key file
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 23, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review
Copy link
Contributor

qodo-code-review bot commented Jan 23, 2026

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

  • Update
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@ypriverol ypriverol changed the title Relax plotly version constraint to allow newer versions Remove plotting capabilities of pridepy because they are not exposed on the commandline and not needed Jan 23, 2026
@ypriverol ypriverol linked an issue Jan 23, 2026 that may be closed by this pull request
@qodo-code-review
Copy link
Contributor

qodo-code-review bot commented Jan 23, 2026

PR Code Suggestions ✨

No code suggestions found for the PR.

The caret constraint (^5.18.0) was limiting plotly to <6.0.0, causing
dependency conflicts for users who want to use plotly 6.x. The codebase
only uses stable, basic plotly APIs (go.Bar and plotly.offline.plot)
that are compatible with both plotly 5.x and 6.x.

https://claude.ai/code/session_01VuwA6zF7mR9zPdgY2Fn8Nn
The statistics module was orphaned code that was never integrated into
the CLI or exported from the package. Removing it eliminates the plotly
dependency entirely, reducing install conflicts for users.

Removed:
- pridepy/statistics/ directory
- plotly from pyproject.toml, requirements.txt, environment.yml, recipe/meta.yaml

https://claude.ai/code/session_01VuwA6zF7mR9zPdgY2Fn8Nn
@ypriverol ypriverol force-pushed the claude/fix-plotly-dependency-W3MX1 branch from 6c9bf5e to 7b5d5ab Compare January 23, 2026 09:47
@ypriverol
Copy link
Contributor Author

@sureshhewabi @selvaebi @chakrabandla do we use the plotting capabilities of pridepy?

@ypriverol ypriverol merged commit 7550f36 into dev Jan 23, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pridepy requires old Plotly verions

5 participants