Skip to content

Regenerate *.repr files using updated proper_repr for numpy ndarray. #6049

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.

Sign up for GitHub

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

Jump to bottom
Open
tanujkhattar opened this issue Apr 3, 2023 · 2 comments
Open

Regenerate *.repr files using updated proper_repr for numpy ndarray. #6049

tanujkhattar opened this issue Apr 3, 2023 · 2 comments
Assignees
@ozamanan
Labels
good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. kind/health For CI/testing/release process/refactoring/technical debt items no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Milestone
2025-T6: Code hea...

Comments

@tanujkhattar
Copy link
Collaborator

Description of the issue
#5991 updates proper_repr for numpy types. As a result, all repr files should be regenerated using the new proper_repr methods. This issue is to unblock the PR and track the changes to .repr files independently.

See #5991 (comment) for more details.
@tanujkhattar tanujkhattar added the kind/health For CI/testing/release process/refactoring/technical debt items label Apr 3, 2023
@tanujkhattar tanujkhattar mentioned this issue Apr 3, 2023
Merged
@pavoljuhas pavoljuhas added good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on labels Apr 18, 2023
@ozamanan
Copy link

ozamanan commented Jun 1, 2023

@tanujkhattar I'd like to take up this issue if no one is assigned to it.

@mhucka
Copy link
Contributor

mhucka commented Nov 16, 2024

@ozamanan For planning purposes, could you let us know the status of this item?

@WingCode WingCode mentioned this issue May 27, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ozamanan ozamanan

Labels
good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. kind/health For CI/testing/release process/refactoring/technical debt items no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Projects
Cirq 2025 roadmap
Status: No status
Milestone
2025-T6: Code health and project main...
Development

No branches or pull requests
4 participants
@mhucka @pavoljuhas @tanujkhattar @ozamanan