Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark conda/plan.py for Deprecation (and do related refactoring work as necessary) #12421

Closed
2 tasks done
beeankha opened this issue Mar 1, 2023 · 5 comments
Closed
2 tasks done
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release source::anaconda created by members of Anaconda, Inc. type::tech-debt identifies or resolves some technical debt
Milestone

Comments

@beeankha
Copy link
Contributor

beeankha commented Mar 1, 2023

What is the idea?

There is a TODO comment marking the conda/plan.py module for deprecation that got added in the pull request titled "separate conda package metadata under new root-level key in repodata (#8639)".

Deprecating/removing that module (and related test file) entirely is not a straightforward task, as there are references to the contents of conda/plan.py in files such as conda/misc.py and conda/exports.py. This deprecation will require:

Tasks

@beeankha beeankha added source::anaconda created by members of Anaconda, Inc. type::tech-debt identifies or resolves some technical debt labels Mar 1, 2023
@kenodegard kenodegard added the backlog issue has been triaged but has not been earmarked for any upcoming release label Mar 3, 2023
Copy link

github-actions bot commented Mar 3, 2024

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Mar 3, 2024
@beeankha beeankha removed the stale [bot] marked as stale due to inactivity label Mar 4, 2024
@jezdez
Copy link
Member

jezdez commented Mar 5, 2024

@beeankha Is there anything we need to do about this ticket?

@beeankha beeankha added this to the 24.5.x milestone Mar 8, 2024
@beeankha beeankha modified the milestones: 24.5.x, 24.7.x, 24.3.x Apr 15, 2024
@beeankha
Copy link
Contributor Author

@jezdez nothing in particular is blocking this work afaik, we just need to get started on it; if it's more complicated than anticipated we can move it to the 24.7.x milestone. I'll do at least the preliminary research (task 1) this week!

@beeankha beeankha modified the milestones: 24.5.x, 24.7.x Apr 18, 2024
@beeankha
Copy link
Contributor Author

beeankha commented Apr 19, 2024

Discoveries for Step 1 of this task:

In conda/conda

In conda/conda-build

@beeankha
Copy link
Contributor Author

beeankha commented May 3, 2024

Resolved per merging of #13881

@beeankha beeankha closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release source::anaconda created by members of Anaconda, Inc. type::tech-debt identifies or resolves some technical debt
Projects
Archived in project
Development

No branches or pull requests

3 participants