explore-flask
explore-flask copied to clipboard
content suggestion - add flask-testing extension
Are you thinking that we should have a testing chapter or mix this in somewhere else? I'm definitely interested in having information on testing, but to be frank I don't know anything about testing in Flask. It was one of the things that got cut out of my research plan.
New chapter. I can write it, with hopefully someone else doing code review.
Sounds good to me, but I should warn you that I'm going to be brutal with comments on the text itself. I'm not afraid to disagree. :)
I know. As long as you can help make suggestions rather than just tearing it apart, it will be fine.
Now I'm wondering if it would be best to write a practical solution on Real Python and then take out the parts that will fit into Explore Flask. ?
On Thu, Oct 2, 2014 at 12:23 PM, Robert Picard [email protected] wrote:
Sounds good to me, but I should warn you that I'm going to be brutal with comments on the text itself. I'm not afraid to disagree. :)
— Reply to this email directly or view it on GitHub https://github.com/rpicard/explore-flask/issues/71#issuecomment-57691375 .
I would definitely say first step is to come up with an outline regarding what you'd want to cover.
Of course.
I have a Michael Herman's Explore Flask edition that has all my notes on it on my local machine. I have a nice epub version as well so I can go through it on my iPad. I'll write it locally, then see what you think. If you're not keen on it, then I'll tailor it for Real Python.
On Thu, Oct 2, 2014 at 12:29 PM, Robert Picard [email protected] wrote:
I would definitely say first step is to come up with an outline regarding what you'd want to cover.
— Reply to this email directly or view it on GitHub https://github.com/rpicard/explore-flask/issues/71#issuecomment-57692121 .
Sounds good. Thanks!