Skip to content

Latest commit

 

History

History
102 lines (78 loc) · 4.56 KB

CHANGELOG.rst

File metadata and controls

102 lines (78 loc) · 4.56 KB
Raw

Changelog

The purpose of this document is to list all of the notable changes to this project. The format was inspired by Keep a Changelog. This project adheres to semantic versioning.

Release 4.0.3 (2020-03-27)

Bug fix for the following :exc:`~exceptions.TypeError` exception raised by the Telegram backend:

Traceback (most recent call last):
  File "../lib/python3.5/site-packages/chat_archive/cli.py", line 199, in main
    command_fn(arguments)
  File "../lib/python3.5/site-packages/chat_archive/cli.py", line 286, in sync_cmd
    self.synchronize(*arguments)
  File "../lib/python3.5/site-packages/chat_archive/__init__.py", line 335, in synchronize
    self.initialize_backend(backend_name, account_name).synchronize()
  File "../lib/python3.5/site-packages/chat_archive/backends/telegram.py", line 97, in synchronize
    event_loop.run_until_complete(self.connect_then_sync())
  File "/usr/lib/python3.5/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 294, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "../lib/python3.5/site-packages/chat_archive/backends/telegram.py", line 124, in connect_then_sync
    elif dialog.date > conversation_in_db.last_modified:
TypeError: can't compare offset-naive and offset-aware datetimes

Release 4.0.2 (2018-12-31)

  • Merged pull request #1: Automatically create archive directory when it doesn't exist yet.
  • Bumped hangups from 0.4.4 to 0.4.6 to improve Google Hangouts authentication compatibility.

Note

Hangups release 0.4.6 (the latest available) doesn't actually work for me, although I managed to get it to connect successfully after hacking in captcha support, which I've since submitted as pull request #446 🙂.

Release 4.0.1 (2018-08-02)

Just before publishing this project yesterday I propagated a rename throughout the code base, rephrasing "password" as "secret" (my rationale being that "naming things is important" 😇). Unfortunately that rename was propagated a bit more thoroughly than I had intended, impacting the interaction with the Hangups API. This should be fixed in release 4.0.1. For posterity, this relates to the following exception:

AttributeError: 'GoogleAccountCredentials' object has no attribute 'get_password'

Release 4.0 (2018-08-01)

The initial public release! 🎉

Because I love giving mixed signals I've decided to use the version number 4.0 for this release (because four chat service backends are supported) but I've added the "beta" trove classifier to the setup.py script and I've added a big fat disclaimer to the readme (see the status section) 😛.

While publishing the project I decided to be pragmatic and strip the version control history, because in the first weeks of development I hard coded quite a few secrets in the code base. Since then I've added support for configuration files and even ~/.password-store but of course those secrets remain in the history...

Now I could have spent hours pouring through tens of thousands of lines of patch output to remove those secrets without trashing the history. Instead I decided to do something more useful with my time, hence "pragmatic" above 😇.

PS. This is that "awesome new project" that I've been referring to in the humanfriendly changelog. Over the course of developing chat-archive I've moved more than six hundred lines of code to the humanfriendly package due to its general purpose nature (the HTML to ANSI conversion).