If this PR is to be accepted, this change will need to be removed.

I removed because it creates bias for the Python webframework. Django might be popular but it is anything but certain that most web application are built with Django. In fact Python has about 35 web frameworks.

If this PR is to be accepted, this change will need to be removed.

If this PR is to be accepted, this change will need to be removed.

Why is Flask the default? What makes that statement factually true?

I don't agree that this change would need to be removed. Why is Flask a "default" choice for any Python web application that isn't a good fit for Django? What exactly about Flask makes it a "default" choice? A "default" choice by whose standards?

This could be reworded as "Flask is a good choice for Python web applications that don't require all of Django's bells and whistles", and it wouldn't exclude every single other framework to the exclusion of Django/Flask.

@bertjwregeer that rewording isn't bad. However, the sentence is intended to do exactly what you suggest.

If this PR is to be accepted, this change will need to be removed.

Am I misunderstanding you here? If the intent of the sentence is excluding everything but Flask and Django, why even mention Pyramid?

Also, from Flask docs: "However Flask is just not designed for large applications or asynchronous servers. Flask wants to make it quick and easy to write a traditional web application." Are you seriously saying that Django is the only option for large applications? Or are you simply not in agreement with the Flask docs?

@cguardia He mentioned that here:

https://github.com/kennethreitz/python-guide/pull/692#issuecomment-203679472

Let me quote:

This page really only needs to mention Django and Flask. I added Pyramid to be nice to the Pyramid community, [...]

So he wants to be nice to the Pyramid community, yet the entire thing reads like "Pyramid is not used so you shouldn't either". A backhanded compliment if you will.

This section's purpose is to recommend the following:

• Almost everyone uses Django. Here's what it's great for.
• If you don't want to use Django, use Flask. It's fantastic.
• Here's a few others (e.g. pyramid, tornado) for the unlikely event that you're still looking for something else.

As mentioned elsewhere on this page, Pyramid could easily be left out of this document, as could tornado (as web2py is). However, I think they are both worthy of mention, with attention brought towards the fact of why they wouldn't otherwise be included.

This paragraph existed in the guide for a while, and was re-written as the original paragraph you are suggesting to replace. What exact information does this pice of text provide that the version your are suggestion be replaced does not? I would prefer to add an additional sentence instead of using this block.

Pyramid is not at all like Django. It does not make sense to make that comparisson. Django is monolithic, Pyramid is anything but. Django tightly couple it's ORM, its Models, Admin and Form management. Pyramid does none of that and has no opinions about the Resources it uses with only one of them being SQLAlchemy,

Suggesting it's a lot like Django does a huge disservice to anyone reading the guide. Unlike Django Pyramid is not kitchen sink included. We allow users to pick and chose from the vast Python eco-system so that they can use best of breed tools without requiring explicit framework support.

Pyramid also follows Python packaging standards more closely, which leads to better code re-use across projects, and can work a lot like Flask or Django, and as projects grow Pyramid more easily grows with them, so start Flask like, and over time grow to use the Django like functionality, no rewrites required.

Thats what "a heavier focus on modularity" is intended to address. Let's focus on rewording that sentence, then.

This whole paragraph should be able to be reduced to a sentence or two.

This paragraph is needless. Trying to keep these sections succinct.

This paragraph is needless. Trying to keep these sections succinct.

It the same size as Django and Flask sections actually. Reword it as you wish.

It's important to note here that Pyramid's userbase and community is significantly smaller than the other frameworks mentioned. Code quality is far from the the only qualifier when selecting a web framework.

This is not proper link syntax for this project. This link is also generally needless, as long as we're linking to the overall documentation.