cnpryer/huak

๐Ÿ“‹ Status tracker

cnpryer opened this issue ยท 7 comments

  • Use Huak to install Python releases
  • Use Huak to use and manage toolchains
  • #852
  • #815
  • #862
  • #865
  • #888
  • #890
  • #889
  • Ship with bundled tools exposed in top-level bin directory
  • #687
  • #853
  • #824
  • #809
    • Animated terminal interface for sub-processes
    • Cargo-makeover
  • #722
  • #857
  • #836
  • Robustness improvements
  • Use Huak for activating synchronized shells (#486)
  • #794
  • Optimize toolchains, virtual environments, and package installs
  • Optimize slower operations
    • Faster package installation
    • Faster formatting
    • Faster linting
    • Faster package resolution
    • Maximize snappy, minimal experience
  • Lock dependencies installed to virtual environments

See milestones for more project status visibility.

@cnpryer Hi! The project looks cool! I wonder how in your opinion it is compared to rye and why you decided to switch to helping with rye?

Hi! I'd say the main differences right now are probably how far huak is willing to go for a specific ux and that rye has more mature toolchain features.

huak would have similar toolchain features (I may go with PyBI), so for the most part both projects are very similar. rye also has a better story for dependency management at the moment.

Overall rye looks great and aligns mostly with the vision for huak, so it's worth consolidating efforts.

I will mention, however, that I'm not abandoning huak entirely just yet. Anything can happen.

Since discovering Huak last week I've been able to install my project's dependencies in isolation, as well as test and lint my code, all of which I'd struggled to do in Python before. Particularly the testing--does Rye offer any help with that? Maybe it does, and it's only the documentation that's lacking?

So if I understand correctly you're referring to how huak test exists out of the box and rye test would be more like rye run test with the following pyproject.toml configuration:

[tool.rye.scripts]
test = "pytest"

If so the short answer is no this doesn't exist the same way in rye as it does with huak. This is that "specific ux" i mentioned here.

I don't think this ux is completely off the table since a lot of rye's inspiration draws from cargo. It probably depends on what Armin's preference/vision is. You could read more about his thoughts here: https://rye-up.com/philosophy/. Note that, unless I missed it, there is no preference listed in the "opinionated defaults section" related to testing specifically.

Yeah, that's what I meant. If using Pytest in Rye is as easy as adding that tool.rye.script section to the pyproject.toml, then I guess Rye would fit my purposes. Maybe it just needs better documentation. At any rate I'm happy using Huak for now, as it seems to have solved my problems with Python's confusing imports system.

Would love feedback for the toolchain plans