Changelog.markdown

   1 ## Changelog for `diaspy`, unofficial DIASPORA\* interface for Python
   2
   3 This changelog file follows few rules:
   4
   5 *   __rem__:    indicates removed features,
   6 *   __new__:    indicates new features,
   7 *   __upd__:    indicates updated features,
   8 *   __dep__:    indicates deprecated features,
   9
  10 Deprecation means that in the next version feature will be removed.
  11
  12 Also, after every version there should be a brief note describing possible
  13 problems with migrating to it from older versions and usage of new features.
  14
  15 Users can always read the manual and dcumentation to make themselves more knowledgeable and
  16 are encouraged to do so. They only need to remember that documentation is usually more
  17 up-to-date than manual and if conflicts appear they should follow the order:
  18
  19 *docstrings* -> *docs/* -> *manual/*
  20
  21
  22 ----
  23
  24 #### Version `0.4.1` (2013-09-):
  25
  26 Login and authentication procedure backend received major changes in this version.
  27 There are no longer `username` and `password` variables in `Connection` object.
  28 Instead, credentials are stored (together with the token) in single variable `_login_data`.
  29 This is preserved until you call `login()` at which point credentials are erased and
  30 only token is left -- it can be obtained by calling `repr(Connection)`.
  31
  32 Also, this release is compatible with DIASPORA\* 0.2.0.0 but should still support
  33 pods running on older versions.
  34
  35 And the test suite was updated. Yay!
  36
  37 **`0.4.1-rc.2` (2013-09-06):**
  38
  39 * __new__:  `diaspy.search.Search.tags()` method for getting tag suggestions,
  40
  41 * __upd__:  `remeber_me` parameter in `diaspy.connection.Connection.login()`,
  42 * __upd__:  you must supply `username` and `password` parameters on init of `diaspy.connection.Connection`,
  43
  44 * __rem__:  `username` and `password` parameters removed from `diaspy.connection.Connection.login()`
  45             must be supplied on init,
  46
  47
  48 **`0.4.1-rc.1` (2013-09-02):**
  49
  50 * __new__:  `__getitem__()` in `diaspy.models.Post`,
  51 * __new__:  `__dict__()` in `diaspy.models.Post`,
  52 * __new__:  `guid` argument in `diaspy.models.Post.__init__()`,
  53 * __new__:  `json()` method in `diaspy.streams.Generic` adds the possibility to export streams to JSON,
  54 * __new__:  `full()` method in `diaspy.streams.Generic` will try to fetch full stream (containing all posts),
  55 * __new__:  `setEmail()` method in `diaspy.settings.Settings`,
  56 * __new__:  `setLanguage()` method in `diaspy.settings.Settings`,
  57 * __new__:  `downloadPhotos()` method in `diaspy.settings.Settings`,
  58 * __new__:  `backtime` argument in `more()` method in `diaspy.streams.Generic`,
  59 * __new__:  `DiaspyError` will be raised when connection is created with empty password and/or username,
  60 * __new__:  `getSessionToken()` method in `diaspy.connection.Connection` returns string from `_diaspora_session` cookie,
  61 * __new__:  `direct` parameter in `diaspy.connection.Connection().get()` allowing to disable pod expansion,
  62
  63 * __upd__:  if `Post()` is created with fetched comments, data will also be fetched as a dependency,
  64 * __upd__:  `id` argument type is now `int` (`diaspy.models.Post.__init__()`),
  65 * __upd__:  `Search().lookup_user()` renamed to `Search().lookupUser()`,
  66 * __upd__:  `diaspy.messages` renamed to `diaspy.conversations` (but will be accessible under both names for this and next release),
  67 * __upd__:  `LoginError` moved to `diaspy.errors`,
  68 * __upd__:  `TokenError` moved to `diaspy.errors`,
  69 * __upd__:  `diaspy.connection.Connection.podswitch()` gained two new positional arguments: `username` and `password`,
  70 * __upd__:  `aspect_id` renamed to `id` in `diaspy.streams.Aspects().remove()`,
  71
  72 * __fix__:  fixed some bugs in regular expressions used by `diaspy` internals
  73             (html tag removal, so you get nicer notifications),
  74 * __fix__:  fixed authentication issues,
  75
  76
  77 ----
  78
  79 #### Version `0.4.0` (2013-08-20):
  80
  81 This release is **not backwards compatible with `0.3.x` line**! You'll have to check your code for corrections.
  82 Also, this release if first to officially released fork version.
  83
  84 * __dep__:  `diaspy.client` is officially deprecated (will be removed in `0.4.1`),
  85
  86 * __upd__:  `diaspy.conversations` renamed to `diaspy.messages`,
  87 * __udp__:  `diaspy.conversations.Conversation` moved to `diaspy.models`,
  88
  89 * __new__:  `diaspy.messages.Mailbox()` object representing diaspora\* mailbox,
  90
  91 ----
  92
  93 Version `0.3.2` (2013-08-20):
  94
  95 * __upd__:  `diaspy.connection.getUserData()` raises `DiaspyError` when it cannot find user data,
  96
  97 * __rem__:  `diaspy.client.Client` must be explicitly imported,
  98
  99 ----
 100
 101 Version `0.3.1` (2013-07-12):
 102
 103 * __upd__:  `diaspy.people.sephandle()` raises `InvalidHandleError` instead of `UserError`
 104 * __upd__:  `models.Post()._fetch()` renamed to `_fetchdata()` (because of new `_fetchcomments()` method)
 105 * __new__:  `models.Comment()` object: wrapper for comments, not to be created manually
 106 * __new__:  `comments` parameter in `models.Post`: defines whether to fetch post's commets
 107 * __new__:  `connection.Connection` has new parameter in `__init__()`: it's `schema`
 108 * __new__:  `author()` method in `models.Post()`
 109
 110
 111 The new parameter in `connection.Connection` is useful when operating with handles.
 112 As handle does not contain schema (`http`, `https`, etc.) `_setlogin()` would raise an
 113 unhandled exception -- `requests.exceptions.MissingSchema`.
 114 Now, however, `Connection` will catch the exception, add missing schema and try once more.
 115 This parameter is provided to give programmers ability to manipulate it.
 116
 117 Also, now you can pass just `pod.example.com` as `pod` parameter. Less typing!
 118
 119 When it comes to posts, we are now able to fetch comments.
 120
 121 ----
 122
 123 Version `0.3.0` (2013-07-07):
 124
 125 First edition of Changelog for `diaspy`.
 126 Developers should update their code as version `0.3.0` may not be fully
 127 backwards compatible depending on how the code is written.
 128 If you always pass named arguments and do not rely on their order you can, at least in
 129 theory, not worry about this update.
 130
 131 Version `0.3.0` introduces few new features, fixes several bugs and brings a bit of
 132 redesign and refactoring od `diaspy`'s code.
 133
 134 ----