Re: [Python-Dev] do people use sys._mercurial?

2016-01-24 Thread Nick Coghlan
On 24 January 2016 at 05:48, Brett Cannon wrote: > On Sat, 23 Jan 2016 at 11:45 francismb wrote: >> for me sys._mercurial it's already returning that (?) : what should >> return now? (it's a bug?) > > Depends on your OS and how CPython was built whether it returns that value > or something more u

Re: [Python-Dev] do people use sys._mercurial?

2016-01-24 Thread Nick Coghlan
On 24 January 2016 at 10:29, Brett Cannon wrote: > Some discussion happened on core-workflow@, otherwise you can look through > the python-dev archives for when we added sys._mercurial. We actually forgot one relevant point in those discussions: there's already a generic API for accessing this in

Re: [Python-Dev] Code formatter bot

2016-01-24 Thread francismb
Hi, from your valuable feedback, here is what I thing could be a previous requirements list (lets call it for e.g. autopep7 script by now): - It should follow PEP 7 :-) - It should check PEP 7 compliance on a per file basis (for simplicity) - It should be embeddable on the test suite, returning PA

Re: [Python-Dev] do people use sys._mercurial?

2016-01-24 Thread francismb
Hi, On 01/24/2016 01:17 PM, Nick Coghlan wrote: > > Linux distros tend to build Python from a tarball rather than a source > checkout, for example, which means the build directory doesn't include > any VCS details: > Does that helps traceability (reproducibility)? If distros use (?) the tarball

Re: [Python-Dev] Code formatter bot

2016-01-24 Thread Raymond Hettinger
> On Jan 19, 2016, at 12:59 PM, francismb wrote: > > Dear Core-Devs, > what's your opinion about a code-formatter bot for cpython. > Pros, Cons, where could be applicable (new commits, new workflow, it > doesn't make sense), ... > > > - At least it should follow PEP 7 ;-) Please don't do this

Re: [Python-Dev] do people use sys._mercurial?

2016-01-24 Thread Stephen J. Turnbull
francismb writes: > Does that helps traceability (reproducibility)? If distros use (?) > the tarball from the release why it doesn't have, at least, the > information from where that tarball was generated from (the check > out point) ? The pointer goes in the other direction: there will be a

Re: [Python-Dev] do people use sys._mercurial?

2016-01-24 Thread Nick Coghlan
On 25 January 2016 at 03:40, francismb wrote: > On 01/24/2016 01:17 PM, Nick Coghlan wrote: >> Linux distros tend to build Python from a tarball rather than a source >> checkout, for example, which means the build directory doesn't include >> any VCS details: > Does that helps traceability (reprod