Floris Bruynooghe 69f1497986 Make dc_get_info() work on a closed context ...

There is very little API guarantees about this, but clients seem to
expect *something* to work on a closed context.  So split this up into
static info an more dynamic context-related info, but let's not
provide any guarantees about what keys are available when.

Fixes #599

2019-09-26 14:22:03 +02:00

..

data

feat: bring back and adapt python bindings with rust core

2019-05-30 23:17:38 +02:00

auditwheels.py

feat: bring back and adapt python bindings with rust core

2019-05-30 23:17:38 +02:00

conftest.py

as discussed during camp and otherwise ... add dc_perform_{mvbox,sentbox}_jobs hooks which, however, for now have an empty implementation. They can already be called from UIs, though. Next step is refactoring imap-job handling to only execute jobs belonging to the respective imap folder.

2019-09-20 01:03:25 +02:00

package_wheels.py

try using setuptools_scm for automatic versioning based on py-* tags (#187)

2019-07-14 09:58:51 +02:00

test_account.py

rustifying dc_continue_key_transfer and fix master-conflict

2019-09-25 23:46:44 +02:00

test_increation.py

improve python caching (#468)

2019-09-19 13:10:19 +02:00

test_lowlevel.py

Make dc_get_info() work on a closed context

2019-09-26 14:22:03 +02:00

test_provider_info.py

Add provider info functions to the FFI API

2019-09-19 07:17:44 +02:00