new release?

[keewis]

Since the last release in October we had quite a few bugfixes:

• Fix to_reduced_units #1417
• Fix uncertainties & failing CI with coverage #1420
• Fix mutating the application registry #1403
• Add support for python 3.10 #1399
• Fix Quantity & Unit is_compatible_with with registry active contexts #1426
• Parse inf and nan in Quantity #1435
• properly deprecate the current behavior of the default_format option #1419
• to_reduced_units() fails with g*t/kg #1427 / Fix 1427: Keep track of exponent reduction #1449
• Fix use of offset units for higher dimensional units (e.g. gauge pressure #1066) #1409
• Remove most pytest warnings #1478
• Fix parsing of units string with same canonalized name #1476
• Fix to_reduced_units with dimensionless units #1481

some new features:

• Add volumetric flow rate and sverdrup #1404
• Add "cooling tower tons" to default units #1484
• expose some of the internal test functions in pint.testing #1421
• custom formatters: pass unit modifiers to the formatter #1448: needs more time to review
• implement numpy.nanprod #1369
• Update hour symbol to h #1454

and some docs updates (including the redesign):

• add a example for a custom unit formatter #1422
• remove pintpandas notebook #1483
• New documentation #1474: pushed back to the next release

and I'm sure I missed a few PRs (if so, feel free to edit the post)

We were originally planning to make a bugfix release, but I think we could just as well make a full release. What do you think, @hgrecco, @jules-ch?

[dalito]

What about merging #1409, too? It fixes a bug for offset units of higher dimension.

[jules-ch]

I'll check those PRs.

We can also change minimum Version support according to NEP29.

Python 3.8+
Numpy 1.19+

[hgrecco]

Agreed on doing a release, maybe also a pint-pandas one just after that. Let's put a deadline. @jules-ch when do you think is reasonable?

[jules-ch]

I've reviewed @keewis PRs.
I think we can say end of this month.
I'l try to fix some bugs in the meantime

[jules-ch]

@keewis can you make the appropriate changes after my review on #1419 #1421 #1422
So I can merge them.

[keewis]

sure, can you tell me what exactly I should change?

[keewis]

@jules-ch, what do we need to make this happen? I really hope it's not me that's blocking this...

[jules-ch]

Ok we should be good to go for a release, just waiting for #1454 to be merged.

@keewis I'm gonna wait for #1448, I haven't had time to review it, and I'm not sure delegating to registered formatter is making things simpler for the end user.
Can we delay this PR to the next release ?

[keewis]

it's not really urgent, but I was hoping to make use of this in a unit format that changes significantly once ~ is passed. I guess that means we can push it back for now?

What do you think about merging #1404?

[hgrecco]

I was looking at the PRs which are still open (and not included here):

• Use application registry in docs #1275 we could merge a version of this
• WIP: floordiv, mod, divmod #943 #946 As stated here I think this works as expected and can be closed
• Added new survey foot USCS group for deprecation support. #1022 I think we can merge this and add it as breaking change referencing survey foot phase out #1021
• Fix #1190 Make is_compatible_with function work with dimensionless types & string parsing errors. #1191 Not sure

[hgrecco]

Shall we release this weekend?

[keewis]

that would be great. What would be needed get there?

Edit: For the record, this is me volunteering to help

[jules-ch]

@keewis @hgrecco If you guys can review #1476 & #1481. After that I think we are ready to do a release.
Next release, we can push the new version of the documentation.

[keewis]

with both of those merged that only leaves us with the remaining PRs that add new units (#1404, and I guess #1484) and the PR removing the pint-pandas notebook (#1483).

I think #1483 is uncontroversial and can be merged immediately, while the new units need a decision (I do think we can merge those too – they're one-line changes – but I don't really know when new units are suitable for addition to the default_en.txt)

[hgrecco]

I agree with merging all three

[jules-ch]

Agreed, I think we need to provide guidelines on units that can be added to the default registry.
That will provide us checks that have to be fullfilled in order to add those units.

I'll add an issue for this.

[jules-ch]

@hgrecco Does the activation of Github Discussions is also on the menu, that can reduce the noise on Issues.
Ideas & day to day maintenance can be moved there also.

[jules-ch]

@hgrecco just merged the 3 PRs mentionned by @keewis

[OrangeChannel]

Should the new units be documented in the changelog? They weren't on the individual PRs.

[jules-ch]

Done in #1494

[jules-ch]

Ok this time I think we are ready for that release :)

[hgrecco]

I have just release Pint 0.19 Thanks for all the awesome work. I will do a few tests and then tweet about it!