10 Sep

Weekly Update 118: Up close with Python

This is a copy of our weekly newsletter for developers which you can subscribe to here.

Hello contributors,

We're continuing our weekly look into the progress of the programming mission and it's the turn of Python, the only language that let's you fly!

Since the start of the mission, Instant Answer coverage for Python-related queries has increased from 35% to 46%. A lot of this is due to improvements with Python docs, but progress has also been made for Django and with tutorial snippets. For example:

Screenshot of a Python Instant Answer

As you can see, this is really helping Python developers and it's thanks to the contributors in our community, in particular Robert and Jussi. Why not join them and help get the Python Instant Answer coverage to 50% and beyond? Details and current status are in the Python Overview post on the forum, where Jason and Zaahir are happy to help.

And now, here are some specific issues we're currently looking for help with...

5-minute Fixes

More quick fix ideas here...

Weekend Warriors

More high priority fix ideas here...

Quick Tip

I'm going to follow the trend of the past two weeks and make the "back-to-basics" tips a trilogy!

When you're learning a programming language, it's common to copy and execute chunks of code from a book or tutorial, but inevitably they sometimes fail. Because the language is new, it's difficult to find the problem quickly and the error messages often don't help, so before you get stuck, here's something to try...

Deliberately make errors

That's right — I want you to put bugs in your code on purpose! When you do, check the resulting error message and make a note of it. For example, you could:

  • Use a variable without declaring it.
  • Use the wrong number of arguments for a function.
  • Remove a character such as a parenthesis or semi-colon.
  • Spell important words wrong in various parts of the code.

Repeat this a few times and you'll soon learn what causes common error messages, meaning that when they appear "for real" it should be much faster for you to find and fix the problem.

You could even use it as an excuse if you mess up in future: "Oh yeah, that bug is supposed to be there!"

Happy coding everyone and enjoy your weekend!

- The DuckDuckGo Staff

2 Tweet

This blog has been archived

Thank you for reading and contributing lively discussion to our blog! Read more posts about online privacy on our new blog at spreadprivacy.com.

I am among those who voted for there to articles related to Python! :D

posted by jarod11 • 1 year and 2 months ago Link

Great, thank you! We hope to keep adding more.

posted by tagawa Staff • 1 year and 2 months ago Link