{"action":"created","issue":{"url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/6","repository_url":"https://api.github.com/repos/pyladies/pyladies-maintainers","labels_url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/6/comments","events_url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/6/events","html_url":"https://github.com/pyladies/pyladies-maintainers/issues/6","id":167920263,"number":6,"title":"Guided tour to the CPython source code","user":{"login":"gvanrossum","id":2894642,"avatar_url":"https://avatars.githubusercontent.com/u/2894642?v=3","gravatar_id":"","url":"https://api.github.com/users/gvanrossum","html_url":"https://github.com/gvanrossum","followers_url":"https://api.github.com/users/gvanrossum/followers","following_url":"https://api.github.com/users/gvanrossum/following{/other_user}","gists_url":"https://api.github.com/users/gvanrossum/gists{/gist_id}","starred_url":"https://api.github.com/users/gvanrossum/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gvanrossum/subscriptions","organizations_url":"https://api.github.com/users/gvanrossum/orgs","repos_url":"https://api.github.com/users/gvanrossum/repos","events_url":"https://api.github.com/users/gvanrossum/events{/privacy}","received_events_url":"https://api.github.com/users/gvanrossum/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":41,"created_at":"2016-07-27T18:14:51Z","updated_at":"2016-08-08T17:59:52Z","closed_at":null,"body":"I propose that we collaborate on creating a guided tour to the CPython source code. I think such a thing is vastly overdue, and I am not aware of existing resources (though I'll gladly take pointers that prove me wrong).\r\n\r\nI've more or less promised @emilymorehouse to help her get started with something like this, and I'm happy to put time in. @willingc I hope you think this would be a useful document to maintain in this repo? I suppose it would go under the cpython tree.\r\n\r\nThe proposed document differs from the existing guides like the devguide -- it doesn't tell you anything about the patch submission flow, nor even how to get things to build -- it should focus on how to read the CPython source code (using your editor of choice).\r\n\r\nSome topics could include:\r\n- structure of the source code (what goes into Include, Objects, Python etc.)\r\n- bytecode (could start with @akaptur's videos)\r\n- [reference counting](https://en.wikipedia.org/wiki/Reference_counting)\r\n- how to find the definition of something\r\n- how to find where a given error comes from"},"comment":{"url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/comments/238323027","html_url":"https://github.com/pyladies/pyladies-maintainers/issues/6#issuecomment-238323027","issue_url":"https://api.github.com/repos/pyladies/pyladies-maintainers/issues/6","id":238323027,"user":{"login":"emilyemorehouse","id":4264897,"avatar_url":"https://avatars.githubusercontent.com/u/4264897?v=3","gravatar_id":"","url":"https://api.github.com/users/emilyemorehouse","html_url":"https://github.com/emilyemorehouse","followers_url":"https://api.github.com/users/emilyemorehouse/followers","following_url":"https://api.github.com/users/emilyemorehouse/following{/other_user}","gists_url":"https://api.github.com/users/emilyemorehouse/gists{/gist_id}","starred_url":"https://api.github.com/users/emilyemorehouse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emilyemorehouse/subscriptions","organizations_url":"https://api.github.com/users/emilyemorehouse/orgs","repos_url":"https://api.github.com/users/emilyemorehouse/repos","events_url":"https://api.github.com/users/emilyemorehouse/events{/privacy}","received_events_url":"https://api.github.com/users/emilyemorehouse/received_events","type":"User","site_admin":false},"created_at":"2016-08-08T17:59:52Z","updated_at":"2016-08-08T17:59:52Z","body":"@gvanrossum from what I can gather, yes, there's still a difference. `make tags` generates a richer, more universal tags file using `ctags` (whichever variant the user has installed), whereas `make TAGS` generates an Emacs-specific tag file using `etags`. "}}
{"actor":{"display_login":"emilyemorehouse"}}