Skip to content

Question: ETA for v5 release? #999

Open

Description

@MattCWheeler

Is there an ETA for release of v5? This feature is killer and when released I should be able to adopt jsonargparse for my projects.

Cheers.

Activity

  1. mauvilsa commented on Oct 2, 2026

    @mauvilsa
    Owner

    There is no specific date. Hopefully soon. It is a major release, so I will not rush it. I might release 5.0.0.dev1 possibly next week. This issue could be a place to ask people to try it out and receive feedback. Then possibly a 5.0.0rc1 and then the final release.

  2. MattCWheeler commented on Oct 5, 2026

    @MattCWheeler
    Author

    I'm happy to help try it out. I have an internal CLI currently using arg parse with args files that inherit from and override each other, with command-line flags for further overrides, but the number of args is growing (past 20 now) and we need to support a nested structure to keep it comprehensible because need to add at least 20 more.

  3. mauvilsa commented on Oct 9, 2026

    @mauvilsa
    Owner

    🚀 jsonargparse v5.0.0rc1 is out, please help test it!

    The first release candidate of v5.0.0 is available on PyPI. This is a major release, so it has breaking changes. Before the final release I'd like to find out how it works in real projects, so that regressions and migration problems get fixed first.

    Install

    pip install --upgrade --pre jsonargparse
    # or pin it: pip install jsonargparse==5.0.0rc1

    Notable changes

    • All features deprecated in v4 have been removed. The migration guide (migrate-v5) explains how to update. Fixing the deprecation warnings you get with v4.52.0 covers most of it. Two more are coming in v4.53.0, which isn't released yet: abbreviated options, and function or method groups with a nested_key in instantiate. To get all the warnings now, install from the v4 branch and run with JSONARGPARSE_DEPRECATION_WARNINGS=all:
      pip install "jsonargparse @ git+https://github.com/omni-us/jsonargparse.git@v4"
    • Some defaults changed: parser_mode is now json_or_yaml, allow_abbrev is False, instantiate_subclass_spec_in_any is False, and pyyaml is no longer a required dependency (install the yaml extra).
    • Errors now say where a value came from, e.g. Source: config file config.yaml:3.
    • Configs can be composed with __include__.
    • Support for *args, datetime/date/time, recursive type aliases, PEP 661 sentinels, Counter, Iterator and more.
    • Many fixes for links, subcommands, relative paths and more.

    The full list is in the changelog.

    How to help

    1. Run your test suite or CLI against 5.0.0rc1.
    2. If something breaks or behaves unexpectedly, open an issue with a minimal reproduction and mention that it's about the RC. A short comment here before creating an issue is also fine.
    3. Making the migration instructions clear is also an objective, so any suggestions in that direction are also welcome.
    4. If everything works, a short 👍 comment here is also useful.
      Thanks! 🙏

    Pinging past contributors, since you know the project and might want to try it: @Borda @bryant1410 @a-gardner1 @MiguelMonteiro @speediedan @kianmeng @Erotemic @ioangatop @psirenny @carmocca @nkrishnaswami @PabloLION @PierreGtch @mquillot @hadipash @Solvik @sfc-gh-tdwojak @ModdingFox @diederus @0x404 @tshu-w @MilkClouds @michael-hoss @HubertPalo @euxhenh @EthanMarx @eggry @DianLiI @cody-mar10 @mougams @asmacdo @ganatraad @Andry-Bal

  4. mauvilsa commented on Oct 26, 2026

    @mauvilsa
    Owner

    Some days ago I released v4.53.0 and today I released v5.0.0rc2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededpending author responseA question was asked or some work is pendingquestionFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions