cswartzvi opened a new pull request, #1374:
URL: https://github.com/apache/hamilton/pull/1374

   Hi all - I was looking through the codebase to help create the first ASF 
release (#1336) and thought we might benefit from a little clean-up. Please 
have a look and let me know if I went too far  with anything - happy to roll 
things back!
   
   ## Changes
   
   - [x] Moved top-level images to new `assets` folder. Do we need to keep 
these?
   - [x] Moved top-level md files to either `docs` or `writeups`. Maybe these 
should be fully integrated with the docs?
   - [x] Deleted `setup.py`, removing the legacy Python packaging script and 
related logic
   - [x] Remove unused configuration files (`.style.yapf`, `.flake8`, ...)
   - [x] Update manifest (remove non-existent requirements files)
   - [x] Update min required python to `3.8.1`. This allows contributors to use 
`uv sync` without allowing prereleases (as per the last meetup, I would like 
bump the min required python to `3.9` next)
   - [x] Update `uv` configuration. Since `pip` now has support, I moved dev 
dependencies to `dependency-groups` (PEP 735)
   - [x] Fix broken tests ~(maybe out of scope for this PR)~
   
   ## How I tested this
   
   No changes to codebase
   
   ## Notes
   
   N/A
   
   ## Checklist
   
   - [x] PR has an informative and human-readable title (this will be pulled 
into the release notes)
   - [x] Changes are limited to a single goal (no scope creep)
   - [x] Code passed the pre-commit check & code is left cleaner/nicer than 
when first encountered.
   - [x] Any _change_ in functionality is tested
   - [x] New functions are documented (with a description, list of inputs, and 
expected output)
   - [x] Placeholder code is flagged / future TODOs are captured in comments
   - [x] Project documentation has been updated if adding/changing 
functionality.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to