librelist archives

« back to archive

Feedback for new Flask extension

Feedback for new Flask extension

From:
David Baumgold
Date:
2012-11-04 @ 15:32
Hey all, I've just written my first Flask extension, and I'm looking for 
some feedback. I recently found the Misaka module [1], a set of Python 
bindings to the Sundown parser for Markdown (the same parser that Github 
uses). It looks awesome -- faster and more flexible than Python's 
`markdown` module -- and I expect that the only reason it isn't more 
widely used is that the API is not very Pythonic. 

So, I created Flask-Misaka [2], with the goal of making Misaka easier to 
integrate into Flask with a more Pythonic API. I've written the code, 
tests, and documentation; I've put the code on Github, published the docs 
on ReadTheDocs[3], integrated the tests with Travis CI [4], published the 
module on PyPI [5], and now that I've put myself out there, I'm soliciting
feedback. How does Flask-Misaka compare with Flask-Markdown? [6] Is there 
any way I can improve the API, docs, or tests? Once I'm sure that the 
project is the way I want it, I'll clean up the last few requirements [7] 
and submit it for an approved extension.

Thanks!
-David Baumgold

[1]: http://misaka.61924.nl/
[2]: https://github.com/singingwolfboy/flask-misaka
[2]: http://pypi.python.org/pypi/Flask-Misaka
[3]: https://flask-misaka.readthedocs.org/en/latest/
[5]: https://travis-ci.org/#!/singingwolfboy/flask-misaka
[6]: http://packages.python.org/Flask-Markdown/
[7]: http://flask.pocoo.org/docs/extensiondev/#approved-extensions

Re: [flask] Feedback for new Flask extension

From:
chrickso
Date:
2012-11-06 @ 02:13
i get this when following the docs:

File "/Users/chris/Dropbox/Repositories/tagxt/tagxtapp/extensions.py", line
38, in <module>
    from flask.ext.misaka import Misaka
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/exthook.py",
line 86, in load_module
    raise ImportError('No module named %s' % fullname)
ImportError: No module named flask.ext.misaka









On Sun, Nov 4, 2012 at 9:32 AM, David Baumgold <david@davidbaumgold.com>wrote:

> Hey all, I've just written my first Flask extension, and I'm looking for
> some feedback. I recently found the Misaka module [1], a set of Python
> bindings to the Sundown parser for Markdown (the same parser that Github
> uses). It looks awesome -- faster and more flexible than Python's
> `markdown` module -- and I expect that the only reason it isn't more widely
> used is that the API is not very Pythonic.
>
> So, I created Flask-Misaka [2], with the goal of making Misaka easier to
> integrate into Flask with a more Pythonic API. I've written the code,
> tests, and documentation; I've put the code on Github, published the docs
> on ReadTheDocs[3], integrated the tests with Travis CI [4], published the
> module on PyPI [5], and now that I've put myself out there, I'm soliciting
> feedback. How does Flask-Misaka compare with Flask-Markdown? [6] Is there
> any way I can improve the API, docs, or tests? Once I'm sure that the
> project is the way I want it, I'll clean up the last few requirements [7]
> and submit it for an approved extension.
>
> Thanks!
> -David Baumgold
>
> [1]: http://misaka.61924.nl/
> [2]: https://github.com/singingwolfboy/flask-misaka
> [2]: http://pypi.python.org/pypi/Flask-Misaka
> [3]: https://flask-misaka.readthedocs.org/en/latest/
> [5]: https://travis-ci.org/#!/singingwolfboy/flask-misaka
> [6]: http://packages.python.org/Flask-Markdown/
> [7]: http://flask.pocoo.org/docs/extensiondev/#approved-extensions
>
>

Re: [flask] Feedback for new Flask extension

From:
David Baumgold
Date:
2012-11-06 @ 02:54
Whoops -- looks like it was a packaging issue. I forgot to include a 
"py_modules" argument in setup.py, and as a result, when I ran `python 
setup.py sdist upload`, it didn't actually include my code! :( I've fixed 
that, as well as a number of other small issues with my setup.py, and I've
now uploaded version 0.1.1 to PyPI. Could you give it another try? (And 
thank you so much for testing!)
-David


On Monday, November 5, 2012 at 9:13 PM, chrickso wrote:

> i get this when following the docs:
> 
> File "/Users/chris/Dropbox/Repositories/tagxt/tagxtapp/extensions.py", 
line 38, in <module>
> from flask.ext.misaka import Misaka
> File 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/exthook.py",
line 86, in load_module
> raise ImportError('No module named %s' % fullname)
> ImportError: No module named flask.ext.misaka
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Sun, Nov 4, 2012 at 9:32 AM, David Baumgold <david@davidbaumgold.com 
(mailto:david@davidbaumgold.com)> wrote:
> > Hey all, I've just written my first Flask extension, and I'm looking 
for some feedback. I recently found the Misaka module [1], a set of Python
bindings to the Sundown parser for Markdown (the same parser that Github 
uses). It looks awesome -- faster and more flexible than Python's 
`markdown` module -- and I expect that the only reason it isn't more 
widely used is that the API is not very Pythonic.
> > 
> > So, I created Flask-Misaka [2], with the goal of making Misaka easier 
to integrate into Flask with a more Pythonic API. I've written the code, 
tests, and documentation; I've put the code on Github, published the docs 
on ReadTheDocs[3], integrated the tests with Travis CI [4], published the 
module on PyPI [5], and now that I've put myself out there, I'm soliciting
feedback. How does Flask-Misaka compare with Flask-Markdown? [6] Is there 
any way I can improve the API, docs, or tests? Once I'm sure that the 
project is the way I want it, I'll clean up the last few requirements [7] 
and submit it for an approved extension.
> > 
> > Thanks!
> > -David Baumgold
> > 
> > [1]: http://misaka.61924.nl/
> > [2]: https://github.com/singingwolfboy/flask-misaka
> > [2]: http://pypi.python.org/pypi/Flask-Misaka
> > [3]: https://flask-misaka.readthedocs.org/en/latest/
> > [5]: https://travis-ci.org/#!/singingwolfboy/flask-misaka
> > [6]: http://packages.python.org/Flask-Markdown/
> > [7]: http://flask.pocoo.org/docs/extensiondev/#approved-extensions
> 


Re: [flask] Feedback for new Flask extension

From:
chrickso
Date:
2012-11-06 @ 22:08
now i get

Traceback (most recent call last):
  File "shell.py", line 116, in <module>
    manager.run()
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
line 710, in run
    self.handle(sys.argv[0], command, sys.argv[2:])
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
line 682, in handle
    command.handle(app, *positional_args, **command_namespace.__dict__)
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
line 193, in handle
    self.run(*args, **kwargs)
  File "shell.py", line 31, in run
    app.run(host='0.0.0.0')
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/app.py",
line 739, in run
    run_simple(host, port, self, **options)
  File

"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/werkzeug/serving.py",
line 613, in run_simple
    test_socket.bind((hostname, port))
  File

"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py",
line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 48] Address already in use

On Mon, Nov 5, 2012 at 8:54 PM, David Baumgold <david@davidbaumgold.com>wrote:

> Whoops -- looks like it was a packaging issue. I forgot to include a
> "py_modules" argument in setup.py, and as a result, when I ran `python
> setup.py sdist upload`, it didn't actually include my code! :( I've fixed
> that, as well as a number of other small issues with my setup.py, and I've
> now uploaded version 0.1.1 to PyPI. Could you give it another try? (And
> thank you so much for testing!)
> -David
>
>
> On Monday, November 5, 2012 at 9:13 PM, chrickso wrote:
>
> > i get this when following the docs:
> >
> > File "/Users/chris/Dropbox/Repositories/tagxt/tagxtapp/extensions.py",
> line 38, in <module>
> > from flask.ext.misaka import Misaka
> > File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/exthook.py",
> line 86, in load_module
> > raise ImportError('No module named %s' % fullname)
> > ImportError: No module named flask.ext.misaka
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Sun, Nov 4, 2012 at 9:32 AM, David Baumgold 
<david@davidbaumgold.com(mailto:
> david@davidbaumgold.com)> wrote:
> > > Hey all, I've just written my first Flask extension, and I'm looking
> for some feedback. I recently found the Misaka module [1], a set of Python
> bindings to the Sundown parser for Markdown (the same parser that Github
> uses). It looks awesome -- faster and more flexible than Python's
> `markdown` module -- and I expect that the only reason it isn't more widely
> used is that the API is not very Pythonic.
> > >
> > > So, I created Flask-Misaka [2], with the goal of making Misaka easier
> to integrate into Flask with a more Pythonic API. I've written the code,
> tests, and documentation; I've put the code on Github, published the docs
> on ReadTheDocs[3], integrated the tests with Travis CI [4], published the
> module on PyPI [5], and now that I've put myself out there, I'm soliciting
> feedback. How does Flask-Misaka compare with Flask-Markdown? [6] Is there
> any way I can improve the API, docs, or tests? Once I'm sure that the
> project is the way I want it, I'll clean up the last few requirements [7]
> and submit it for an approved extension.
> > >
> > > Thanks!
> > > -David Baumgold
> > >
> > > [1]: http://misaka.61924.nl/
> > > [2]: https://github.com/singingwolfboy/flask-misaka
> > > [2]: http://pypi.python.org/pypi/Flask-Misaka
> > > [3]: https://flask-misaka.readthedocs.org/en/latest/
> > > [5]: https://travis-ci.org/#!/singingwolfboy/flask-misaka
> > > [6]: http://packages.python.org/Flask-Markdown/
> > > [7]: http://flask.pocoo.org/docs/extensiondev/#approved-extensions
> >
>
>
>
>

Re: [flask] Feedback for new Flask extension

From:
chrickso
Date:
2012-11-06 @ 22:09
lol whoops, didn't see i had another server running in another tab.

all good now, sorry

On Tue, Nov 6, 2012 at 4:08 PM, chrickso <chrickso@gmail.com> wrote:

> now i get
>
> Traceback (most recent call last):
>   File "shell.py", line 116, in <module>
>     manager.run()
>   File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
> line 710, in run
>     self.handle(sys.argv[0], command, sys.argv[2:])
>   File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
> line 682, in handle
>     command.handle(app, *positional_args, **command_namespace.__dict__)
>   File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flaskext/script.py",
> line 193, in handle
>     self.run(*args, **kwargs)
>   File "shell.py", line 31, in run
>     app.run(host='0.0.0.0')
>   File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/app.py",
> line 739, in run
>     run_simple(host, port, self, **options)
>   File
> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/werkzeug/serving.py",
> line 613, in run_simple
>     test_socket.bind((hostname, port))
>   File
> 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py",
> line 224, in meth
>     return getattr(self._sock,name)(*args)
> socket.error: [Errno 48] Address already in use
>
> On Mon, Nov 5, 2012 at 8:54 PM, David Baumgold <david@davidbaumgold.com>wrote:
>
>> Whoops -- looks like it was a packaging issue. I forgot to include a
>> "py_modules" argument in setup.py, and as a result, when I ran `python
>> setup.py sdist upload`, it didn't actually include my code! :( I've fixed
>> that, as well as a number of other small issues with my setup.py, and I've
>> now uploaded version 0.1.1 to PyPI. Could you give it another try? (And
>> thank you so much for testing!)
>> -David
>>
>>
>> On Monday, November 5, 2012 at 9:13 PM, chrickso wrote:
>>
>> > i get this when following the docs:
>> >
>> > File "/Users/chris/Dropbox/Repositories/tagxt/tagxtapp/extensions.py",
>> line 38, in <module>
>> > from flask.ext.misaka import Misaka
>> > File
>> 
"/Users/chris/Dropbox/Repositories/venvs/tagxt/lib/python2.7/site-packages/flask/exthook.py",
>> line 86, in load_module
>> > raise ImportError('No module named %s' % fullname)
>> > ImportError: No module named flask.ext.misaka
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Sun, Nov 4, 2012 at 9:32 AM, David Baumgold 
<david@davidbaumgold.com(mailto:
>> david@davidbaumgold.com)> wrote:
>> > > Hey all, I've just written my first Flask extension, and I'm looking
>> for some feedback. I recently found the Misaka module [1], a set of Python
>> bindings to the Sundown parser for Markdown (the same parser that Github
>> uses). It looks awesome -- faster and more flexible than Python's
>> `markdown` module -- and I expect that the only reason it isn't more widely
>> used is that the API is not very Pythonic.
>> > >
>> > > So, I created Flask-Misaka [2], with the goal of making Misaka easier
>> to integrate into Flask with a more Pythonic API. I've written the code,
>> tests, and documentation; I've put the code on Github, published the docs
>> on ReadTheDocs[3], integrated the tests with Travis CI [4], published the
>> module on PyPI [5], and now that I've put myself out there, I'm soliciting
>> feedback. How does Flask-Misaka compare with Flask-Markdown? [6] Is there
>> any way I can improve the API, docs, or tests? Once I'm sure that the
>> project is the way I want it, I'll clean up the last few requirements [7]
>> and submit it for an approved extension.
>> > >
>> > > Thanks!
>> > > -David Baumgold
>> > >
>> > > [1]: http://misaka.61924.nl/
>> > > [2]: https://github.com/singingwolfboy/flask-misaka
>> > > [2]: http://pypi.python.org/pypi/Flask-Misaka
>> > > [3]: https://flask-misaka.readthedocs.org/en/latest/
>> > > [5]: https://travis-ci.org/#!/singingwolfboy/flask-misaka
>> > > [6]: http://packages.python.org/Flask-Markdown/
>> > > [7]: http://flask.pocoo.org/docs/extensiondev/#approved-extensions
>> >
>>
>>
>>
>>
>