I'm not sure that your question is a good fit anywhere. The community here was not likely involved in designing and implementing the Python language, so we have no first-hand experiences to draw on. The only person who can provide an experience-based answer would be someone involved in developing Python, and that's such a small group of people compared to those who practice software engineering. Instead of relying on experience, the answers would go down one of two paths. The first would be finding and pointing to references - books, blog posts, conference talks, etc. - by Python developers. The second would be opinion-based, where every answer is sharing that person's opinion or thought and it would be difficult to objectively judge the correctness of each answer. Since the answers that would be generated would likely be low quality, the question isn't a good fit.
I'm also not clear how you are associating this type of question with software development methods and practices, requirements, or architecture and design.
Software development methods and practices refer to how work is done. Think project and program management in software projects. It can be large scale topics, like Scrum, Kanban, RUP, or CMMI. It can also be smaller-scale practices - TDD, pair programming, domain-driven design. It also includes standards, like ISO 12207 and ISO 9000.
Requirements are all about figuring out what stakeholders need. Requirements engineering is about talking to stakeholders to figure out what they need and want, identifying and deconflicting those needs, documenting the stakeholder needs, validating that the developers understand the stakeholder needs, and managing the documentation of and changes to the requirements.
Architecture and design are focused on the structures and interactions of software systems, subsystems, and components at various levels of abstraction, including structuring and organizing code. It also includes modeling those structures and interactions using tools like SysML, UML, C4, ER diagrams, and more.
The question does get into the design of a programming language. There's a weak argument that it does get into the requirements of stakeholders (perhaps the programmers using the language) or the design of interpreters and compilers. However, programming language design is more in the realm of computer science than software engineering.
You may want to check out existing questions or ask for more details on their respective Meta sites, but Computer Science or Programming Language Design and Implementation may be more suitable for this type of question. I'm not sure if they can answer why the design decision was made, though, so you may need to formulate a question based on understanding the decision and its impacts rather than the rationale someone made.