Skip to content

Releases: polm/posuto

2022.07 Updates

02 Jul 12:00
Compare
Choose a tag to compare

posuto has been updated with this month's changes from JP Post. Changes include:

  • many changes to 上鳥羽 in Kyoto
  • the creation of みらい平 in Ibaraki, named after a station
  • smaller changes in Oosaka and elsewhere

2022.06 Updates

31 May 12:57
Compare
Choose a tag to compare

posuto has been updated with the latest data from JP Post. There were very few changes this month.

  • 福岡県福岡市西区 implemented 住居表示 in a few areas
  • 宮崎県延岡市中の瀬町 had its reading corrected from ナカノセチョウ to ナカノセマチ

2022.05 Updates

02 May 11:07
Compare
Choose a tag to compare

posuto has been updated with the latest postal data. There were relatively few changes this time.

Some interesting changes:

  • One neighborhood in Fukui was corrected from 檜原 to 桧原
  • Also in Fukui, Tomiokamachi in Futaba-gun added a neighborhood simply called 駅前
  • In Osaka, the pronunciation of 三ケ山 was corrected from ミケヤマ to ミカヤマ

2022.03 Updates

01 Mar 05:36
Compare
Choose a tag to compare

This month's release includes the latest data from JP post and no functionality changes.

The main interesting change this month is that Nara changed ケ (large katakana ke) to ヶ (small katakana ke) in fifteen place names. Interestingly, after the change a roughly equal number of places use the large and small ke, so the change does not appear to have been arbitrary.

October Updates

01 Oct 03:55
Compare
Choose a tag to compare

This update includes the monthly updates for October. Notable changes this month:

  • The Hamamatsu World Trade Center postal codes were removed as the building enters demolition
  • Numazu City in Shizuoka re-organized several existing postal codes

There are no feature changes in this release.

September Updates: Calendar Versioning and More

31 Aug 11:34
Compare
Choose a tag to compare

Starting this month posuto uses Calendar Based versioning, so the latest release is v2021.9.0. The second component is the month; I wanted to use 09 but PyPI doesn't show leading zeroes so it'll just be like this. The final number is the release, it will be incremented if there's a bugfix or something.

Besides the versioning change there are no changes in functionality this month.

This month there were more updates than usual to normal postal codes.

  • The artificial island Choushuu Dejima got a postal code (7510840)
  • A danchi in Tsukuba got a new postal code (3002408)
  • A danchi in Kouchi Prefecture got a new postal code (7830097)
  • A number of postal codes in Yawata City in Kyoto with place names beginning with Matsui were removed (no news found) (6148292, 6148293, 6148291)
  • Something seems to have changed with the organization of some codes in Imizu City in Toyama, though this may be a diff artefact (9390332, 9390333)

Monthly Updates

06 Aug 14:15
Compare
Choose a tag to compare

posuto v0.4.5 with monthly updates has been released. The updates to the standard postal data were very small in number this month, mostly consisting of straightforward additions.

v0.4.4: Monthly Updates

02 Jul 07:33
Compare
Choose a tag to compare

A new version with the latest JP Post data has been released. There weren't that many changes this month, but there were a number of new codes added, including 希望が丘 in Sukumo City.

v0.4.1: Monthly Updates & Bugfix

04 Apr 14:17
Compare
Choose a tag to compare

This release includes monthly updates to the source files as well as a bugfix related to multithreaded environment handling (#9).

This month's updates included an unusual number of minor updates in Hokkaido.

Thanks to @yukota for the fix!

Adding support for Office Postal Codes

26 Feb 12:28
Compare
Choose a tag to compare

In addition to monthly updates this release adds support for 大口事業所の個別番号, or postal codes for high-volume office destinations.

While these codes look the same as other codes, the data associated with them is very different, and includes an explicity address and recipient name. You can access them with the same posuto.get you're familiar with, but the returned object may be an OfficeCode instead of a PostalCode, so be sure to check.

See #4 for further details on this feature.