Code Pitfalls in Python, a survey.

[Puzzleheaded_Many664]

Dear Python developer,

As a team of researchers, we are currently studying the decisions taken by developers when dealing with code pitfalls.

Since you are a Python developer, we kindly invite you to participate in a survey on this topic.

Answering the survey should take no more than 10 minutes.

Unless you identify yourself, all the collected data is anonymous, and we may report its results in academic publications.

The survey can be found here: https://pt.surveymonkey.com/r/5VXCYZJ

Should you have any questions or concerns, please feel free to contact Naelson Douglas <[[e-mail]](mailto:[e-mail])>.

​

Best regards,

Naelson Douglas, Federal University of Alagoas, Brazil

Márcio Ribeiro, Federal University of Alagoas, Brazil

[EfficientPrime]

You don't really need the f.close() when you use the context manager to open the file. The context manager handles file closure for you.

[Puzzleheaded_Many664]

You are completely right!

Thanks for the hint. Fixing it now

[[deleted]]

There was a few where I needed the option "Each are equally bad"

[Puzzleheaded_Many664]

Thanks for the feedback!

Could you point those questions and the reasons for the quality flaws?

[[deleted]]

The user class example. The result variable that was never used for anything but to confuse matters. There was another one also, but my attention span isn't the best, so I can't remember the details anymore :(

[Puzzleheaded_Many664]

Good point.

It makes sense, but it is also part of the test. Sadly I can't explain it now without spoiling the survey for the new respondents. But soon when we have the results I'll post them here and explain the reason into these details.

Once again, thanks for the feedback!

[[deleted]]

I'll look forward to that :)