On Thursday, April 16, 2015 06:45:08 PM Stefano Rivera wrote:
> Hi Scott (2015.04.15_18:30:23_+0200)
>
> > If we are sharing dist-packages, then pypy can probably use the same
> > binary when the content would be the same. Only in cases where the
> > content is different would you duplicate a sepa
Hi Scott (2015.04.15_18:30:23_+0200)
> If we are sharing dist-packages, then pypy can probably use the same
> binary when the content would be the same. Only in cases where the
> content is different would you duplicate a separate pypy package.
That works, but only for leaf packages. Transitive de
The odds of system management scripts I wrote a decade ago and haven't touched
since living in a virtualenv is approximately zero. The issue with switching
where /usr/bin/python points to python3 is to avoid problems on systems. I
don't think virtualenv is relevant. In any case, if you're usi
It's worth mentioning that in virtualenvs and conda envs, where there can
only be one version of Python installed, 'python' refers to that whether it
is Python 3 or 2. So it's already not a safe assumption that 'python'
always means Python 2, even if you discount Arch.
On 15 April 2015 at 21:04, S
On April 15, 2015 8:00:22 PM EDT, Barry Warsaw wrote:
>On Apr 15, 2015, at 04:42 PM, Scott Kitterman wrote:
>
>>Then I don't understand why the whole s/python/python2// plan in the
>shebangs
>>helps anything. As long as both exist, it's a no-op.
>
>Partly this is to begin to educate users to sto
On Apr 15, 2015, at 04:42 PM, Scott Kitterman wrote:
>Then I don't understand why the whole s/python/python2// plan in the shebangs
>helps anything. As long as both exist, it's a no-op.
Partly this is to begin to educate users to stop using /usr/bin/python, which
has unclear semantics across th
On Wednesday, April 15, 2015 11:00:53 PM Stefano Rivera wrote:
> Hi Scott (2015.04.15_22:42:26_+0200)
>
> > P.S. It would be nice if there would be a PEP that says to never ever do
> > this. I know it would make Arch have a sad, but they'll get over it.
>
> I think everyone wants to make Arch s
Hi Scott (2015.04.15_22:42:26_+0200)
> P.S. It would be nice if there would be a PEP that says to never ever do
> this. I know it would make Arch have a sad, but they'll get over it.
I think everyone wants to make Arch sad. In retaliation for them making
us sad. Apparently there were many confu
On Wednesday, April 15, 2015 02:16:58 PM Barry Warsaw wrote:
> On Apr 15, 2015, at 12:24 PM, Scott Kitterman wrote:
> >Maybe I'll mellow over time, but currently my thinking is that if there's
> >an upload to point /usr/bin/python at a python3, it will be immediately
> >followed by one where I remo
On Apr 15, 2015, at 12:24 PM, Scott Kitterman wrote:
>Maybe I'll mellow over time, but currently my thinking is that if there's an
>upload to point /usr/bin/python at a python3, it will be immediately followed
>by one where I remove myself from being maintainer. It's an idea that can
>only cause p
On April 15, 2015 11:24:30 AM EDT, Stefano Rivera wrote:
>Hi Scott (2015.04.15_17:19:39_+0200)
>> Since these pypy extension packages are new and there are no
>applications, I
>> think it would make a lot of sense to limit this to PY3. It makes
>things much
>> simpler technically. We should no
On April 15, 2015 11:17:52 AM EDT, Stefano Rivera wrote:
>Hi Scott (2015.04.15_02:17:18_+0200)
>> >Upstream Python's direction for Python paths is in favor of
>explicitly
>> >numbered
>> >/usr/bin/python2 and /usr/bin/python3. In support of this, rough
>> >consensus in
>> >the room is that /usr/bi
On Wednesday, April 15, 2015 04:54:45 PM Stefano Rivera wrote:
> Hi Scott (2015.04.15_02:17:18_+0200)
>
> > >Consensus seems to be "give it a shot" and try to see what works.
> > >There are no pypy apps, so this isn't an issue yet.
> >
> > What is the "it" that's to be given a shot? I see two cho
Hi Scott (2015.04.15_17:19:39_+0200)
> Since these pypy extension packages are new and there are no applications, I
> think it would make a lot of sense to limit this to PY3. It makes things
> much
> simpler technically. We should not recreate the symlink farm we used to have
> for python.
>
Hi Scott (2015.04.15_02:17:18_+0200)
> >Upstream Python's direction for Python paths is in favor of explicitly
> >numbered
> >/usr/bin/python2 and /usr/bin/python3. In support of this, rough
> >consensus in
> >the room is that /usr/bin/python should likely be removed *entirely*
> >from
> >shebangs
Hi Scott (2015.04.15_02:17:18_+0200)
> >Consensus seems to be "give it a shot" and try to see what works.
> >There are no pypy apps, so this isn't an issue yet.
>
> What is the "it" that's to be given a shot? I see two choices there?
Give python3 + pypy3 shared dist-packages a shot.
> Did you di
On April 14, 2015 6:01:56 PM EDT, Paul Tagliamonte wrote:
>
>=== BITS FROM THE DEBIAN PYCON HANGOUT ===
>
>
>Agenda:
>
> - Discuss how we might support multiple interpreters with Python 3
>packages, for cpython + pypy C extensions.
> - Set up a plan for the svn =>
Paul Tagliamonte writes:
> === BITS FROM THE DEBIAN PYCON HANGOUT ===
Thanks for posting this so promptly, Paul!
--
\ “Not using Microsoft products is like being a non-smoker 40 or |
`\ 50 years ago: You can choose not to smoke, yourself, but it's |
_o__)
18 matches
Mail list logo
