Skip to content

Releases: jwodder/javaproperties

v0.8.2 — Packaging updates

01 Dec 12:48
v0.8.2
Compare
Choose a tag to compare
  • Drop support for Python 3.6 and 3.7
  • Support Python 3.11, 3.12, and 3.13
  • Migrated from setuptools to hatch

v0.8.1 — Typing bugfix

05 Oct 20:40
v0.8.1
Compare
Choose a tag to compare
  • Fix a typing issue in Python 3.9
  • Support Python 3.10

v0.8.0 — Type annotations; drop pre-Python 3.6

28 Nov 20:27
v0.8.0
Compare
Choose a tag to compare
  • Drop support for Python 2.7, 3.4, and 3.5
  • Support Python 3.9
  • ensure_ascii parameter added to PropertiesFile.dump() and PropertiesFile.dumps()
  • Bugfix: When parsing XML input, empty <entry> tags now produce an empty string as a value, not None
  • Added type annotations
  • Properties and PropertiesFile no longer raise TypeError when given a non-string key or value, as type correctness is now expected to be enforced through static type checking
  • The PropertiesElement classes returned by parse() are no longer subclasses of namedtuple, but they can still be iterated over to retrieve their fields like a tuple

v0.7.0 — `parse()` objects and `PropertiesFile` properties

09 Mar 18:52
v0.7.0
Compare
Choose a tag to compare
  • parse() now accepts strings as input
  • Breaking: parse() now returns a generator of custom objects instead of triples of strings
  • Gave PropertiesFile a settable timestamp property
  • Gave PropertiesFile a settable header_comment property
  • Handle unescaping surrogate pairs on narrow Python builds

v0.6.0 — `ensure_ascii`

28 Feb 15:57
v0.6.0
Compare
Choose a tag to compare
  • Include changelog in the Read the Docs site
  • Support Python 3.8
  • When dumping a value that begins with more than one space, only escape the first space in order to better match Java's behavior
  • Gave dump(), dumps(), escape(), and join_key_value() an ensure_ascii parameter for optionally not escaping non-ASCII characters in output
  • Gave dump() and dumps() an ensure_ascii_comments parameter for controlling what characters in the comments parameter are escaped
  • Gave to_comment() an ensure_ascii parameter for controlling what characters are escaped
  • Added a custom encoding error handler 'javapropertiesreplace' that encodes invalid characters as \uXXXX escape sequences

v0.5.2 — Fix build

08 Apr 14:12
v0.5.2
Compare
Choose a tag to compare
  • Added an example of each format to the format descriptions in the docs
  • Fix building in non-UTF-8 environments

v0.5.1 — Support datetime.fold

25 Oct 19:54
v0.5.1
Compare
Choose a tag to compare
  • Bugfix: java_timestamp() now properly handles naïve datetime objects with fold=1
  • Include installation instructions, examples, and GitHub links in the Read the Docs site

v0.5.0 — Error on invalid \uXXXX escapes

18 Sep 19:29
v0.5.0
Compare
Choose a tag to compare
  • Breaking: Invalid \uXXXX escape sequences now cause an InvalidUEscapeError to be raised
  • Properties instances can now compare equal to dicts and other mapping types
  • Gave Properties a copy method
  • Drop support for Python 2.6 and 3.3
  • Fixed a DeprecationWarning in Python 3.7

v0.4.0 — Moved CLI to separate package

22 Apr 19:37
v0.4.0
Compare
Choose a tag to compare

Split off the command-line programs into a separate package, javaproperties-cli

v0.3.0 — Class for preserving comments

13 Apr 20:16
v0.3.0
Compare
Choose a tag to compare
  • Added the PropertiesFile class for preserving comments in files [#1]
  • The ordereddict package is now required under Python 2.6