Django has a few features that can be taken for granted: the ORM, the templating language (ouch), the admin, the user/auth/permission system, the division in views (called controllers in Rails) and templates (called views in Rails.) They are well known entities but there is no well defined structure for the code. A project can have any shape and I've seen no two projects with the same shape. On the other side every Rails project has the same shape, often even across multiple versions of the framework. The greatest departures from the standard are some app/services directories but in general you can tell where a url is implemented without looking at Rails' equivalent of urls.py
Django allows multiple subprojects inside an app and code wherever one wants to place it. Rails also allows code anywhere but in practice it's always in the same places. Maybe it's Python, inviting developers to overengineer their code.
Yeah the templating language is not so nice, I sometimes use Jinja instead. Also, I don't like the classic MVC so I have a completely different structure thus validation your point completely :P
If you ever end up in Django land (for some project), checkout Django Ninja for APIs, you'll end up avoiding having these annoying url files and just have a
@api.get("some/api")
def some_api(request):
instead. Super simple and useful. I just recently discovered it and I don't know how stable it is but it seems pretty stable so far.
Django allows multiple subprojects inside an app and code wherever one wants to place it. Rails also allows code anywhere but in practice it's always in the same places. Maybe it's Python, inviting developers to overengineer their code.