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.
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!
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\!
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.
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!
cd tinytorch
source .venv/Scripts/activate
tito setup
Checking prerequisites...
✓ Git 2.55.0.windows.2
bash: cd: tinytorch: No such file or directory
bash: .venv/Scripts/activate: No such file or directory
bash: tito: command not found
Thank you.
<!-- gh-comment-id:4969836884 -->
@gusscruz commented on GitHub (Jul 14, 2026):
I tried running the installaltion script, but I received this message and tinytorch was not installed. I have Python 3.13.9, Anaconda distribution.
curl -sSL mlsysbook.ai/tinytorch/install.sh | bash
# Activate and verify
cd tinytorch
source .venv/Scripts/activate
tito setup
Checking prerequisites...
✓ Git 2.55.0.windows.2
bash: cd: tinytorch: No such file or directory
bash: .venv/Scripts/activate: No such file or directory
bash: tito: command not found
Thank you.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
After changing the pyproject.toml file to require Python >= 3.9, it worked.
@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!
@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!
@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.
@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!
@gusscruz commented on GitHub (Jul 14, 2026):
I tried running the installaltion script, but I received this message and tinytorch was not installed. I have Python 3.13.9, Anaconda distribution.
curl -sSL mlsysbook.ai/tinytorch/install.sh | bash
Activate and verify
cd tinytorch
source .venv/Scripts/activate
tito setup
Checking prerequisites...
✓ Git 2.55.0.windows.2
bash: cd: tinytorch: No such file or directory
bash: .venv/Scripts/activate: No such file or directory
bash: tito: command not found
Thank you.