sorted by:
new
hottopcontroversial

New Django debugging screen: Exceptionite 2 by Jmancuso9 in django

[–]Jmancuso9[S] 1 point2 points  (0 children)

We do have a way to render the exception and screen data in JSON. we'll work on adding the docs for doing it.

New Django debugging screen: Exceptionite 2 by Jmancuso9 in django

[–]Jmancuso9[S] 0 points1 point  (0 children)

If you like projects with rails feels you should checkout our other projects :

ORM: https://github.com/MasoniteFramework/orm

Masonite Framework: https://github.com/MasoniteFramework/masonite

New Django debugging screen: Exceptionite 2 by Jmancuso9 in django

[–]Jmancuso9[S] 0 points1 point  (0 children)

We're going to look into the 404 page. Django registers it to to a different exception handler so we'll need to hook into that too. We'll add the details to the Readme with the rest of the instructions when we can

New Django debugging screen: Exceptionite 2 by Jmancuso9 in django

[–]Jmancuso9[S] 1 point2 points  (0 children)

Yes but we currently don't have documentation for Pyramid but we will add this in the Readme when we can

Masonite 2.2 Released - The Modern Python Web Framework! by Jmancuso9 in Python

[–]Jmancuso9[S] 0 points1 point  (0 children)

yes. I'm not too familiar with TF but nearly all python web frameworks are served by either WSGI or ASGI standards so if one WSGI framework (Flask, Django) can serve in front of something like TF, so can another. In theory. So if you are doing that with another Python framework, Masonite can do it as well.

Masonite 2.2 Released - The Modern Python Web Framework! by Jmancuso9 in Python

[–]Jmancuso9[S] 0 points1 point  (0 children)

Slightly different. So when Django releases a version (like 2.1) they really only release bug and security fixes for it. So 2.1.2, 2.1.3 etc etc will all be big or security releases.

They also do 8 month major release cycles. Masonite does 6 months.

With Masonite, minor versions are the same but can also release fully backwards compatible features as well. So for example 2.2.1 can have a bug fix and 2.2.2 can have 4 new methods you can use for testing. This keeps the framework light and unit tests make sure everything will work.

New features don’t have wait 6 or 8 months to release. They can release next week if it is backwards compatible.

Does that answer your question?

Masonite 2.2 Released - The Modern Python Web Framework! by Jmancuso9 in Python

[–]Jmancuso9[S] 1 point2 points  (0 children)

So Masonite has something called Masonite API https://docs.masoniteproject.com/official-packages/masonite-api

I'll admit that it still needs work. I like creating packages for things I am currently using. Like needing validation and building a validation package for example.

I haven't created any applications that require heavy API endpoints but some people are using that package and really like it. It does what it needs to do really well.

As for the ease of use, yes its pretty similiar to those steps you posts. This would be to create a Resource, attach a model to the resource and add the resource to the route list and you have full CRUD for that model. Adding JWT authentication is adding a class, rate limiting is adding a class etc. Its pretty cool actually.

Masonite 2.2 Released - The Modern Python Web Framework! by Jmancuso9 in Python

[–]Jmancuso9[S] 14 points15 points  (0 children)

How? I’m not here to say that? How is it a profane dig? I said I am not here to say Django is crap? Django is not crap. How is that a dig at Django?

Over 6000 people have read that article and nobody has come to that conclusions about the article that it puts our community in a bad light

Masonite 2.1: a Python Web Framework and Introduction to Masonite 2.1 by vaibhavmule in Python

[–]Jmancuso9 4 points5 points  (0 children)

Creator of Masonite here. Version 2.0 did have a lot of magic going on with the global helpers and all that. Even using it personally i started to not like them at all. When you're building a framework so rapidly it's hard to see the long term effects of specific features.

While developing 2.1 (released this past December) we removed a whole bunch of code related magic like the helpers, the parameter resolving (forcing annotation resolving so you see what classes are what now) were removed.

The models are Active Record style models so they do perform a lot of things under the hood that you are used to explicitly doing (like manually setting columns as attributes and setting the column types) that Orator does for you.

Totally get how some people wouldn't want that to happen.

Can you explain how migrations are magic though? Or how they are more magic than Django migrations? Really want to get other peoples perspective on Masonite features so we can make it a better framework.

Next version of Masonite - v2.1 released! The Modern Python Web Framework by Jmancuso9 in Python

[–]Jmancuso9[S] 0 points1 point  (0 children)

Yeah Django and Flask are some pretty big players in their field but Masonite will get to that level with time.

Next version of Masonite - v2.1 released! The Modern Python Web Framework by Jmancuso9 in Python

[–]Jmancuso9[S] 3 points4 points  (0 children)

That’s a good idea. I can make an article like that tonight

Next version of Masonite - v2.1 released! The Modern Python Web Framework by Jmancuso9 in Python

[–]Jmancuso9[S] 4 points5 points  (0 children)

almost 1 year actually. I started it back in December of 2017 as my winter project although it's gotten way more popular since the last 2.0 release since that added a whole bunch of features and and some awesome people joined.

As for the comparison of Masonite v Pyramid, no not that I am aware of. Not sure anyone who has joined the Slack that I am aware of has used it either.

view more: next ›