This should allow Pull Requests to properly run all non-integration tests.
Squashed commit of the following:
commit a03e2a6592234e089d1fe9adc360b1e33a0c4b57
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 22:57:27 2015 -0700
Removing a dummy empty variable.
commit cd5964ab59
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 22:52:52 2015 -0700
Removing unused import.
commit 39b67b8562
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 22:52:35 2015 -0700
Use TestCase.skipTest.
commit 63d6dad73e
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 22:44:16 2015 -0700
Testing something out to make sure integration tests will fail.
commit 51f0cf44bf
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 22:38:50 2015 -0700
Adding unittest2 to requirements so we can skip tests on Python 2.6.
commit 3cc035f58b
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 21 20:56:04 2015 -0700
Try skipping integration tests if not all environment variables are available.
Squashed commit of the following:
commit 5bcbac33d6
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 23:05:15 2015 -0700
Add handling for situations in which the message was deleted in another thread before processing.
commit 6183f68b39
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 22:58:15 2015 -0700
Always store message as attachment if its content-disposition is marked as such.
commit 4c16494b1a
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 22:46:52 2015 -0700
Adding a (hopefully) failing test case for #52.
Testing the switch to uid-based IMAP calls required better testing
The better testing revealed some code that wasn't so pretty
I fixed the tests and the code
* Using a query parameter argument (rather than the entire query string)
to specify the folder into which e-mail messages should be archived.
* Duplicating the IMAP tests; this could probably be a bit more simply
done, but we'll at least be verifying both archived and non-archived
use cases.
* Simplifying some aspects of the documentation to include references
to this new feature.
* Since Django requires that the content stored in a TextField be unicode, we
need some way to encode the message safely. In situations before where
a single-byte non-7-bit-clean encoding were used, django-mailbox could
explode when writing the message copy to the database; this should ameliorate
that problem.
* Reverts earlier changesets' encoding normalization.
message copy in database.
Bumping version number to 2.1
* Walks through incoming message, write attachments to disk as they are found,
and alters message body removing actual attachment body, and adding
header 'X-Django-Mailbox-Interpolate-Attachment' referencing the ID of the
stored attachment.
* When calling ``get_email_object``, will walk through stored message, and
're-hydrate' the message by finding said headers, searching for the
appropriate record in the MessageAttachments table, and rebuild the message
object as closely as possible.
Minor fixes:
* Properly collect text/plain content from any part of the message; previously
would only check the message's first level of payloads, now walks through
all payloads, building a string of all text/plain content.
* Remove use of deprecated `assertEquals` message.
