Hi James, Sure, let's do that! I'm fine with emails, too. I needed only a bit of structure since we lumped so many issues together, but maybe it's just my OCD :)
Le lun. 1 oct. 2018 à 04:05, James Lu <jam...@gmail.com> a écrit : > Hi Marko, > > Regarding switching over to GitHub issues: > * I copy-pasted the MockP original code to GitHub issues. > * There's a clunky way to view the discussion at > https://mail.python.org/pipermail/python-ideas/2018-September/subject.html#start > . > * The less clunky way to view the discussion is to subscribe to the > mailing list and use Gmail to move all the messages from python-ideas to > python ideas list and all the messages from the discussions we have to a > "contracts" label and view the discussion with your email client. > * A week earlier I didn't think I'd be saying this, but I like email for > discussion better. It works on mobile and I can send messages offline, and > I send 90% of my messages on my phone and when I'm offline. Unless you know > an alternative (WhatsApp, maybe?) that fits my use cases off the top of > your head, I think we should stick to email. > * My proposal: We split the discussion into a new email thread, we keep > the latest agreed upon proposal on GitHub issues. > > On Sun, Sep 30, 2018 at 4:32 PM Marko Ristin-Kaufmann < > marko.ris...@gmail.com> wrote: > >> Hi James, >> (I'm just about to go to sleep, so I'll answer the other messages >> tomorrow.) >> >> Should we keep some kind of document to keep track of all the different >>> proposals? I’m thinking an editable document like HackMD where we can label >>> all the different ideas to keep them straight in our head. >>> >> >> I thought github issues would be a suitable place for that: >> https://github.com/Parquery/icontract/issues >> >> It reads a bit easier as a discussion rather than a single document -- if >> anybody else needs to follow. What do you think? >> >> On Sun, 30 Sep 2018 at 22:07, James Lu <jam...@gmail.com> wrote: >> >>> Hi Marko, >>> >>> Going back to your proposal on repeating lambda P as a convention. >>> >>> I do find >>> >>> @snapshot(some_identifier=P -> P.self(P.arg1), >>> some_identifier2=P -> P.arg1 + P.arg2) >>> >>> acceptable. >>> >>> Should we keep some kind of document to keep track of all the different >>> proposals? I’m thinking an editable document like HackMD where we can label >>> all the different ideas to keep them straight in our head. >>> >>> James Lu >> >>
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
