aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Cleaned up commandline script. Everything is in module now.Waylan Limberg2011-08-032-10/+2
|
* Markdown.convertFile now actually works with stdin and stdout. Previously ↵Waylan Limberg2011-08-032-5/+9
| | | | only the commandline script did.
* rename command 'fab do_release' -> 'fad deploy_release'Waylan Limberg2011-08-031-1/+1
|
* Updated fabfile to automate deploying a release. Includes building a release ↵Waylan Limberg2011-08-031-2/+81
| | | | distribution, registering it with PyPI and uploading donwloads to PyPI and Github.
* Added doctests to fabfile and edited them to pass in all supported versions ↵Waylan Limberg2011-08-028-58/+67
| | | | of python. Note: one test (meta) is still failing on Python 3 due to unicode strings.
* Edited release notes. Made a few minor corrections and added a note ↵Waylan Limberg2011-07-281-7/+15
| | | | regarding supported python versions. No more support for Python 2.3 with 2.4 support depreciated. We now support Python 3.2.
* TestCase.assert_ and TestCase.failUnless are depreciated in Python 3 in ↵Waylan Limberg2011-07-281-3/+3
| | | | favor of testCase.assertTrue. Might as well be using the right method in our tests.
* Fix a minor Python 3 incompatability in the headerid extension's slugify ↵Waylan Limberg2011-07-281-1/+1
| | | | function. The url is being encoded (with errors ignored) as an easy means of removing non-ascii chars, but we have to re-encode it *before* running the regex on it, not after.
* Skip the UnidoceDecodeError API test in Python 3.x as all input should be ↵Waylan Limberg2011-07-281-2/+3
| | | | unicode anyway.
* Python 3.2 made some changes to the configparser which broke the testing ↵Waylan Limberg2011-07-282-5/+5
| | | | framework. With a simple addition to our subclass (which we then make use of), this is an easy fix.
* Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵Waylan Limberg2011-07-282-2/+2
| | | | positional arguments back then.
* All internal encoding of output now uses the 'xmlcharrefreplace' error ↵Waylan Limberg2011-07-283-6/+13
| | | | handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
* All API tests now utilize our own searializers.Waylan Limberg2011-07-271-3/+5
|
* Stripped out encoding/decoding in the searializers.Waylan Limberg2011-07-272-48/+38
| | | | | | | | | | | | | | | | | | | | | | | Those extra steps always bothered me as being unnecessary. Additionally, this should make conversion to Python 3 easier. The 2to3 tool wasn't converting the searializers properly and we were getting byte strings in the output. Previously, this wasn't a major problem because the default searializer was the xml searializer provided in the ElementTree standard lib. However, now that we are using our own xhtml searializer, it must work smoothly in all supported versions. As a side note, I believe the thought was that we needed to do the encoding to take advantage of the "xmlcharrefreplace" error handling. However, using the example in the python [docs](http://docs.python.org/howto/unicode.html#the-unicode-type): >>> u = unichr(40960) + u'abcd' + unichr(1972) >>> u.encode('utf-8', 'xmlcharrefreplace').decode('utf-8') == u True There's no point of using the "xmlcharrefreplace" error handling if we just convert back to the original Unicode anyway. Interestingly, the Python 3 standard lib is doing essentially what we are doing here, so I'm convinced this is the right way to go.
* Fix syntax error in doctests which tripped up the 2to3 tool.Waylan Limberg2011-07-241-6/+6
|
* Added fabfile as a script to automate various common mainentance tasks. ↵Waylan Limberg2011-07-241-0/+68
| | | | Currently only automates testing (makes 2to3 testing easier). More featurs to come.
* Fixed a few minor Python2.4 incompatabilities. Runs in 2.4-2.7 cleanly.Waylan Limberg2011-07-222-2/+8
|
* Fixed the bug exposed in 8761cd1780a7cec60123. We no longer should get empty ↵Waylan Limberg2011-07-211-2/+3
| | | | rawhtml blocks. All tests pass again.
* Fixed #31. Headers in tight lists now get inline patterns run on their ↵Waylan Limberg2011-07-213-5/+16
| | | | tails. Tests included.
* Updated toc extension's anchorlink option to work properly with recent refactor.Waylan Limberg2011-07-141-2/+6
|
* Refactored the toc extension. Fixes #33: The [TOC] marker is now ignored in ↵Waylan Limberg2011-07-141-28/+17
| | | | code blocks/spans. A better fix for #4: Only the *text* from the header is caried over to the toc (without *any* inline formatting). Also refactored the extension to better work in tandem with the refactored headerid extension and the new attr_list extension.
* Fixed #34. Better support for unicode text with the html_tidy extension. ↵Waylan Limberg2011-07-141-2/+5
| | | | Force input and output of tidy to use UTF-8 and encode before and decode after passing in the text.
* Updated release notes for recent changes to headerid extension.Waylan Limberg2011-06-301-0/+6
|
* Refactored HeaderId extension to no longer include defining ids. It only ↵Waylan Limberg2011-06-304-126/+126
| | | | autogenerates ids. If you want to define your own, use the attr_list extension. Also expanded HeaderId extension to use the same algorithm as the TOC extension (which is better) for slugifying the header text. Added config settings to override the default word separator and the slugify callable. Closes #16 as the reported bug is for a removed feature.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-293-7/+69
| | | | Thanks to skurfer for report and inital patch.
* Fixed #28. Inline raw html is now enclosed in p tags. This used to work. ↵Waylan Limberg2011-06-284-3/+16
| | | | Somehow we stopped checking for a single inline html element when swapping back in raw html. Added a test. Also patched a weird (invalid) comment test. Seeing the input is not really a valid html comment - it doesn't matter what we do with it. I suppose we test it to make sure it doesn't break the parser. Actual output is not so important. As a side note, this has exposed a preexisting (unrelated) bug with the extra extension's handling of raw html. That test is failing following this fix.
* Merge pull request #27 from teepark/stdin-encodingWaylan Limberg2011-06-271-1/+1
|\ | | | | also respect encoding when reading from a user-provided file
| * also respect encoding when reading from a user-provided fileTravis Parker2011-06-251-1/+1
|/
* Added first draft of 2.1.0-Alpha release notes.Waylan Limberg2011-06-231-0/+97
|
* Added html5 and xhtml5 output formats. These are just aliases to html4 and ↵Waylan Limberg2011-06-232-2/+8
| | | | xhtml1 searializers respectively.
* Added test for escaping chars in link urls. Closes #14 which was fixed in ↵Waylan Limberg2011-06-232-0/+10
| | | | previous commits. This addes the missing tests.
* Cleaned up backward compatability of old positional arguments. Some people ↵Waylan Limberg2011-06-232-20/+53
| | | | may be using them, so we should continue to support them. Also adjusted docs to encourage using keyword args only. However, if existing code was using positional args in previous versions, it should still work.
* Added nl2br extension. Closes #13. Thanks to Brian Neal for writing the code ↵Waylan Limberg2011-06-213-17/+56
| | | | and allowing us to use it.
* Fixed a few failing API tests. ElementTree is only available from ↵Waylan Limberg2011-06-211-5/+5
| | | | markdown.util.etree not markdown.etree. This may be a backward incompatable change for some extensions.
* Cleaned up markdown namespace. This may be a backward incompatible change ↵Waylan Limberg2011-06-201-5/+2
| | | | for some extensions. They should be importing from markdown.util
* Made the searializer wrapping code a little more dry and more clearly ↵Waylan Limberg2011-06-201-20/+10
| | | | defined the public methods.
* Updated searializers to handle boolean attributes. html gets the value only ↵Waylan Limberg2011-06-201-2/+5
| | | | and xhtml gets the key=value pair. We didn't need this prior to adding the attr_list ext.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2011-06-203-4/+24
|\
| * Minor Doc update. Fixed a typo in previous commit.Waylan Limberg2011-06-201-1/+1
| |
| * Merge pull request #25 from skurfer/noGuessingWaylan Limberg2011-06-193-4/+24
| |\ | | | | | | allow language guessing to be disabled by passing a setting to CodeHilite - closes #24
| | * allow language guessing to be disabled by passing a setting to CodeHilite - ↵Rob McBroom2011-06-193-4/+24
| |/ | | | | | | closes #24
* / Added docs and tests to attr_list ext. Closes #7.Waylan Limberg2011-06-204-0/+129
|/
* Added attribute list extension inspired by Maruku's attribute list feature. ↵Waylan Limberg2011-06-171-0/+122
| | | | See issue #7. Also likely to become a replacement for the headerid extension (with a little more work - need a forceid option) which means it will also address issue #16. The extension works with some limited testing. Still needs tests and documentation. Currently breaks toc extension - which should run after attr_list, not before.
* Added our own xhtml searializer. We no longer use a xml searializer to ↵Waylan Limberg2011-06-166-37/+52
| | | | output xhtml. This fixes #9 among other bugs. The test suite even had bad tests that should have been failing. They also have been corrected.
* Fixed #22. Horizontal rules now work in a few more crazy edge cases. Who ↵Waylan Limberg2011-06-161-1/+1
| | | | actualy useses these? Anyway, we now match markdown.pl.
* Fixed #23. Turns out markdown.pl only allows up to one space between ↵Waylan Limberg2011-06-161-2/+2
| | | | brackets in reference links. Now we do as well.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2011-06-151-2/+2
|\
| * A few minor tweaks to the smart_strong extension. Thanks to David Chambers ↵Waylan Limberg2011-06-131-2/+2
| | | | | | | | for pointing out the typo.
* | Fixed #21. A header and paragraph not seperated by a blank line inside a ↵Waylan Limberg2011-06-153-4/+61
|/ | | | list item are now parsed correctly. One of those crazy wierd edge cases that no one would ever test for, but is obvious once you see it.
* Added smart_strong extension. Fixes Issue #17. Like PHP Markdown Extra, we ↵Waylan Limberg2011-06-074-1/+78
| | | | now include smart handling of double underscores (not just single underscores). The new behavior may be called seperately as the 'smart_strong' extension or as part of the 'extra' extension.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 11:52:50 +0000