Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #70731 > unrolled thread
| Started by | Ned Deily <nad@acm.org> |
|---|---|
| First post | 2014-04-29 12:13 -0700 |
| Last post | 2014-04-29 12:13 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: how to build and install multiple micro-level major.minor versions of Python Ned Deily <nad@acm.org> - 2014-04-29 12:13 -0700
| From | Ned Deily <nad@acm.org> |
|---|---|
| Date | 2014-04-29 12:13 -0700 |
| Subject | Re: how to build and install multiple micro-level major.minor versions of Python |
| Message-ID | <mailman.9583.1398804450.18130.python-list@python.org> |
On Apr 29, 2014, at 11:53 , Brent S. Elmer Ph.D. <webe3vt@aim.com> wrote: > Yes, I already use --prefix to build to a different path. I guess that > is what I need to do but I would rather have a way to have the build and > install process install to the micro level. Python deliberately does not provide a way to install to the micro level as an important "contract" in the Python maintenance and release process is to maintain ABI compatibility among maintenance (i.j.k) releases in the same major release series (i.j). We sometimes fail in that but we do try really hard to make it painless to move from i.j.k to i.j.x. That's also why we only supply fixes for the most recent micro release. -- Ned Deily nad@acm.org -- []
Back to top | Article view | comp.lang.python
csiph-web