Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #207876 > unrolled thread

Obtaining/compiling/installing python3.7

Back to article view | Back to linux.debian.user

Contents

  Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-26 19:50 +0200
    Re: Obtaining/compiling/installing python3.7 Brian <ad44@cityscape.co.uk> - 2019-04-26 20:20 +0200
    Re: Obtaining/compiling/installing python3.7 Joe <joe@jretrading.com> - 2019-04-26 20:40 +0200
      Re: Obtaining/compiling/installing python3.7 Cindy Sue Causey <butterflybytes@gmail.com> - 2019-04-26 21:40 +0200
        Re: Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-27 08:30 +0200
    Re: Obtaining/compiling/installing python3.7 Darac Marjal <mailinglist@darac.org.uk> - 2019-04-26 21:30 +0200
      Re: Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-27 08:50 +0200
        Re: Obtaining/compiling/installing python3.7 Curt <curty@free.fr> - 2019-04-27 09:50 +0200
          Re: Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-27 13:30 +0200
        Re: Obtaining/compiling/installing python3.7 Brian <ad44@cityscape.co.uk> - 2019-04-27 12:20 +0200
        Re: Obtaining/compiling/installing python3.7 Brian <ad44@cityscape.co.uk> - 2019-04-27 16:20 +0200
    Re: Obtaining/compiling/installing python3.7 deloptes <deloptes@gmail.com> - 2019-04-26 21:50 +0200
      Re: Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-27 09:00 +0200
    Re: Obtaining/compiling/installing python3.7 Kushal Kumaran <kushal@locationd.net> - 2019-04-27 04:30 +0200
      Re: Obtaining/compiling/installing python3.7 Richard Owlett <rowlett@cloud85.net> - 2019-04-27 09:00 +0200

#207876 — Obtaining/compiling/installing python3.7

I wish to try some beta software which assumes python3.7 is installed. I 
have Debian 9.8 installed on a machine dedicated to this exercise. I did 
a web search and got a half dozen on topic hits. There were enough 
differences that I wasn't sure if I was missing something important. The 
last time I compiled something was on a PDP 11/45 in approximately 1975.

Suggestions?
TIA

[toc] | [next] | [standalone]

#207877

On Fri 26 Apr 2019 at 12:42:04 -0500, Richard Owlett wrote:

> I wish to try some beta software

Very informative.

>                                  which assumes python3.7 is installed. I
> have Debian 9.8 installed on a machine dedicated to this exercise. I did a
> web search

For what?

>            and got a half dozen on topic hits. There were enough differences
> that I wasn't sure if I was missing something important.

Differences in what? You? Miss something? Surely not?

>                                                          The last time I
> compiled something was on a PDP 11/45 in approximately 1975.

So?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#207879

On Fri, 26 Apr 2019 12:42:04 -0500
Richard Owlett <rowlett@cloud85.net> wrote:

> I wish to try some beta software which assumes python3.7 is
> installed. I have Debian 9.8 installed on a machine dedicated to this
> exercise. I did a web search and got a half dozen on topic hits.
> There were enough differences that I wasn't sure if I was missing
> something important. The last time I compiled something was on a PDP
> 11/45 in approximately 1975.
> 
>
You mentioned that you considered LFS. If you have the time, that's
a real baptism of fire as far as compiling things goes. There were
automatic systems being developed when I was interested, but as far as
I can see, there's no point to LFS if you're just going to push a
button. I did it twice, mainly to learn what I could, with better
understanding the second time, the first try was basically just
following instructions. Lots of them. My firewall pseudo-daemon (until
systemd) was nicked from the basic LFS init script.

As it happens, the first Linux magazine I bought contained an article on
compiling kernels, so I did. Not until later did I find that it is
thought to be difficult. I didn't understand many of the modules, but
with a kernel, when in doubt say 'yes'. I think that was around Red Hat
5 (*not* RHEL).

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#207882

On 4/26/19, Joe <joe@jretrading.com> wrote:
> On Fri, 26 Apr 2019 12:42:04 -0500
> Richard Owlett <rowlett@cloud85.net> wrote:
>
>> I wish to try some beta software which assumes python3.7 is
>> installed. I have Debian 9.8 installed on a machine dedicated to this
>> exercise. I did a web search and got a half dozen on topic hits.
>> There were enough differences that I wasn't sure if I was missing
>> something important. The last time I compiled something was on a PDP
>> 11/45 in approximately 1975.
>>
>>
> You mentioned that you considered LFS. If you have the time, that's
> a real baptism of fire as far as compiling things goes. There were
> automatic systems being developed when I was interested, but as far as
> I can see, there's no point to LFS if you're just going to push a
> button. I did it twice, mainly to learn what I could, with better
> understanding the second time, the first try was basically just
> following instructions. Lots of them. My firewall pseudo-daemon (until
> systemd) was nicked from the basic LFS init script.


Just finished downloading all [tarballs], except maybe 1/2 of the
kernel, just last night. This is Round 2 for me. I got through Chapter
5 then #Life poked its nose into the mix.

Oh, and I just remembered... my brain blew a circuit over working
through the package manager process, too. I think of that frequently
when package manager questions come up here at Debian-User..

The testing part will be where I focus my curiosity this time. Do the
tests, yada-yada, keep on movin' on WHEN they fail. LOL. My memory is
that some of the "it's ok to fail" was that we hadn't installed
pertinent packages yet so there was no way it would ever not fail.

That repetition helps instill each point in the
compilation/installation process. The mantra back in early 2000's was,
"Eh, it's ok not to test, just keep going" That was talking about
compiling a single package on a pre-existing system.

If you follow the Linux From Scratch support list, you see why it's
not so ok. Occasional related user questions show typos and such would
have absolutely destroyed those users' entire install, thus wasting a
TON of time, had they either skipped testing or had they failed a test
and kept going anyway instead of questioning what failed. :)

Makes you a better advocate for doing things the right way.. I never
once md5sum'ed ANYTHING *ALL THESE YEARS*. As simple as the process
turned out to be, I could never find a HOWTO that made sense.

These days, that md5ums list is serving double duty by performing the
chore of instantly advising if packages are expired and need updated
simply because they don't get checked off as OK. Match any fails to
that HANDY wget-list that's also provided, and, chick-a-BOOM, you're
off and running toward Linux knowledge self-empowerment just that
quick (depending on Internet connection speed, of course.... of
course). :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#207892

On 04/26/2019 02:32 PM, Cindy Sue Causey wrote:
> On 4/26/19, Joe <joe@jretrading.com> wrote:
>> On Fri, 26 Apr 2019 12:42:04 -0500
>> Richard Owlett <rowlett@cloud85.net> wrote:
>>
>>> I wish to try some beta software which assumes python3.7 is
>>> installed. I have Debian 9.8 installed on a machine dedicated to this
>>> exercise. I did a web search and got a half dozen on topic hits.
>>> There were enough differences that I wasn't sure if I was missing
>>> something important. The last time I compiled something was on a PDP
>>> 11/45 in approximately 1975.
>>>
>>>
>> You mentioned that you considered LFS. If you have the time, that's
>> a real baptism of fire as far as compiling things goes. There were
>> automatic systems being developed when I was interested, but as far as
>> I can see, there's no point to LFS if you're just going to push a
>> button. I did it twice, mainly to learn what I could, with better
>> understanding the second time, the first try was basically just
>> following instructions. Lots of them. My firewall pseudo-daemon (until
>> systemd) was nicked from the basic LFS init script.
> 
> 
> Just finished downloading all [tarballs], except maybe 1/2 of the
> kernel, just last night. This is Round 2 for me. I got through Chapter
> 5 then #Life poked its nose into the mix.
> 
> Oh, and I just remembered... my brain blew a circuit over working
> through the package manager process, too. I think of that frequently
> when package manager questions come up here at Debian-User..
> 
> The testing part will be where I focus my curiosity this time. Do the
> tests, yada-yada, keep on movin' on WHEN they fail. LOL. My memory is
> that some of the "it's ok to fail" was that we hadn't installed
> pertinent packages yet so there was no way it would ever not fail.
> 
> That repetition helps instill each point in the
> compilation/installation process. The mantra back in early 2000's was,
> "Eh, it's ok not to test, just keep going" That was talking about
> compiling a single package on a pre-existing system.
> 
> If you follow the Linux From Scratch support list, you see why it's
> not so ok. Occasional related user questions show typos and such would
> have absolutely destroyed those users' entire install, thus wasting a
> TON of time, had they either skipped testing or had they failed a test
> and kept going anyway instead of questioning what failed. :)
> 
> Makes you a better advocate for doing things the right way.. I never
> once md5sum'ed ANYTHING *ALL THESE YEARS*. As simple as the process
> turned out to be, I could never find a HOWTO that made sense.
> 
> These days, that md5ums list is serving double duty by performing the
> chore of instantly advising if packages are expired and need updated
> simply because they don't get checked off as OK. Match any fails to
> that HANDY wget-list that's also provided, and, chick-a-BOOM, you're
> off and running toward Linux knowledge self-empowerment just that
> quick (depending on Internet connection speed, of course.... of
> course). :)
> 
> Cindy :)
> 

Yes LFS is in my future
I would have been better off if I had done that rather trying to get 
"work" done by plunging into Debian initially. Life is for learning. 
Retirement makes time available ;/

[toc] | [prev] | [next] | [standalone]

#207881

On 26/04/2019 18:42, Richard Owlett wrote:
> I wish to try some beta software which assumes python3.7 is installed.
> I have Debian 9.8 installed on a machine dedicated to this exercise. I
> did a web search and got a half dozen on topic hits. There were enough
> differences that I wasn't sure if I was missing something important.
> The last time I compiled something was on a PDP 11/45 in approximately
> 1975.
>
> Suggestions?
> TIA
>
>
If you're beta testing the application, you may need to beta-test the OS
for it, too:

https://packages.debian.org/search?keywords=python3.7

python3.7 is available in testing.

Alternatively, if you want to be able to run python3.7 alongside your
system python, why not run it in a docker?

https://quay.io/repository/python-devs/ci-image

[toc] | [prev] | [next] | [standalone]

#207893

On 04/26/2019 02:25 PM, Darac Marjal wrote:
> 
> On 26/04/2019 18:42, Richard Owlett wrote:
>> I wish to try some beta software which assumes python3.7 is installed.
>> I have Debian 9.8 installed on a machine dedicated to this exercise. I
>> did a web search and got a half dozen on topic hits. There were enough
>> differences that I wasn't sure if I was missing something important.
>> The last time I compiled something was on a PDP 11/45 in approximately
>> 1975.
>>
>> Suggestions?
>> TIA
>>
>>
> If you're beta testing the application, you may need to beta-test the OS
> for it, too:
> 
> https://packages.debian.org/search?keywords=python3.7
> 
> python3.7 is available in testing.

Using Buster was my original idea but it's not ready in ways important 
to me. I had been looking for Python3.7 in backports. What snags might I 
hit attempting to use a testing package in stable? I'm using an isolated 
system so I can take some risks.

> 
> Alternatively, if you want to be able to run python3.7 alongside your
> system python, why not run it in a docker?

I've seen the term "docker". Looks about time to see just what it is. I 
see a reading assignment in my near future. It may solve some unrelated 
problems.

> 
> https://quay.io/repository/python-devs/ci-image
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#207897

On 2019-04-27, Richard Owlett <rowlett@cloud85.net> wrote:
>> 
>> https://packages.debian.org/search?keywords=python3.7
>> 
>> python3.7 is available in testing.
>
> Using Buster was my original idea but it's not ready in ways important 
> to me. I had been looking for Python3.7 in backports. What snags might I 
> hit attempting to use a testing package in stable? I'm using an isolated 
> system so I can take some risks.
>


I would do it this way (maybe not the very best way because I'm pretty
ignorant):

https://tecadmin.net/install-python-3-7-on-ubuntu-linuxmint/

The essential thing is not to touch or overwrite the default python
installation in /usr/bin/python, which would break certain things (or
many things) as I think you've already kind of discovered earlier, maybe.

This would be the frankensnag in installing the testing package,
creating a hybrid monster of a distro that might attack your
grandchildren when you're not looking (python being rather integral to 
the running OS, I think).

A docker instance (of which I know next to nothing) would be completely
sandboxed (if that is the term) and sans danger, in my understanding of
it. In that regard, why people don't run or suggest a docker Firefox
(which I believe exists somewhere) to assuage security concerns I'm
uncertain (perhaps more trouble than it's worth). 

-- 
The major, who had been a great fencer, did not believe in bravery, and spent
much time while we sat in the machines correcting my grammar. He had
complimented me on how I spoke Italian, and we talked together very easily. One
day I had said that Italian seemed such an easy language to me that I could not
take a great interest in it; everything was so easy to say. "Ah, yes," the
major said. "Why, then, do you not take up the use of grammar?" - "Another Country"

[toc] | [prev] | [next] | [standalone]

#207902

On 04/27/2019 02:45 AM, Curt wrote:
> On 2019-04-27, Richard Owlett <rowlett@cloud85.net> wrote:
>>>
>>> https://packages.debian.org/search?keywords=python3.7
>>>
>>> python3.7 is available in testing.
>>
>> Using Buster was my original idea but it's not ready in ways important
>> to me. I had been looking for Python3.7 in backports. What snags might I
>> hit attempting to use a testing package in stable? I'm using an isolated
>> system so I can take some risks.
>>
> 
> 
> I would do it this way (maybe not the very best way because I'm pretty
> ignorant):
> 
> https://tecadmin.net/install-python-3-7-on-ubuntu-linuxmint/
> 
> The essential thing is not to touch or overwrite the default python
> installation in /usr/bin/python, which would break certain things (or
> many things) as I think you've already kind of discovered earlier, maybe.
> 
> This would be the frankensnag in installing the testing package,

For the benefit of those reading this thread in future
see https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

> creating a hybrid monster of a distro that might attack your
> grandchildren when you're not looking (python being rather integral to
> the running OS, I think).
> 
> A docker instance (of which I know next to nothing) would be completely
> sandboxed (if that is the term) and sans danger, in my understanding of
> it. In that regard, why people don't run or suggest a docker Firefox
> (which I believe exists somewhere) to assuage security concerns I'm
> uncertain (perhaps more trouble than it's worth).
> 

It has been suggested on a LUG which I follow.
I've gotten a significant reading assignment there.
I think it is something I want in my "toolbox".

Besides:
If retirement isn't for learning, what use is it :}

[toc] | [prev] | [next] | [standalone]

#207900

On Sat 27 Apr 2019 at 01:47:53 -0500, Richard Owlett wrote:

> On 04/26/2019 02:25 PM, Darac Marjal wrote:
> > 
> > python3.7 is available in testing.
> 
> Using Buster was my original idea but it's not ready in ways important to
> me. I had been looking for Python3.7 in backports. What snags might I hit
> attempting to use a testing package in stable? I'm using an isolated system
> so I can take some risks.

Install stretch; base system only. Change sources.list to buster.
Update and upgrade. python3.7 is installed as part of the upgrade.
No snags and completely risk-free. Thirty minutes work at most.

Advising on what else is needed to test the beta software is not
possible as the package name is unknown.

I think this ticks all the boxes apart from compiling. But why
bother compiling when someone has done it for you and buster is
as ready for anything as stretch is?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#207903

On Sat 27 Apr 2019 at 01:47:53 -0500, Richard Owlett wrote:

> On 04/26/2019 02:25 PM, Darac Marjal wrote:
> > 
> Using Buster was my original idea but it's not ready in ways important to
> me. I had been looking for Python3.7 in backports. What snags might I hit
> attempting to use a testing package in stable? I'm using an isolated system
> so I can take some risks.

Install Python3.7 on stretch? Fifteen minutes work at the most,
and a learning experience into the bargain.

Install stretch; base system only. Change sources.list to buster.
Update and install python3.7. Seven new packages and six upgraded
packages. Not bad at all. Not a snag in sight. Revert the previous
change to sources.list.

How this unknown beta software behaves on such a system would be
interesting to know.

No compilation box ticked because Debian did it all.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#207883

Richard Owlett wrote:

> I wish to try some beta software which assumes python3.7 is installed. I
> have Debian 9.8 installed on a machine dedicated to this exercise. I did
> a web search and got a half dozen on topic hits. There were enough
> differences that I wasn't sure if I was missing something important. The
> last time I compiled something was on a PDP 11/45 in approximately 1975.
> 
> Suggestions?
> TIA

Try the pip python repositories
https://docs.python.org/3/installing/index.html#install-pip-in-versions-of-python-prior-to-python-3-4

I recall I used it with ansible on debian with 2.7 where I needed python3.
I am not sure it will give you exactly what you need, but may be it would.

[toc] | [prev] | [next] | [standalone]

#207896

On 04/26/2019 02:39 PM, deloptes wrote:
> Richard Owlett wrote:
> 
>> I wish to try some beta software which assumes python3.7 is installed. I
>> have Debian 9.8 installed on a machine dedicated to this exercise. I did
>> a web search and got a half dozen on topic hits. There were enough
>> differences that I wasn't sure if I was missing something important. The
>> last time I compiled something was on a PDP 11/45 in approximately 1975.
>>
>> Suggestions?
>> TIA
> 
> Try the pip python repositories
> https://docs.python.org/3/installing/index.html#install-pip-in-versions-of-python-prior-to-python-3-4

It looks like https://docs.python.org/3/ is where I should start. A 
quick browse suggests it will answer questions I hadn't thought of yet. 
Thanks for the link.

> 
> I recall I used it with ansible on debian with 2.7 where I needed python3.
> I am not sure it will give you exactly what you need, but may be it would.
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#207891

Richard Owlett <rowlett@cloud85.net> writes:

> I wish to try some beta software which assumes python3.7 is
> installed. I have Debian 9.8 installed on a machine dedicated to this
> exercise. I did a web search and got a half dozen on topic hits. There
> were enough differences that I wasn't sure if I was missing something
> important. The last time I compiled something was on a PDP 11/45 in
> approximately 1975.
>
> Suggestions?
> TIA

https://github.com/pyenv/pyenv#installation

-- 
regards,
kushal

[toc] | [prev] | [next] | [standalone]

#207894

On 04/26/2019 09:26 PM, Kushal Kumaran wrote:
> Richard Owlett <rowlett@cloud85.net> writes:
> 
>> I wish to try some beta software which assumes python3.7 is
>> installed. I have Debian 9.8 installed on a machine dedicated to this
>> exercise. I did a web search and got a half dozen on topic hits. There
>> were enough differences that I wasn't sure if I was missing something
>> important. The last time I compiled something was on a PDP 11/45 in
>> approximately 1975.
>>
>> Suggestions?
>> TIA
> 
> https://github.com/pyenv/pyenv#installation

Looks like another valuable reading assignment.
Thanks.

> 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web