uv for quadfeather

[bmschmidt]

Important

This PR updates the project to use Python 3.12 and uv for package management, adding pyproject.toml and uv.lock for dependency management.

• Python Version:
  • Adds .python-version file specifying Python 3.12.
• Package Management:
  • Updates README.md to use uv for managing Python packages instead of pip.
  • Adds pyproject.toml to define project metadata and dependencies, including quadfeather.
  • Introduces uv.lock to lock dependencies, including numpy, pandas, pyarrow, and quadfeather.

^{This description was created by for 12fb692. You can customize this summary. It will automatically update as commits are pushed.}

[bmschmidt]

• refactor manifests to be lazier #173 : 2 dependent PRs (#174 , #195 )
• uv for quadfeather #154 👈 (View in Graphite)
• cleaner deeptable instantiation pattern #172
• update evaluation set size on sortedDataSelection #192 : 1 other dependent PR (#193 )
• no linting in ci #194 : 1 other dependent PR (#81 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 12fb692 in 1 minute and 53 seconds. Click for details.

• Reviewed 203 lines of code in 4 files
• Skipped 1 files when reviewing.
• Skipped posting 6 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .python-version:1

• Draft comment:
  Python version is set to 3.12. Verify that this upgrade (from earlier 3.9/3.10 mentions) is intentional for compatibility.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 70% This comment is asking the PR author to verify the intention behind upgrading the Python version, which violates the rule against asking for confirmation of intention. It does not provide a specific suggestion or point out a specific issue with the code.

2. README.md:57

• Draft comment:
  The tone in the package management instructions is informal. Consider using a more professional phrasing.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 70% None

3. pyproject.toml:4

• Draft comment:
  The project description is still a placeholder. Update it to reflect Deep Scatterplots’ purpose.
• Reason this comment was not posted:
  Confidence changes required: 70% <= threshold 70% None

4. pyproject.toml:6

• Draft comment:
  The Python requirement is set to '>=3.12'. Confirm this is intentional as it may exclude users on slightly older versions.
• Reason this comment was not posted:
  Confidence changes required: 70% <= threshold 70% None

5. uv.lock:1

• Draft comment:
  This auto-generated lock file pins dependencies (including the quadfeather git commit). Ensure it remains updated and consistent.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 70% None

6. README.md:57

• Draft comment:
  Typographical suggestion: 'python' should be capitalized as 'Python' when referring to the programming language.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 70% While technically correct that 'Python' should be capitalized when referring to the programming language, this is a very minor typographical issue in documentation. The rules state not to make comments that are obvious or unimportant. This seems like a very low-priority change that doesn't affect functionality or code quality. The capitalization of Python is the official style guide recommendation, so there's an argument for consistency and professionalism in documentation. While correct, this type of minor documentation fix doesn't warrant a PR comment - it's too trivial and could be fixed in a general documentation pass if needed. Delete this comment as it violates the rule about not making obvious or unimportant comments. This minor typographical suggestion doesn't merit a PR comment.

Workflow ID: wflow_jYD3IEYYNdTcsSLE

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[bmschmidt]

Merge activity

• May 26, 4:18 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 26, 4:25 PM UTC: Graphite rebased this pull request as part of a merge.
• May 26, 4:27 PM UTC: @bmschmidt merged this pull request with Graphite.