Top products from r/flask

We found 12 product mentions on r/flask. We ranked the 8 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/flask:

u/invictus08 · 2 pointsr/flask

First of all, applause for the great start.

Here are some criticisms/suggestions I would like to offer. Keep in mind, I am not assuming your level/experience as a software developer:

  1. Functions with smaller size. You see, most of the functions that you have written is lengthy because of the sql statements. Here comes my second point.

  2. Separate business logic, application code, data storage related stuff etc. Keep things modular. That separation is important because you want things to be maintainable and reusable. Your code should be open for extension, but close for modification. If that does not make sense to you, that's perfectly fine, just start from this

  3. On that note, since you are using flask, might I suggest using flask-sqlalchemy instead of sqlalchemy? You may like it better. I know you have mentioned

    > I force myself to write raw SQL Request to get better with SQL

    while that is commendable, it is not really a good idea to write raw sqls in production code if there are ORM library alternatives available. Remember, it's not always you that is going to read/modify the code. While ORM syntax will be fairly universal, your style of writing SQL may vary starkly from other people - which is what creates confusion and lets errors sneak in. Even if you want to do that, maybe keep the raw sql in separate modules (point 2).

  4. Instead of computing everything and then sending the result along with the page, maybe create api endpoints for specific sections; render page with bare minimum info and from the webpage make multiple calls to update the page sections when required. This way, it will be far more responsive, user will not be waiting for you to finish all the computation and if you detect any change in any section of the page, you can just update that particular section with an appropriate api call, thereby avoiding a whole page reload. Design choices.

  5. PEP8. You don't have to blindly follow every rule - just make sure you understand why those rules are there, and that if you are breaking any, you know that it is absolutely necessary for accomplishing what you want. Again, what you want may not always be what you actually need - so be really careful.

  6. This is something I wish I knew earlier - Design Patterns. Without going into much details, I would recommend reading these books to start with and really understand instead of memorizing:
  7. Documentation is also important. Follow the good practices there. A remarkable reference would be Ken Reitz's Requests library.

    Finally, remember that all these are just suggestions, and you may already know them. You will decide which ones to take and which ones to leave behind based on your situation.

    Again, great job (I also learnt something from this). Just make sure you keep running.
u/phalt_ · 3 pointsr/flask

Hi, I'd love to give you some honest feedback on REST APIs and how you've implemented yours.

Have you read any documentation on building REST APIs before? How to use HTTP methods and correctly build URIs? Obviously, REST is a set of guidelines and not a standard, so you haven't done anything wrong, but your API is currently not very REST-like at all. Allow me to explain:

  1. REST should use HTTP methods to perform CRUD (Create, Read, Update and Delete) functions on resources / models in an application. These map to the GET, POST, PUT and DELETE methods in HTTP. Currently, your API does not conform to this. You are using HTTP POST on a GET method here, for example.

  2. Your URIs (URLs) should be formatted like this: /token and not /get_token. Your HTTP METHOD already defines the action you want to perform on the token.

  3. Most REST APIs have decoupled resources, so instead of being able to get the page from a book with a single URL, you should be providing a hypermedia link as an attribute in the returned data of a book resource that links to a list of page resources. Obviously this isn't always practical, and your API might work better this way.

    The main points I'm trying to emphasise here is that REST is not a standard, but it is still a set of guidelines and REST APIs do not just mean you're using HTTP. Now - your API might work perfectly with good documentation and great for you (you built it, after all). Just consider the naming of the type of API before you share it. Someone who sees "this is a REST API" will be in for a shock because some parts of your API is not.

    For further reading, I'd recommend RESTful Web APIs
u/Spuds_McKinness · 5 pointsr/flask

The Flask Mega Tutorial is the canonical onboarding, but for some reason I gravitated towards Miguel’s O’Reily on Flask instead.

https://www.amazon.com/Flask-Web-Development-Developing-Applications/dp/1491991739

I especially appreciated the first third of the book being a simple app architecture, THEN the rest of the book making things more scalable for larger applications.

So I guess if you are already a web dev, the mega tutorial will definitely get you where you’re going, but if you’re brand new to web dev (like me!), I’d recommend the above. They’re not too different, but I like the second one better :)

u/johnwheeler_ · 1 pointr/flask

These are sweet! Subscribed. I'm starting to do tutorials for Echo programming, so we're probably on similar wavelengths and maybe can even work together in the future if it makes sense (The Echo programming I do is based on a Flask extension I wrote).


I'm using Camtasia and a Blue Snowball mic - You can check out the audio https://www.youtube.com/watch?v=1l6qwz-xZmc I'm also learning a ton about nonlinear video editing. I've been checking out the more expensive Yeti mic from Blue, and the demos I heard sounds terrific (demo in reviews).


http://www.amazon.com/gp/product/B002VA464S/ref=pd_lpo_sbs_dp_ss_3?pf_rd_p=1944687702&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=B000EOPQ7E&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=1P7SMM61C64JAVRRG0XS


Best of luck to you Alex!

u/7600_slayer · 2 pointsr/flask

I'd also like to recommend Miguel's book: Flask Web Development

I started with that and Miguel's blog, worked great for me.

u/generic_gif · 6 pointsr/flask

The man himself! Too cool. I'm going back now and re-reading the section of your book that covers the Application and Request Contexts, everything's starting to come together now, especially after having gone back and taken a look at the Form class.

Thanks for taking the time to respond, in case anyone's wondering I highly recommend the book/blog!! (Flask Web Development, published by O'Reilly)

u/Earhacker · 2 pointsr/flask

This is the second edition, which hasn't been released yet. Amazon UK says 31st March. I know this because it's been in my wishlist for months.

u/WunderBoss · 1 pointr/flask

make sure this is legally waterproof. i've read in Social Engineering that there was prosecution of hired security experts that performed a certain penetration test on their clients servers, because it's still a criminal offence to do so.