take a look at the kedpm PKGBUILD [1], the package have
/usr/bin/python as shebang, but if you run:
python2 setup.py
the script will automatically fix the shebangs to /usr/bin/python2
before installing
**
[1] https://aur.archlinux.org/packages/ke/kedpm/PKGBUILD
On Fri, Dec 16, 2011 at 5:30 AM,
On Thu, Dec 15, 2011 at 9:51 AM, Alex Bolgarov wrote:
>> you all think the proper fix is for
>> me to put in the docs something like "on Arch systems you need to do
>> [x] before building", whether [x] is "get the PKGBUILD with the patch
>> from AUR" or even "run the sed-python-with-python2.sh inc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/12/11 14:20, Hector Martinez-Seara wrote:
> +1 to archlinux initiative. Someone has to be the first and as
> always arch is there. Actually python, read python3, as default is
> one of the reasons I use arch. Hector
>
> On 15 December 2011 17:58
+1 to archlinux initiative. Someone has to be the first and as always
arch is there. Actually python, read python3, as default is one of the
reasons I use arch.
Hector
On 15 December 2011 17:58, Thanasis Georgiou wrote:
> Sorry I meant 'in a different path among distributions'. Forgot to
> doubl
Sorry I meant 'in a different path among distributions'. Forgot to double-check.
On 15 December 2011 17:56, Thanasis Georgiou wrote:
> Or use #!/usr/bin/env python2. This should fix problems like python2
> being in a different path among distribution.
Or use #!/usr/bin/env python2. This should fix problems like python2
being in a different path among distribution.
On 15 December 2011 17:51, Alex Bolgarov wrote:>>
you all think the proper fix is for>> me to put in the docs something
like "on Arch systems you need to do>> [x] before building", wh
> you all think the proper fix is for
> me to put in the docs something like "on Arch systems you need to do
> [x] before building", whether [x] is "get the PKGBUILD with the patch
> from AUR" or even "run the sed-python-with-python2.sh included in the
> distribution".
I personally don't think it
On Wed, Dec 14, 2011 at 08:48:25PM -0800, Evan Martin wrote:
> I just wanted to be certain that you all think the proper fix is for
> me to put in the docs something like "on Arch systems you need to do
> [x] before building", whether [x] is "get the PKGBUILD with the patch
> from AUR" or even "run
On 15/12/11 05:57, Angel Velásquez wrote:
> On 14/12/11 19:24, Evan Martin wrote:
>
>
>> 1) Is it intentional that I am unable to use software from
>> upstream like Django unmodified? Am I expected to only install
>> software from the Arch repositories, where it has been patched by
>> Arch devs
On Wed, Dec 14, 2011 at 5:44 PM, Thomas Dziedzic wrote:
> On Wed, Dec 14, 2011 at 5:19 PM, Sander Jansen wrote:
>> On Wed, Dec 14, 2011 at 5:05 PM, Thomas Dziedzic wrote:
>>> On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler
>>> wrote:
Am 14.12.2011 23:24, schrieb Evan Martin:
> What I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 19:24, Evan Martin wrote:
> Hello,
>
> I'm a recent Arch user, a refugee from Ubuntu. I was attracted to
> Arch because I was tired of Ubuntu forcing their new software on me
> -- it seemed the Arch way was to allow you to use bleeding e
On Wed, Dec 14, 2011 at 7:53 PM, Qadri wrote:
> On Wed, Dec 14, 2011 at 5:24 PM, Evan Martin wrote:
>
>> As a software developer, I am now getting contacted by users where my
>> software doesn't work on Arch. I even applied a patch submitted by an
>> Arch user to make my code use "python2" only
On Wed, Dec 14, 2011 at 5:24 PM, Evan Martin wrote:
> As a software developer, I am now getting contacted by users where my
> software doesn't work on Arch. I even applied a patch submitted by an
> Arch user to make my code use "python2" only to discover it broke my
> software on Mac and Windows
On 15 December 2011 07:44, Thomas Dziedzic wrote:
> On Wed, Dec 14, 2011 at 5:19 PM, Sander Jansen wrote:
>> On Wed, Dec 14, 2011 at 5:05 PM, Thomas Dziedzic wrote:
>>> On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler
>>> wrote:
Am 14.12.2011 23:24, schrieb Evan Martin:
> What I don't
On Wed, Dec 14, 2011 at 5:19 PM, Sander Jansen wrote:
> On Wed, Dec 14, 2011 at 5:05 PM, Thomas Dziedzic wrote:
>> On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler wrote:
>>> Am 14.12.2011 23:24, schrieb Evan Martin:
What I don't understand is why you're manually patching upstream
softw
On Wed, Dec 14, 2011 at 5:05 PM, Thomas Dziedzic wrote:
> On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler wrote:
>> Am 14.12.2011 23:24, schrieb Evan Martin:
>>> What I don't understand is why you're manually patching upstream
>>> software to rewrite references from /usr/bin/python to
>>> /usr/bi
On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler wrote:
> Am 14.12.2011 23:24, schrieb Evan Martin:
>> What I don't understand is why you're manually patching upstream
>> software to rewrite references from /usr/bin/python to
>> /usr/bin/python2. This sort of forking is exactly the sort of
>> dive
On Wed, Dec 14, 2011 at 11:57 PM, Oon-Ee Ng wrote:
> On Thu, Dec 15, 2011 at 6:54 AM, Sander Jansen wrote:
>> I think the question was whether it was a "good idea" (tm) to alias
>> python to python3 instead of python2. Then again, you can easily
>> change the alias yourself...
>>
>> Sander
>>
>
>
Am 14.12.2011 23:24, schrieb Evan Martin:
> What I don't understand is why you're manually patching upstream
> software to rewrite references from /usr/bin/python to
> /usr/bin/python2. This sort of forking is exactly the sort of
> divergence (like how Ubuntu modified their GTK to add their own
>
On 12/14/2011 05:24 PM, Evan Martin wrote:
1) Is it intentional that I am unable to use software from upstream
like Django unmodified? Am I expected to only install software
from the Arch repositories, where it has been patched by Arch devs
to work on Arch? (See below for more on Dja
On Thu, Dec 15, 2011 at 6:54 AM, Sander Jansen wrote:
> I think the question was whether it was a "good idea" (tm) to alias
> python to python3 instead of python2. Then again, you can easily
> change the alias yourself...
>
> Sander
>
Bottom-posting, please. And I believe rather than discuss this
I think the question was whether it was a "good idea" (tm) to alias
python to python3 instead of python2. Then again, you can easily
change the alias yourself...
Sander
On Wed, Dec 14, 2011 at 4:39 PM, Thomas Dziedzic wrote:
> "python2 will refer to some version of Python 2.x
> python3 will refe
"python2 will refer to some version of Python 2.x
python3 will refer to some version of Python 3.x
python should refer to the same target as python2 but may refer to
python3 on some bleeding edge distributions"
above snippet taken from: http://www.python.org/dev/peps/pep-0394/
Hello,
I'm a recent Arch user, a refugee from Ubuntu. I was attracted to
Arch because I was tired of Ubuntu forcing their new software on me --
it seemed the Arch way was to allow you to use bleeding edge if you
wanted it, but to not fork upstream.
So it was with some surprise that I discovered
24 matches
Mail list logo