Skip to content
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

Scraping OKpy server stuff from the homework materials #11

Closed
choldgraf opened this issue Mar 1, 2018 · 4 comments
Closed

Scraping OKpy server stuff from the homework materials #11

choldgraf opened this issue Mar 1, 2018 · 4 comments

Comments

@choldgraf
Copy link
Collaborator

Right now we have a lot of homework materials / labs that require OKpy authentication and submission. What's the best path forward for scraping this away from the notebooks so that others can interact with them. Two main ideas I had:

  1. Write a helper script that clones the homework/lab repos and automatically scrapes out the server-specific stuff, then places the repo in the user's current directory.
  2. Publish a "public-facing" version of the homeworks/labs.
  3. Provide a "request access to the homeworks" form and then we grant people private access so they can clone w/o the answers being public. Combine this with Improvements to make #1

Any other ideas on how this could be handled? @henchc you mentioned this before, so curious as to your thoughts

@henchc
Copy link

henchc commented Mar 1, 2018

I think option 1 shouldn't be too hard. if you take hw1 as an example, you can remove the _ = ok.auth(inline=True) line and all .submit lines. When you run _ = ok.grade('q2') you can still see if you got the answer correct because the answers are all local at this point.

this would allow one to complete the entire course and get it graded, but it wouldn't track it in a database like the OKpy servers (which I don't think we could expect to support).

am i missing something?

@henchc
Copy link

henchc commented Mar 1, 2018

and as for #3 isn't it all public already?

@choldgraf
Copy link
Collaborator Author

cool, we can shoot for 1 and good point re: number 3

@choldgraf
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants