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
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
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
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
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
Some discussion happened on core-workflow@, otherwise you can look through
the python-dev archives for when we added sys._mercurial.
On Sat, 23 Jan 2016, 16:25 Random832 wrote:
> Brett Cannon writes:
> > (and no, we are not going to adopt a generic one; already had that
> > debate).
>
> Do you
Brett Cannon writes:
> (and no, we are not going to adopt a generic one; already had that
> debate).
Do you have a link to the relevant discussions?
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
U
On Sat, 23 Jan 2016 at 11:45 francismb wrote:
> Hi,
>
> On 01/23/2016 12:44 AM, Brett Cannon wrote:
> > Since we are going to be switching over to Git, sys._mercurial is going
> to
> > be made to return a dummy value of `('CPython', '', '')` once we switch
> to
> > Git.
>
> for me sys._mercurial
Hi,
On 01/23/2016 12:44 AM, Brett Cannon wrote:
> Since we are going to be switching over to Git, sys._mercurial is going to
> be made to return a dummy value of `('CPython', '', '')` once we switch to
> Git.
for me sys._mercurial it's already returning that (?) : what should
return now? (it's a
It seems that people do use the values so there will be a sys._git
attribute.
On Fri, 22 Jan 2016 at 19:57 Ned Deily wrote:
> On Jan 22, 2016, at 18:44, Brett Cannon wrote:
> > Since we are going to be switching over to Git, sys._mercurial is going
> to be made to return a dummy value of `('CPy
On Jan 22, 2016, at 18:44, Brett Cannon wrote:
> Since we are going to be switching over to Git, sys._mercurial is going to be
> made to return a dummy value of `('CPython', '', '')` once we switch to Git.
> But my question is do we bother to replace it with sys._git? I wanted to make
> sure th
On 23 January 2016 at 09:44, Brett Cannon wrote:
> Since we are going to be switching over to Git, sys._mercurial is going to
> be made to return a dummy value of `('CPython', '', '')` once we switch to
> Git. But my question is do we bother to replace it with sys._git? I wanted
> to make sure tha
Since we are going to be switching over to Git, sys._mercurial is going to
be made to return a dummy value of `('CPython', '', '')` once we switch to
Git. But my question is do we bother to replace it with sys._git? I wanted
to make sure that the effort is worth it to keep changing these
VCS-specif
13 matches
Mail list logo