summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_quopri.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-40280: Skip subprocess-based tests on wasm32-emscripten (GH-30615)Christian Heimes2022-01-251-0/+3
|
* Issue #23277: Remove unused sys and os importsBerker Peksag2016-04-241-1/+1
| | | | Patch by Jon Dufresne.
* Issue #21741: Update 147 test modules to use test discovery.Zachary Ware2015-04-131-6/+1
| | | | | | | I have compared output between pre- and post-patch runs of these tests to make sure there's nothing missing and nothing broken, on both Windows and Linux. The only differences I found were actually tests that were previously *not* run.
* Unittest for Issue 21511 by Christie Wilson bobcatfish@gmail.com.Guido van Rossum2015-04-111-0/+7
|
* Fix ResourceWarning from subprocess pipes being left open.Brian Curtin2010-11-051-0/+2
|
* #2621 rename test.test_support to test.supportBenjamin Peterson2008-05-201-2/+2
|
* Use BytesIO instead of cStringIO.StringIO.Martin v. Löwis2007-07-281-5/+5
|
* Fix quopri to operate consistently on bytes.Martin v. Löwis2007-07-281-29/+36
|
* Patch by Christian Heimes to change self.assert_(x == y) intoGuido van Rossum2007-07-111-8/+8
| | | | | self.assertEqual(x, y). (Christian used self.failUnlessEqual(), but the double negative makes it hard to grok, so I changed it.)
* Merge p3yk branch with the trunk up to revision 45595. This breaks a fairThomas Wouters2006-04-211-9/+12
| | | | | | | | | | | | | | | | | | | | number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
* Whitespace normalization.Tim Peters2005-12-251-10/+10
|
* Add two tests for the script interface.Walter Dörwald2005-12-151-5/+19
|
* If quopri uses the implementations from binascii do the tests a second timeWalter Dörwald2005-12-141-10/+35
| | | | | using the Python implementations of the functions. This imcreases code coverage and makes sure that both implementations do the same thing.
* Get rid of relative imports in all unittests. Now anything thatBarry Warsaw2002-07-231-1/+1
| | | | | | | | | | | imports e.g. test_support must do so using an absolute package name such as "import test.test_support" or "from test import test_support". This also updates the README in Lib/test, and gets rid of the duplicate data dirctory in Lib/test/data (replaced by Lib/email/test/data). Now Tim and Jack can have at it. :)
* Patch #462190, patch #464070: Support quoted printable in the binascii module.Martin v. Löwis2001-09-301-0/+13
| | | | Decode and encode underscores for header style encoding. Fixes bug #463996.
* Change the PyUnit-based tests to use the test_main() approach. ThisFred Drake2001-09-201-1/+6
| | | | | allows using the tests with unittest.py as a script. The tests will still run when run as a script themselves.
* Don't use any characters C doesn't guarantee are safe for text-mode files.Tim Peters2001-08-031-12/+12
| | | | This should stop the bizarre translations Jack was getting from Mac CVS.
* Whitespace normalization, plus:Tim Peters2001-07-211-8/+8
| | | | | | + test_quopri.py relied on significant trailing spaces. Fixed. + test_dircache.py (still) doesn't work on Windows (directory mtime on Windows doesn't work like it does on Unix).
* Add a bunch of sample strings to test soft line breaks of varying endBarry Warsaw2001-06-191-1/+28
| | | | cases.
* A unittest-based test for the quopri module.Barry Warsaw2001-06-191-0/+112