-
-
Notifications
You must be signed in to change notification settings - Fork 314
Introducing len() function #376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introducing len() function #376
Conversation
|
Could you please restore the 6th episode? It will be deleted from the repo if we merge your PR as is. You can restore the episode with the following commands: git checkout gh-pages _episodes/06-loops-and-functions.md
git add -u
git commit -m "Restore 06-loops-and-functions.md"
git push your-fork |
|
Apologies, its my first time doing this. |
|
Oh, I see... You can't do what I asked for using web interface. |
Addressing Issue datacarpentry#362: Ep2: Statistics challenge relies on untaught knowledge datacarpentry#362 Introducing the built-in function len() after the tuple and list section in episode 01
908a53e to
846332c
Compare
|
Thank you.
Sorry for the trouble . I was trying to undo the changed and didn't realise
that would happen.
…On Sun, Apr 28, 2019, 4:59 AM Maxim Belkin ***@***.***> wrote:
Oh, I see... You can't do what I asked about using web interface.
But don't worry -- I'll do that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADJQ2IQFRO4VFFMS7KY2VELPSSPARANCNFSM4HIUFRAA>
.
|
|
No worries. It was not difficult to fix -- I just was not sure if you wanted to do it yourself or not. My thoughts: the question, if added, should be reformulated as:
|
|
Thank you.
Ideally, I would have liked to do it, but I am still figuring how to
contribute using GitHub website and do not want to mess things up.
I do like the reformatted challenge question.
…On Sun, Apr 28, 2019 at 2:08 PM Maxim Belkin ***@***.***> wrote:
No worries. It was not difficult to fix -- I just was not sure if you
wanted to do it yourself or not.
I'll let April ***@***.*** <https://github.com/wrightaprilm>) chime in
on the content.
My thoughts: the question, if added, should be reformulated as:
"Find the number of elements ("items") in a_list or a_tuple using
Python's built-in function len()"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADJQ2IXAJW5PDNGG3CZVYXTPSUPK5ANCNFSM4HIUFRAA>
.
|
|
No problem, Pradeep. |
|
The idea was to show that the same built-in function can be used for looking at two different data structures, and to introduce the len() function. |
|
I'm on the fence with regards to this PR. Let me first argue why I think it should not be merged and then on what grounds it can be merged. NAY: I think that when we're talking about differences (between any two things) it is important to highlight exactly them, not the common things. This way these differences have a better chance of sticking in our minds. AYE: We could, actually, start with the I'll let @wrightaprilm make the final decision. |
|
I'm also a little bit on the fence - we do introduce built-in functions in this lesson, so I like the idea of having the learners just try another built-in. And my hesitance isn't about this pull request, per se. One thing that this lesson is kind of weak on is tuples as a data type. The why isn't well explained, and I often skip them for later when I use these materials. What if we edited the question to be about the built-in function? As in "What information does the built-in function |
I like that idea. |
|
Hi, Pradeep! Did you want to update the PR as we discussed above? Do you need any help with that? What information does the built-in function `len()` provide?
Does it provide the same information on both tuples and lists?
Does the `help()` function confirm this? |
|
I'm helping the current lesson Maintainers process outstanding pull requests on this repository, in preparation for transition to the new lesson infrastructure. @pr4deepr thank you for contributing this suggested change. Reading through the conversation above it seems the former lesson Maintainers settled on a suggestion for how the exercise text could be adjusted to address the issue. If you are still interested in contributing this change, please resolve the conflicts that have been introduced in the intervening years then update the pull request (or close it and open a new one) based on the suggestion above before the end of April. After that, the infrastructure transition will invalidate your fork and we will have to close the PR. Let me know if there's anything I can do to help. |
|
Closing in favour of #449 |
Addressing #362 to introduce len() built-in python function