On Mon, Feb 16, 2015 at 10:50 PM, Blaxton
wrote:
> I am using the spec file that comes with Python source code which downloaded
> from python.org website
> source file is set on spec file to file with bz2 format while there is only
> .xz and zipped are available to download.
>
>
> I thought someho
I am using the spec file that comes with Python source code which downloaded
from python.org website
source file is set on spec file to file with bz2 format while there is only .xz
and zipped are available to download.
I thought somehow some one from development team has wrote that .spec fileand
Blaxton writes:
> I am having problem building Python RPM on AIX and I think there
> are several bugs in Python .spec files.
This list is for development *of* Python, not development *with*
Python. In this case, you would probably be better off with an AIX
list devoted to packaging, an RPM-spe
On 15 February 2015 at 17:46, Daniel Holth wrote:
> Go ahead, make my pep.
>
> I will appreciate seeing it happen.
Here is a draft update for PEP 441. It's still a work in progress - in
particular I want to wait for consensus on the issue of the default
interpreter before finalising it. But I tho
2015-02-16 17:34 GMT+01:00 Stefan Krah :
>
> On Mon, Feb 16, 2015 at 11:35:52AM +, serhiy.storchaka wrote:
>> diff --git a/Modules/_testbuffer.c b/Modules/_testbuffer.c
>> --- a/Modules/_testbuffer.c
>> +++ b/Modules/_testbuffer.c
>> @@ -850,7 +850,7 @@
>> Py_ssize_t *dest;
>> Py_ssiz
Paul Moore wrote:
The alternative, I guess, is to have *no* default and write no shebang
unless -p is specified.
+1. That sounds like a very good idea to me.
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/li
On Mon, Feb 16, 2015 at 11:35:52AM +, serhiy.storchaka wrote:
> diff --git a/Modules/_testbuffer.c b/Modules/_testbuffer.c
> --- a/Modules/_testbuffer.c
> +++ b/Modules/_testbuffer.c
> @@ -850,7 +850,7 @@
> Py_ssize_t *dest;
> Py_ssize_t x, i;
>
> -dest = PyMem_Malloc(len * (si
If I only have one version on my box, yes, I only use "python". But like I
said, for me personally, that situation doesn't last very long.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On 16 February 2015 at 17:00, Mark Young wrote:
> I don't know what anyone else does, but in cases where I have both on my
> windows box, I do use python2(.x) and python3(.y) . If I only have one
> version on the box, I use the generic name of course. (I don't often have
> only one version on my b
On 16 February 2015 at 16:42, Paul Moore wrote:
> My point is that on Windows, users typically don't change the
> executable name they use[1], but rather configure the "python" (or
> "py") command to do what they want. So I think that on Windows we
> should follow that convention and execute whate
Paul Moore wrote:
> On 15 February 2015 at 18:25, Petr Viktorin wrote:
>> On POSIXy systems the "python3" symlink is created in all venvs. I
>> thought (perhaps naïvely) that Windows doesn't do shebangs natively,
>> so there's some Python-specific mechanism around them, which should
>> handle "pyt
I don't know what anyone else does, but in cases where I have both on my
windows box, I do use python2(.x) and python3(.y) . If I only have one
version on the box, I use the generic name of course. (I don't often have
only one version on my boxes though. 2.x inevitably gets drug in in for
some reas
On 16 February 2015 at 16:34, Steve Dower wrote:
>> As far as I know, this is *identical* behaviour to Unix - even to the
>> incredibly
>> annoying (to me) choice of Python 2 as a default. So I reconfigure the
>> default
>> in my personal settings to Python 3. Unix users can do this too (althoug
On 02/16/2015 08:16 AM, Paul Moore wrote:
> The alternative, I guess, is to have *no* default and write no shebang
> unless -p is specified.
This seems to make sense.
> So, the options I see:
>
> 1. Stick with /usr/bin/env python
> 2. No shebang unless -p is specified
> 3. Unix users come up wi
On 15 February 2015 at 18:25, Petr Viktorin wrote:
> On POSIXy systems the "python3" symlink is created in all venvs. I
> thought (perhaps naïvely) that Windows doesn't do shebangs natively,
> so there's some Python-specific mechanism around them, which should
> handle "python3".
Windows doesn't
hi
I am having problem building Python RPM on AIX and I think there are several
bugs in Python .spec files.
README file says download the bz2 version, but only gziped and xz version
available from Python website
so had to convert the .tgz file to bz2 and copy it over to SOURCES directory.
%defin
On Mon, Feb 16, 2015 at 12:00 AM, Chris Angelico wrote:
> On Sat, Feb 14, 2015 at 11:07 AM, Nick Coghlan wrote:
>> OTOH, it may be time to reconsider our recommendation to distros as well,
>> suggesting that for Python 3.5+, we will consider it appropriate to have the
>> "python" symlink refer to
On Mon, Feb 16, 2015 at 10:47 PM, Petr Viktorin wrote:
>> If *all* distros provide a "python2" symlink, then the recommendation
>> can become "use python if it's 2/3 compatible, or python2/python3 to
>> choose", and then it won't hurt to switch python to be python3.
>> Are there known distros in w
18 matches
Mail list logo
