FAQ: Learn Python: Functions - Function Junction

This community-built FAQ covers the “Function Junction” exercise in Codecademy’s lessons on Python.

FAQs for the Codecademy Python exercise Function Junction:

Join the Discussion. We Want to Hear From You!

Have a new question or can answer someone else’s? Reply (reply) to an existing thread!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources about Python in general? Go here!

Want to take the conversation in a totally different direction? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account, billing, Pro, or Pro Intensive? Reach out to our support team!

None of the above? Find out where to ask other questions here!

Other FAQs

The following are links to additional questions that our community has asked about this exercise:

  • This list will contain other frequently asked questions that aren’t quite as popular as the ones above.
  • Currently there have not been enough questions asked and answered about this exercise to populate this FAQ section.
  • This FAQ is built and maintained by you, the Codecademy community – help yourself and other learners like you by contributing!

Not seeing your question? It may still have been asked before – try (search) in the top-right of this page. Still can’t find it? Ask it below by hitting the reply button below this post (reply).

2 posts were split to a new topic: Why Does the Lesson Use Triple Quotes Instead of Hash Signs For the Comment?

A post was split to a new topic: Didnt i just set the value

Entered identical code to solution given and received error code “Failed to test code”.

Same here. My comment was different but that’s irrelevant.
Please fix the bug. Thanks
FYI…The next one has the same issue.

1 Like

After some frustrated toying, I replaced code w/ solution. It runs and prints “Eggs!”, but is still marked as incorrect. Unable to proceed and unsure of what to do.

2 Likes

Why can’t you use “#” to comment rather than the triple quotes? Don’t they do the same thing? The code already written into the terminal area (I’m unsure what you call the area where you type the code) has comments written with the # key, so it makes zero sense to me why it makes you use triple quotes.

If it is simply just wanting you to do that comment method vs the other, then why do previous units allow you to use different code that does the same thing i.e. in the pig latin project, you need to grab the every letter except the first. You’d type something like [1:len(variable)] which supposedly would grab “ariable” (pretending “variable” is stored in variable. But it also lets you do [1:(variable)]. Though, ironically enough, in that lesson, it wasn’t letting me finish it the way it taught, it only let me do it once I typed it the way it showed you could do in the “Hint” section.

Albeit, replies much appreciated!

# is for single inline comments.

'''...''' is for multiline comments, and when used at the very start of a function, for writing a docstring of the function that help() can access.


On another consideration, commenting out code, temporarily, is a common debugging and testing strategy during the build phase. In the end, all comments might best be removed if they are not absolutely necessary in a production or end use version. That is where the docstring comes in.

In any interactive shell, type,

>>> help(print)

or any other built-in, for that matter. They all have a docstring. Notice how it describes both syntax and common usage? That is how we might best document our function, as well.

One should take one’s own advice more, though. Pretty sure there are still of my repl’s out there that have commented lines all over the place to show the progression from one method to another. Really need to go back and clean those up.