On Tue, Apr 14, 2015 at 08:55:07AM +0200, Piotr Ożarowski wrote:
> > If you want python (which include /usr/bin/python), install it. If you
> > want
> > python3, then the interpreter you're looking for is found at
> > /usr/bin/python3.
> >
> > There's no dilemma to solve.
>
> +1
+1, but only
> I'm
> planning on playing notekeeper, and I'll publish a summary of what was
> discussed to this thread, if that works.
great, thanks
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A8
On Apr 14, 2015, at 12:38 AM, Scott Kitterman wrote:
>If you want python (which include /usr/bin/python), install it. If you want
>python3, then the interpreter you're looking for is found at /usr/bin/python3.
I just don't want it to fail mysteriously.
When there's no Python 2 by default, comm
On 14 April 2015 at 08:10, Barry Warsaw wrote:
> But it fails unhelpfully when you use it in a shebang.
>
> $ /tmp/foo.py
> bash: /tmp/foo.py: /usr/bin/python: bad interpreter: No such file or
> directory
>
> Let's make the latter more helpful.
>
>From a script authors point of view, it's curren
On Tuesday, April 14, 2015 08:10:49 AM Barry Warsaw wrote:
> On Apr 14, 2015, at 12:38 AM, Scott Kitterman wrote:
> >If you want python (which include /usr/bin/python), install it. If you
> >want python3, then the interpreter you're looking for is found at
> >/usr/bin/python3.
> I just don't want
On Tuesday, April 14, 2015 08:24:01 AM Thomas Kluyver wrote:
> On 14 April 2015 at 08:10, Barry Warsaw wrote:
> > But it fails unhelpfully when you use it in a shebang.
> >
> > $ /tmp/foo.py
> > bash: /tmp/foo.py: /usr/bin/python: bad interpreter: No such file or
> > directory
> >
> > Let's make
On 14 April 2015 at 08:57, Scott Kitterman wrote:
> I have scripts I use locally that are untouched in almost a decade that use
> /usr/bin/python.
I'm thinking about scripts that are written and distributed to people
running on different, unknown, Linux distros. Obviously if you're only
targeti
On Tuesday, April 14, 2015 09:22:22 AM Thomas Kluyver wrote:
> On 14 April 2015 at 08:57, Scott Kitterman wrote:
> > I have scripts I use locally that are untouched in almost a decade that
> > use
> > /usr/bin/python.
>
> I'm thinking about scripts that are written and distributed to people
> run
On 2015-04-14 at 09:22:22 -0400, Thomas Kluyver wrote:
> I'm thinking about scripts that are written and distributed to people
> running on different, unknown, Linux distros. Obviously if you're only
> targeting your own machines, there's no problem. But if you want to write a
> script that will wo
On Tue, Apr 14, 2015 at 10:00:07AM -0400, Scott Kitterman wrote:
> It is, as I think it was you said, easy enough to write Python code these
> days
> that works for both python and python3. As an upstream developer, go ahead
> and do that and leave it to the distros to packageit appropriately f
I'm trying to make sure I understand this subthread correctly. Is the
following an accurate summary of the desires?
1. It should be possible, in Debian, not to ship Python 2 by default in
the near future, and to remove Python 2 from the archive in the far
future.
2. A huge number of existing
Hi debian-python (2015.04.13_22:17:03_+0200)
> Matthias and I are planning to have a Debian Python BoF at PyCon,
> tomorrow afternoon. I think lunch is 2pm, so 3pm?
>
> Meet outside the cPython sprint room?
In case you didn't see the private mails:
We've got a table in room 513b.
Still on for 3
=== 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 => git migration
- Python 2 "deprecation"
- /usr/bin/pytho
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__)
Paul Tagliamonte writes:
> SVN => GIT
> --
> "We should just do it!"
+1
[…]
> All present felt strongly that we should always use pristine upstream
> tarballs as released by upstreams, with pristine-tar.
I'm glad of the former. I don't use ‘pristine-tar’, though.
I use the “m
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 =>
16 matches
Mail list logo
