a1af97a51199d62c1b19639ae4affb8b73e242fa
[diaspy.git] / 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 #### Known issues
24
25 * __bug__: `diaspy` has problems/can't connect to pods using SNI (this is an issue with requests/urllib3/python),
26
27
28 ----
29
30 #### Version `0.4.1` (2013-09-):
31
32 * __new__: `diaspy.people.User._fetchstream()` method,
33
34
35 ----
36
37 #### Version `0.4.1` (2013-09-12):
38
39 Login and authentication procedure backend received major changes in this version.
40 There are no longer `username` and `password` variables in `Connection` object.
41 Instead, credentials are stored (together with the token) in single variable `_login_data`.
42 This is preserved until you call `login()` at which point credentials are erased and
43 only token is left -- it can be obtained by calling `repr(Connection)`.
44
45 Also, this release is compatible with DIASPORA\* 0.2.0.0 but should still support
46 pods running on older versions.
47
48 And the test suite was updated. Yay!
49
50
51 * __new__: `diaspy.errors.SettingsError`.
52
53
54 * __upd__: `diaspy.settings.Account.setEmail()` can now raise `SettingsError` when request fails,
55 * __upd__: `diaspy.settings.Account.getEmail()` will now return empty string instead of raising an exception if cannot fetch mail,
56 * __upd__: improved language fetching in `diaspy.settings.Account.getLanguages()`.
57
58
59 * __rem__: `diaspy/client.py` is removed,
60
61
62 **`0.4.1-rc.3` (2013-09-08):**
63
64 * __new__: `diaspy.settings.Profile.load()` method for loading profile information,
65 * __new__: `diaspy.settings.Profile.update()` method for updating profile information,
66 * __new__: `diaspy.settings.Profile.setName()` method,
67 * __new__: `diaspy.settings.Profile.setBio()` method,
68 * __new__: `diaspy.settings.Profile.setLocation()` method,
69 * __new__: `diaspy.settings.Profile.setTags()` method,
70 * __new__: `diaspy.settings.Profile.setGender()` method,
71 * __new__: `diaspy.settings.Profile.setBirthDate()` method,
72 * __new__: `diaspy.settings.Profile.setSearchable()` method,
73 * __new__: `diaspy.settings.Profile.setNSFW()` method,
74
75
76 **`0.4.1-rc.2` (2013-09-06):**
77
78 * __new__: `diaspy.search.Search.tags()` method for getting tag suggestions,
79 * __new__: `diaspy.settings.Profile.getName()` method,
80 * __new__: `diaspy.settings.Profile.getBio()` method,
81 * __new__: `diaspy.settings.Profile.getLocation()` method,
82 * __new__: `diaspy.settings.Profile.getTags()` method,
83 * __new__: `diaspy.settings.Profile.getGender()` method,
84 * __new__: `diaspy.settings.Profile.getBirthDate()` method,
85 * __new__: `diaspy.settings.Profile.isSearchable()` method,
86 * __new__: `diaspy.settings.Profile.isNSFW()` method,
87 * __new__: `provider_display_name` parameter in `diaspy.streams.Stream.post()` (thanks @svbergerem),
88
89
90 * __upd__: `remeber_me` parameter in `diaspy.connection.Connection.login()`,
91 * __upd__: you must supply `username` and `password` parameters on init of `diaspy.connection.Connection`,
92 * __upd__: you must update your testconf.py (new fields are required for settings tests),
93 * __upd__: `diaspy.settings.Settings` renamed to `diaspy.settings.Account`,
94
95
96 * __rem__: `username` and `password` parameters removed from `diaspy.connection.Connection.login()`
97 must be supplied on init,
98
99
100 **`0.4.1-rc.1` (2013-09-02):**
101
102 * __new__: `__getitem__()` in `diaspy.models.Post`,
103 * __new__: `__dict__()` in `diaspy.models.Post`,
104 * __new__: `guid` argument in `diaspy.models.Post.__init__()`,
105 * __new__: `json()` method in `diaspy.streams.Generic` adds the possibility to export streams to JSON,
106 * __new__: `full()` method in `diaspy.streams.Generic` will try to fetch full stream (containing all posts),
107 * __new__: `setEmail()` method in `diaspy.settings.Settings`,
108 * __new__: `setLanguage()` method in `diaspy.settings.Settings`,
109 * __new__: `downloadPhotos()` method in `diaspy.settings.Settings`,
110 * __new__: `backtime` argument in `more()` method in `diaspy.streams.Generic`,
111 * __new__: `DiaspyError` will be raised when connection is created with empty password and/or username,
112 * __new__: `getSessionToken()` method in `diaspy.connection.Connection` returns string from `_diaspora_session` cookie,
113 * __new__: `direct` parameter in `diaspy.connection.Connection().get()` allowing to disable pod expansion,
114
115
116 * __upd__: if `Post()` is created with fetched comments, data will also be fetched as a dependency,
117 * __upd__: `id` argument type is now `int` (`diaspy.models.Post.__init__()`),
118 * __upd__: `Search().lookup_user()` renamed to `Search().lookupUser()`,
119 * __upd__: `diaspy.messages` renamed to `diaspy.conversations` (but will be accessible under both names for this and next release),
120 * __upd__: `LoginError` moved to `diaspy.errors`,
121 * __upd__: `TokenError` moved to `diaspy.errors`,
122 * __upd__: `diaspy.connection.Connection.podswitch()` gained two new positional arguments: `username` and `password`,
123 * __upd__: `aspect_id` renamed to `id` in `diaspy.streams.Aspects().remove()`,
124
125
126 * __fix__: fixed some bugs in regular expressions used by `diaspy` internals (html tag removal, so you get nicer notifications),
127 * __fix__: fixed authentication issues,
128
129
130 ----
131
132 #### Version `0.4.0` (2013-08-20):
133
134 This release is **not backwards compatible with `0.3.x` line**! You'll have to check your code for corrections.
135 Also, this release if first to officially released fork version.
136
137 * __dep__: `diaspy.client` is officially deprecated (will be removed in `0.4.1`),
138
139
140 * __upd__: `diaspy.conversations` renamed to `diaspy.messages`,
141 * __udp__: `diaspy.conversations.Conversation` moved to `diaspy.models`,
142
143
144 * __new__: `diaspy.messages.Mailbox()` object representing diaspora\* mailbox,
145
146 ----
147
148 #### Version `0.3.2` (2013-08-20):
149
150 * __upd__: `diaspy.connection.getUserData()` raises `DiaspyError` when it cannot find user data,
151
152
153 * __rem__: `diaspy.client.Client` must be explicitly imported,
154
155 ----
156
157 #### Version `0.3.1` (2013-07-12):
158
159 * __upd__: `diaspy.people.sephandle()` raises `InvalidHandleError` instead of `UserError`
160 * __upd__: `models.Post()._fetch()` renamed to `_fetchdata()` (because of new `_fetchcomments()` method)
161
162
163 * __new__: `models.Comment()` object: wrapper for comments, not to be created manually
164 * __new__: `comments` parameter in `models.Post`: defines whether to fetch post's commets
165 * __new__: `connection.Connection` has new parameter in `__init__()`: it's `schema`
166 * __new__: `author()` method in `models.Post()`
167
168
169 The new parameter in `connection.Connection` is useful when operating with handles.
170 As handle does not contain schema (`http`, `https`, etc.) `_setlogin()` would raise an
171 unhandled exception -- `requests.exceptions.MissingSchema`.
172 Now, however, `Connection` will catch the exception, add missing schema and try once more.
173 This parameter is provided to give programmers ability to manipulate it.
174
175 Also, now you can pass just `pod.example.com` as `pod` parameter. Less typing!
176
177 When it comes to posts, we are now able to fetch comments.
178
179 ----
180
181 #### Version `0.3.0` (2013-07-07):
182
183 First edition of Changelog for `diaspy`.
184 Developers should update their code as version `0.3.0` may not be fully
185 backwards compatible depending on how the code is written.
186 If you always pass named arguments and do not rely on their order you can, at least in
187 theory, not worry about this update.
188
189 Version `0.3.0` introduces few new features, fixes several bugs and brings a bit of
190 redesign and refactoring od `diaspy`'s code.
191
192