Date: Wed, 18 Jun 2014 10:20:48 +0200 From: Marcus von Appen <mva@freebsd.org> To: freebsd-python@freebsd.org Subject: Re: Wrong python_CMD in shebangfix? Message-ID: <20140618102048.Horde.w1CivWZQea2qzyDdsxrb4w1@webmail.df.eu> In-Reply-To: <9A0AFE0A-8150-41F9-962F-274D2C7A5694@gmail.com> References: <0AE311F0-87F8-4376-8E24-742C6C54F564@gmail.com> <20140515053140.GA920@medusa.sysfault.org> <E04D7426-A04C-4609-87C7-B789B9E8E6A7@gmail.com> <9A0AFE0A-8150-41F9-962F-274D2C7A5694@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dmitry Sivachenko <trtrmitya@gmail.com>: > Well, so what is the consensus on this? > > May I commit the proposed patch? > Sorry, I missed the mail completely. The patch should be checked against those ports, which currently use the shebangfix for python files, but do not set python_CMD explicitly. Otherwise, we may break things in a pretty bad way, since the behaviour changes. Cheers Marcus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140618102048.Horde.w1CivWZQea2qzyDdsxrb4w1>