Re: [core-workflow] PEP 512 - Choosing a CI service

Hey Ryan, You're right that Travis supports uploading/deploying to various services. My wording is really bad there. For my purposes of exposing the xunit output, i wished that Travis would at least keep/expose some artifacts itself to save me trouble. Do you know if that is supported by Travis?

Re: [core-workflow] Updated draft of PEP 512

For backwards compatibility sys._mercurial must probably stay. Maybe it could be None, so we could write if sys._mercurial: ... elif sys._git: ... else: # unknown VCS ... On Wed, Jan 20, 2016 at 12:39 PM, francismb wrote: > Hi Brett, > > > > Change sys._mercurial >

Re: [core-workflow] Updated draft of PEP 512

FWIW sys.subversion has been deprecated in 3.2.1 and removed in 3.3 [0]. In 3.2.1+ and 2.7 it returns ('CPython', '', ''). In theory sys._mercurial is private, so technically we don't have to go through the same deprecation process, but I see no harm in deprecating it in 3.6 and then removing it