Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
"
Additionally, the encoding argument has been removed from both
markdown and Markdown. Markdown expects unicode (or ascii) input and
it is the users responsibility to ensure that's what is provided.
"
The current dja
On Tue, May 6, 2008 at 6:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
>
> "
> Additionally, the encoding argument has been removed from both
> markdown and Markdown. Markdown expects unicode (or ascii) input and
On Tue, May 6, 2008 at 7:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
>
> I think there should be a branch checking the markdown version, and
> passing in a unicode object if markdown.version_info >= (1,7,0,'').
Um, what about lines 71-74 [1] does not do this? Yeah the check is the
other w
On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 7:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >
> >
>
> > I think there should be a branch checking the markdown version, and
> > passing in a unicode object if markdown.version_info >=
On Tue, May 6, 2008 at 10:45 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> >
> > Yeah, we probably should mention this in the docs, along with an
> > explanation of how to enable Markdown's safe_mode. Sure, it's
>
