From: Cyril Roelandt <tipecaml@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Python
Date: Fri, 13 Sep 2013 18:25:00 +0200 [thread overview]
Message-ID: <52333C5C.4010008@gmail.com> (raw)
In-Reply-To: <20130913154607.GA5258@debian>
On 09/13/2013 05:46 PM, Andreas Enge wrote:
> Hello,
>
> recently I added a few more python packages, and things seem to work well
> (except for the surprising realisation that more projects than not seem to
> still depend on python 2 instead of python 3). So I do not expect big changes
> to the python build system in the near future.
This does not come as a surprise to Pythonists, unfortunately :/
>
> I considered switching from python 3.3.2 to 3.4, but the available versions
> are 3.4.0a1 and 3.4.0a2, which does not inspire too much confidence; maybe
> we should wait for 3.4.1.
>
See http://www.python.org/download/ : we should stick to 3.3.2.
> So I would suggest to merge the branch python into master. I did a test
> merge, and there were no conflicts.
>
> What do you think?
>
I agree with you.
Cyril.
next prev parent reply other threads:[~2013-09-13 16:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:46 Python Andreas Enge
2013-09-13 16:25 ` Cyril Roelandt [this message]
2013-09-14 9:02 ` Python Andreas Enge
2013-09-13 21:32 ` Python Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2023-02-12 9:05 Merging core-updates? Julien Lepiller
2023-02-13 20:35 ` Andreas Enge
2023-02-19 11:02 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 11:15 ` Andreas Enge
2023-02-19 11:19 ` Andreas Enge
2023-02-19 15:10 ` Attila Lendvai
2023-02-21 16:24 ` Python Andreas Enge
2023-02-19 11:30 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 20:31 ` Python Andreas Enge
2023-02-21 16:41 ` Python Andreas Enge
2023-02-22 14:23 ` Python Andreas Enge
2023-02-23 15:16 ` Python Andreas Enge
2023-02-24 16:47 ` Python Andreas Enge
2023-02-24 16:51 ` Python Andreas Enge
2023-02-24 18:08 ` Python Lars-Dominik Braun
2023-02-25 15:15 ` Python Andreas Enge
2023-02-25 15:45 ` Python Lars-Dominik Braun
2023-02-25 16:39 ` Python Andreas Enge
2023-02-25 16:56 ` Python Lars-Dominik Braun
2023-02-25 18:00 ` Python Andreas Enge
2023-02-25 18:06 ` Python Andreas Enge
2023-02-25 18:15 ` Python Andreas Enge
2023-02-25 18:33 ` Python Andreas Enge
2023-02-27 19:14 ` Python Lars-Dominik Braun
2023-02-28 15:05 ` Python Andreas Enge
2023-02-25 18:29 ` Python Andreas Enge
2023-03-11 11:20 ` Python Andreas Enge
2023-03-11 11:44 ` Python Andreas Enge
2023-03-15 13:49 ` Python Andreas Enge
2023-03-18 8:59 ` Python Lars-Dominik Braun
2023-03-18 9:15 ` Python Andreas Enge
2023-03-18 10:02 ` Python Lars-Dominik Braun
2023-03-18 10:13 ` Python Andreas Enge
2023-03-18 9:43 ` Python Lars-Dominik Braun
2023-03-18 19:37 ` Python Andreas Enge
2023-03-21 18:56 ` Python Lars-Dominik Braun
2023-03-30 9:57 ` Python Lars-Dominik Braun
2023-03-30 10:10 ` Python Andreas Enge
2023-03-30 11:05 ` Python Lars-Dominik Braun
2023-03-31 8:52 ` Python Andreas Enge
2023-02-27 18:55 ` Python Efraim Flashner
2023-02-27 19:12 ` Python Lars-Dominik Braun
2023-02-19 11:47 ` Python (was: Merging core-updates?) Lars-Dominik Braun
2023-02-19 11:57 ` Andreas Enge
2023-02-19 15:50 ` Lars-Dominik Braun
2023-02-19 20:27 ` Python Andreas Enge
2023-02-25 17:44 ` Python Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52333C5C.4010008@gmail.com \
--to=tipecaml@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).