{"action":"created","issue":{"url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/375","repository_url":"https://api.github.com/repos/rhempel/ev3dev-lang-python","labels_url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/375/labels{/name}","comments_url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/375/comments","events_url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/375/events","html_url":"https://github.com/rhempel/ev3dev-lang-python/issues/375","id":260445633,"number":375,"title":"Split core.py into individual files","user":{"login":"WasabiFan","id":3310349,"avatar_url":"https://avatars0.githubusercontent.com/u/3310349?v=4","gravatar_id":"","url":"https://api.github.com/users/WasabiFan","html_url":"https://github.com/WasabiFan","followers_url":"https://api.github.com/users/WasabiFan/followers","following_url":"https://api.github.com/users/WasabiFan/following{/other_user}","gists_url":"https://api.github.com/users/WasabiFan/gists{/gist_id}","starred_url":"https://api.github.com/users/WasabiFan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WasabiFan/subscriptions","organizations_url":"https://api.github.com/users/WasabiFan/orgs","repos_url":"https://api.github.com/users/WasabiFan/repos","events_url":"https://api.github.com/users/WasabiFan/events{/privacy}","received_events_url":"https://api.github.com/users/WasabiFan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-09-25T23:28:55Z","updated_at":"2017-10-01T13:25:32Z","closed_at":null,"author_association":"COLLABORATOR","body":"As discussed in ev3dev/ev3dev#937, it would be helpful for many reasons to split each class or area into its own file.\r\n\r\nThe primary difficulty here is that we want to wait until all outstanding work is merged so that we don't accidentally lose anything. Naturally, git will treat all of these changes as deletions and creations rather than a clean delta.\r\n"},"comment":{"url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/comments/333376512","html_url":"https://github.com/rhempel/ev3dev-lang-python/issues/375#issuecomment-333376512","issue_url":"https://api.github.com/repos/rhempel/ev3dev-lang-python/issues/375","id":333376512,"user":{"login":"dwalton76","id":468309,"avatar_url":"https://avatars2.githubusercontent.com/u/468309?v=4","gravatar_id":"","url":"https://api.github.com/users/dwalton76","html_url":"https://github.com/dwalton76","followers_url":"https://api.github.com/users/dwalton76/followers","following_url":"https://api.github.com/users/dwalton76/following{/other_user}","gists_url":"https://api.github.com/users/dwalton76/gists{/gist_id}","starred_url":"https://api.github.com/users/dwalton76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dwalton76/subscriptions","organizations_url":"https://api.github.com/users/dwalton76/orgs","repos_url":"https://api.github.com/users/dwalton76/repos","events_url":"https://api.github.com/users/dwalton76/events{/privacy}","received_events_url":"https://api.github.com/users/dwalton76/received_events","type":"User","site_admin":false},"created_at":"2017-10-01T13:25:32Z","updated_at":"2017-10-01T13:25:32Z","author_association":"COLLABORATOR","body":"For code varies by platform (take buttons for instance), will the user do `from ev3dev import button` and that in turn determines the platform and imports the appropriate `platform/XYZ.py` or will all button code for all platforms live in `button.py`? If the latter would we even need the platform dir? If its the former it might get a little confusing for the button code to be spread out in different directories.\r\n\r\nI'm still trying to get my head wrapped around what will live where for this scenario.\r\n"}}
{"actor":{"display_login":"dwalton76"}}