Re: [Python-Dev] What is the rationale behind source only releases?

On 17May2018 1004, Brett Cannon wrote: > > > On Thu, 17 May 2018 at 09:57 Paul Moore > wrote: > > On 17 May 2018 at 14:42, Brett Cannon > wrote: > > > > If I understand things

Re: [Python-Dev] What is the rationale behind source only releases?

On Thu, 17 May 2018 at 09:57 Paul Moore wrote: > On 17 May 2018 at 14:42, Brett Cannon wrote: > > > > If I understand things correctly, our planned migration to VSTS will > include > > eventually automating the signing of the Windows releases so that part

Re: [Python-Dev] What is the rationale behind source only releases?

On 17 May 2018 at 14:42, Brett Cannon wrote: > > If I understand things correctly, our planned migration to VSTS will include > eventually automating the signing of the Windows releases so that part wont > be an issue (which are currently signed manually be Steve). Somewhat

Re: [Python-Dev] What is the rationale behind source only releases?

On Thu, 17 May 2018 09:42:38 -0400 Brett Cannon wrote: > > If I understand things correctly, our planned migration to VSTS will > include eventually automating the signing of the Windows releases so that > part wont be an issue (which are currently signed manually be Steve).

Re: [Python-Dev] What is the rationale behind source only releases?

On Thu, 17 May 2018 at 04:25 Paul Moore wrote: > On 17 May 2018 at 04:46, Alex Walters wrote: > >> 1. Producing binaries (to the quality we normally deliver - I'm not > >> talking about auto-built binaries produced from a CI system) is a > >> chunk

Re: [Python-Dev] What is the rationale behind source only releases?

On May 17, 2018, at 04:24, Paul Moore wrote: > On 17 May 2018 at 04:46, Alex Walters wrote: >>> 1. Producing binaries (to the quality we normally deliver - I'm not >>> talking about auto-built binaries produced from a CI system) is a >>> chunk of

Re: [Python-Dev] What is the rationale behind source only releases?

On 17 May 2018 at 04:46, Alex Walters wrote: >> 1. Producing binaries (to the quality we normally deliver - I'm not >> talking about auto-built binaries produced from a CI system) is a >> chunk of extra work for the release managers. > > This is actually the heart of the

Re: [Python-Dev] What is the rationale behind source only releases?

On 5/16/2018 11:46 PM, Alex Walters wrote: This is actually the heart of the reason I asked the question. CI tools are fairly good now. If the CI tools could be used in such a way to make the building of binary artifacts less of a burden on the release managers, would there be interest in

Re: [Python-Dev] What is the rationale behind source only releases?

> -Original Message- > From: Paul Moore <p.f.mo...@gmail.com> > Sent: Wednesday, May 16, 2018 4:07 AM > To: Alex Walters <tritium-l...@sdamon.com> > Cc: Python Dev <python-dev@python.org> > Subject: Re: [Python-Dev] What is the rationale behind sourc

Re: [Python-Dev] What is the rationale behind source only releases?

org> On Behalf Of Donald Stufft Sent: Wednesday, May 16, 2018 1:23 AM To: Ben Finney <ben+pyt...@benfinney.id.au> Cc: python-dev@python.org Subject: Re: [Python-Dev] What is the rationale behind source only releases? On May 16, 2018, at 1:06 AM, Ben Finney <ben+pyt...@benfinney.id.

Re: [Python-Dev] What is the rationale behind source only releases?

Thank you, that's exactly what I needed to read. > -Original Message- > From: Ned Deily <n...@python.org> > Sent: Wednesday, May 16, 2018 7:07 AM > To: Alex Walters <tritium-l...@sdamon.com> > Cc: Python-Dev <python-dev@python.org> > Subject: Re: [Pyth

Re: [Python-Dev] What is the rationale behind source only releases?

On May 16, 2018, at 00:35, Alex Walters wrote: > > In the spirit of learning why there is a fence across the road before I tear > it down out of ignorance [1], I'd like to know the rationale behind source > only releases of cpython. Historically, it was a matter of

Re: [Python-Dev] What is the rationale behind source only releases?

On May 16, 2018, at 00:35, Alex Walters wrote: > In the spirit of learning why there is a fence across the road before I tear > it down out of ignorance [1], I'd like to know the rationale behind source > only releases of cpython. I have an opinion on their utility and

Re: [Python-Dev] What is the rationale behind source only releases?

On 5/16/18 4:34 AM, Serhiy Storchaka wrote: 16.05.18 07:35, Alex Walters пише: [1]: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence And I wish that every author who suggested the idea for Python was familiar with the Chesterton's fence principle. Indeed! It's refreshing.

Re: [Python-Dev] What is the rationale behind source only releases?

On 16 May 2018 at 09:34, Serhiy Storchaka wrote: > 16.05.18 07:35, Alex Walters пише: >> >> [1]: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence > > > And I wish that every author who suggested the idea for Python was familiar > with the Chesterton's fence

Re: [Python-Dev] What is the rationale behind source only releases?

16.05.18 07:35, Alex Walters пише: [1]: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence And I wish that every author who suggested the idea for Python was familiar with the Chesterton's fence principle. ___ Python-Dev mailing list

Re: [Python-Dev] What is the rationale behind source only releases?

16.05.18 07:35, Alex Walters пише: In the spirit of learning why there is a fence across the road before I tear it down out of ignorance [1], I'd like to know the rationale behind source only releases of cpython. I have an opinion on their utility and perhaps an idea about changing them, but

Re: [Python-Dev] What is the rationale behind source only releases?

On 16 May 2018 at 05:35, Alex Walters wrote: > In the spirit of learning why there is a fence across the road before I tear > it down out of ignorance [1], I'd like to know the rationale behind source > only releases of cpython. I have an opinion on their utility and

Re: [Python-Dev] What is the rationale behind source only releases?

On Tue, May 15, 2018 at 10:55:07PM -0700, Chris Jerdonek wrote: > What does “no release at all” mean? If it’s not released, how would people > use it? I've been using Python 1.7 for years now. It is the perfect Python, with exactly all the features I want, and none that I don't want, and so much

Re: [Python-Dev] What is the rationale behind source only releases?

What does “no release at all” mean? If it’s not released, how would people use it? —Chris On Tue, May 15, 2018 at 9:36 PM Alex Walters wrote: > In the spirit of learning why there is a fence across the road before I > tear > it down out of ignorance [1], I'd like to

Re: [Python-Dev] What is the rationale behind source only releases?

> On May 16, 2018, at 1:06 AM, Ben Finney wrote: > >> >> I'd like to know the rationale behind source only releases of cpython. > > Software freedom entails the freedom to modify and build the software. > For that, one needs the source form of the software. > >

Re: [Python-Dev] What is the rationale behind source only releases?

On Wed, May 16, 2018 at 3:06 PM, Ben Finney wrote: > "Alex Walters" writes: > >> I'd like to know the rationale behind source only releases of cpython. > > Software freedom entails the freedom to modify and build the software. > For that, one

Re: [Python-Dev] What is the rationale behind source only releases?

"Alex Walters" writes: > I'd like to know the rationale behind source only releases of cpython. Software freedom entails the freedom to modify and build the software. For that, one needs the source form of the software. Portable software should be feasible to build