• dallen@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    11 days ago

    Really looking forward to running type checks with pre-commit. Mypy is just too slow with most code bases.

    • Doccool@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      10 days ago

      Same honestly. Mypy is sooo slow… Very excited for the emerging landscape with both Ty and Pyrefly

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    2
    ·
    10 days ago

    Ive tried ty in neovim and it runs circles around basedpyright. You can feel its instant. You should try it.

  • logging_strict@programming.dev
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    10 days ago

    Really don’t understand why post about a dev pre-release? It’s confusing, what is the goal trying to achieve with this post?

    And why not using semantic versioning?

    >>> from packaging.version import Version
    >>> v = Version("0.0.1-alpha.22")
    >>> str(v)
    '0.0.1a22'
    >>>
    

    0.0.1alpha22 or 0.0.1a22 although that looks alot like pre-release dev level fixes. In which case, 0.0.1a0-dev22

    There is no project ever that had 22 alpha releases. That’s nuts. Your alpha testers must be really overworked.

    Fire the six year old in charge versioning decisions ;-)

    Your welcome. Your future user base can thank me later for putting a stop to that atrocity posing as versioning

    epoch is used to transition from random nonsense versioning to semantic versioning.

    There is no shame/stigma for admitting a mistake and correcting it. Eventhough that epoch will now stick around with the project forever.

    • lens0021@programming.devOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      10 days ago

      I posted because I was happy to see some software in growing up. If you are not comfortable, I will not post this kind again.

        • logging_strict@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          7 days ago

          Until @fruitcantfly set me straight, couldn’t read and understand the version str and was unaware Rust followed a different pattern than Python.

      • Doccool@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        10 days ago

        I recommend you ignore this guys takes, he’s posted a lot of wild and controversial takes on other topics and honestly it’s not like we have too much posts in this community anyway. Post if you like, up- and downvotes are meant to give and indication of what people think. Not a single person. Conversation is good even if it’s on a alpha release!

          • logging_strict@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            7 days ago

            Never even viewed Milestones before. Thanks @lens0021 for pointing them out. Link to Milestone found on both Issues and PR sections.

            Don’t know why been ignoring it, maybe something like,

            “Milestones ewww scary. Might be dangerous better not click on it”

      • logging_strict@programming.dev
        link
        fedilink
        arrow-up
        1
        arrow-down
        3
        ·
        edit-2
        10 days ago

        My point is to wait for an actual release, a call to action, or an article about the project. Release notes on a dev pre-release is odd.

        Not discouraging you from posting. You are very welcome to post here. And btw thanks for responding.

        This is the semantic versioning spec, but it’ll give you nightmares.

        Here are examples with explanation for each versioning component. Much easier on the eyes

        gl

          • logging_strict@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            7 days ago

            Thanks for the link to Cargo’s versioning docs.

            In Python, packaging is authoritative. Past that version str thru packaging and it was modified.

            Honestly misunderstood, thinking there was 22 alpha releases.

            Am still misreading it. The alpha and dev portions are not distinctive enough to be clear. Didn’t even see in the Cargo dev portion mentioned.

            Obviously publishing dev releases is not allowed, but in git dev commits are a thing.