github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-21 13:31:55 -05:00
Code Issues 114 Packages Projects Releases 24 Wiki Activity

[GH-ISSUE #1209] Installation Script did not work #4351

New Issue
Closed
opened 2026-04-19 12:22:11 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-19 12:22:11 -05:00
Owner
Copy Link

Originally created by @Roldao-Neto on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1209

I tried running the installation script in my Linux (Pop_OS Cosmic - currently in "beta"). It did not work.

I do have uv installed, so I suppose this was the reason a .venv was not created. Then I tried running uv sync, but the dependencies do not match:

rolds@pop-os:~/tinytorch$ uv sync
× No solution found when resolving dependencies
│ for split (markers: python_full_version ==
│ '3.8.*'):
╰─▶ Because the requested Python version
(>=3.8) does not satisfy Python>=3.9 and
jupyter-book>=1.0.0,<=1.0.4.post1 depends
on Python>=3.9, we can conclude that
jupyter-book>=1.0.0,<=1.0.4.post1 cannot
be used.
And because only the following versions of
jupyter-book are available:
jupyter-book<=1.0.0
jupyter-book==1.0.2
jupyter-book==1.0.3
jupyter-book==1.0.4
jupyter-book==1.0.4.post0
jupyter-book==1.0.4.post1
jupyter-book>=2.0.0
we can conclude that
jupyter-book>=1.0.0,<2.0.0 cannot be used.
And because tinytorch[docs] depends on
jupyter-book>=1.0.0,<2.0.0 and your project
requires tinytorch[docs], we can conclude
that your project's requirements are
unsatisfiable.

  hint: While the active Python version is
  3.12, the resolution failed for other Python
  versions supported by your project. Consider
  limiting your project's supported Python
  versions using `requires-python`.

  hint: The `requires-python` value (>=3.8)
  includes Python versions that are not
  supported by your dependencies (e.g.,
  jupyter-book>=1.0.0,<=1.0.4.post1 only
  supports >=3.9). Consider using a more
  restrictive `requires-python` value (like
  >=3.9).

After changing the pyproject.toml file to require Python >= 3.9, it worked.

Originally created by @Roldao-Neto on GitHub (Mar 4, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1209 I tried running the installation script in my Linux (Pop_OS Cosmic - currently in "beta"). It did not work. I do have uv installed, so I suppose this was the reason a .venv was not created. Then I tried running uv sync, but the dependencies do not match: rolds@pop-os:~/tinytorch$ uv sync × No solution found when resolving dependencies │ for split (markers: python_full_version == │ '3.8.*'): ╰─▶ Because the requested Python version (>=3.8) does not satisfy Python>=3.9 and jupyter-book>=1.0.0,<=1.0.4.post1 depends on Python>=3.9, we can conclude that jupyter-book>=1.0.0,<=1.0.4.post1 cannot be used. And because only the following versions of jupyter-book are available: jupyter-book<=1.0.0 jupyter-book==1.0.2 jupyter-book==1.0.3 jupyter-book==1.0.4 jupyter-book==1.0.4.post0 jupyter-book==1.0.4.post1 jupyter-book>=2.0.0 we can conclude that jupyter-book>=1.0.0,<2.0.0 cannot be used. And because tinytorch[docs] depends on jupyter-book>=1.0.0,<2.0.0 and your project requires tinytorch[docs], we can conclude that your project's requirements are unsatisfiable. hint: While the active Python version is 3.12, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`. hint: The `requires-python` value (>=3.8) includes Python versions that are not supported by your dependencies (e.g., jupyter-book>=1.0.0,<=1.0.4.post1 only supports >=3.9). Consider using a more restrictive `requires-python` value (like >=3.9). After changing the pyproject.toml file to require Python >= 3.9, it worked.
GiteaMirror added the area: booktype: bug labels 2026-04-19 12:22:11 -05:00
GiteaMirror commented 2026-04-19 12:22:13 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Mar 4, 2026):

Hey @Roldao-Neto, thanks for posting this. Feel free to submit a PR if you'd like, or I can update it later too. Thanks for reporting this!

<!-- gh-comment-id:3994444528 --> @profvjreddi commented on GitHub (Mar 4, 2026): Hey @Roldao-Neto, thanks for posting this. Feel free to submit a PR if you'd like, or I can update it later too. Thanks for reporting this!
GiteaMirror commented 2026-04-19 12:22:14 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Apr 3, 2026):

Hey @Roldao-Neto just checking back on this. Were you able to get things working? The Python version constraint has been tightened up since then. If you're still running into issues let me know, otherwise I'll close this one out in a couple weeks. Thanks for reporting it!

<!-- gh-comment-id:4184722725 --> @profvjreddi commented on GitHub (Apr 3, 2026): Hey @Roldao-Neto just checking back on this. Were you able to get things working? The Python version constraint has been tightened up since then. If you're still running into issues let me know, otherwise I'll close this one out in a couple weeks. Thanks for reporting it\!
GiteaMirror commented 2026-04-19 12:22:15 -05:00
Author
Owner
Copy Link

@Roldao-Neto commented on GitHub (Apr 3, 2026):

Hello @profvjreddi , it seems everything is working now, but if you want TinyTorch to be uv supported, last time I checked, there are some things that should be done. In my last PR, I did the minimum to get it working, but I did not follow some best practices.

If you are interested in making it uv compatible, just respond to this message and tell me if you want to try to make it work with the updated libraries or only with the current versions that are being used. I will create a PR on this later if you want to.

Best Regards.

<!-- gh-comment-id:4184832905 --> @Roldao-Neto commented on GitHub (Apr 3, 2026): Hello @profvjreddi , it seems everything is working now, but if you want TinyTorch to be uv supported, last time I checked, there are some things that should be done. In my last PR, I did the minimum to get it working, but I did not follow some best practices. If you are interested in making it uv compatible, just respond to this message and tell me if you want to try to make it work with the updated libraries or only with the current versions that are being used. I will create a PR on this later if you want to. Best Regards.
GiteaMirror commented 2026-04-19 12:22:15 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Apr 3, 2026):

Closing — @Roldao-Neto confirmed the install is working now. Thanks for the PR contributions to improve uv support!

<!-- gh-comment-id:4184853491 --> @profvjreddi commented on GitHub (Apr 3, 2026): Closing — @Roldao-Neto confirmed the install is working now. Thanks for the PR contributions to improve uv support!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label area: book type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#4351
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?