From owner-freebsd-python@FreeBSD.ORG Wed May 27 19:58:45 2009 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F04E1065670 for <python@freebsd.org>; Wed, 27 May 2009 19:58:45 +0000 (UTC) (envelope-from ctrachte@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 283968FC16 for <python@freebsd.org>; Wed, 27 May 2009 19:58:44 +0000 (UTC) (envelope-from ctrachte@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so2608774ana.13 for <python@freebsd.org>; Wed, 27 May 2009 12:58:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=NyCRMopAYrGotgaKIP9J1fefH9qhkLkF8qDcFFHEI2E=; b=A3oSIGPhEIaGpZtbWsaxN09itu1hqsg89tV9Unzzv/VIFpFQJnKasiDukvQbITRA2Z Lb80iEod7w9LnhCrw+M82YJqQ+dOn+fN6/irOq9gJixiNihsX/lAPsMi6BlebUFg4tCP a3pgKPTouBoCaPTnH6sc0l30Nb6QshDqnil+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=TGQ9KF6nP86WHwEic3mXTq6A9Ll+YDxGTthdwE4AehTsiRrKdQBy4XJWXi2C9OiEWV nvw8fjhERpt8GerG88Ly5Ut6Xlefyd8OsKX4nk9Rj+dLL4f6/I4uefcck2P4AHQusKcp 2myGnNTDALLLFVcvfj8QwHLPjOkUD/zRBna9I= MIME-Version: 1.0 Received: by 10.100.141.15 with SMTP id o15mr680519and.20.1243452934249; Wed, 27 May 2009 12:35:34 -0700 (PDT) In-Reply-To: <426ada670905271233t1f9ec929wab858f7a9d35d683@mail.gmail.com> References: <20090517165416.GW71804@bsdcrew.de> <4f615770905262030r71075f5bmc1bc41417d878313@mail.gmail.com> <4A1D7F2D.5010803@FreeBSD.org> <426ada670905271233t1f9ec929wab858f7a9d35d683@mail.gmail.com> Date: Wed, 27 May 2009 13:35:34 -0600 Message-ID: <426ada670905271235p65ae3be9m922955fd6382181c@mail.gmail.com> From: Carl Trachte <ctrachte@gmail.com> To: python@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Fwd: [CFT] FreeBSD python25 move to python26 as default version. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 27 May 2009 19:58:45 -0000 Sorry, neglected to post to list. CBT ---------- Forwarded message ---------- From: Carl Trachte <ctrachte@gmail.com> Date: Wed, May 27, 2009 at 1:33 PM Subject: Re: [CFT] FreeBSD python25 move to python26 as default version. To: Doug Barton <dougb@freebsd.org> On Wed, May 27, 2009 at 11:58 AM, Doug Barton <dougb@freebsd.org> wrote: > Kelly Hays wrote: >> On Sun, May 17, 2009 at 11:54 AM, Martin Wilke <miwi@freebsd.org> wrote: >>> =A0 =A0Once the installed Python has been updated to 2.6, by using one = of the >>> =A0 =A0methods above, it is required to run the upgrade-site-packages t= arget in >>> =A0 =A0lang/python to assure that site-packages are made available to t= he new Python >>> =A0 =A0version. >>> >>> =A0 =A0# cd /usr/ports/lang/python && make upgrade-site-packages >>> >>> This Makefile target requires ports-mgmt/portupgrade to be installed. >>> >> A lot of us are no longer using ports-mgmt/portupgrade in favor of >> ports-mgmt/portmaster. Please support both tools. > > First, I don't use python, so I'm not directly affected by this. > Second, I don't think it's reasonable to _require_ that a user needs > to use any additional tools (such as portupgrade or portmaster) to do > something with the ports system. I do think it's reasonable to provide > instructions such as, "If you use toolA, do X, for toolB do Y, and if > you don't use a tool do Z, etc." > > That said, if someone can explain what it is that needs to be done, I > will be glad to help write instructions for doing it with portmaster. > > > Doug > > -- > > =A0 =A0This .signature sanitized for your protection > > _______________________________________________ > freebsd-python@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-python > To unsubscribe, send any mail to "freebsd-python-unsubscribe@freebsd.org" > I'm a pretty much a newb to BSD and have not contributed to the ports collection; apologies if I'm off track on the thread. The Python source build has IIRC an altinstall flag that allows you to have multiple versions on the machine. =A0I've got the Python from ports (I believe it's 2.5) and Python 3.0 (installed from source with altinstall) on my FreeBSD laptop. =A0I was surprised that a port for 2.6 was going to be available so soon (thanks). =A0I'm not sure if the method I've laid out for 3.0 is considered good practice within a FreeBSD context, but it's handy for having more than one version of Python on a machine. The advantage of doing the install with ports is that there is some assurance as to the security and functionality of the software (it will work under the FreeBSD OS). =A0If there is a dependence within the port, even one just required to build the port or use its Makefile, as a newb at least, I expect it to show up in the port's dependencies. My 2 cents of a possibly relevant nature. Carl T.