public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: compiling an actual version of python
Date: Fri, 06 Feb 2015 00:37:23 +0100	[thread overview]
Message-ID: <1423179443.17371.171.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <54D371BF.6060207@redcor.ch>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

Hello,

indeed the Python version is not the most recent one. And that answers
your question as well: No one is currently working on an update of this,
but we would be happy if you would look into that and send us the
patches.

Generally I don't see any problems you might expect. Please stick to the
latest version of Python 2.7 as most (if not all) python code that we
use in IPFire is not compatible with Python 3.x.

If there are any questions, feel free to consult us here on this list.
Arne already pointed you to where to start from.

-Michael

On Thu, 2015-02-05 at 14:35 +0100, robert rottermann wrote:
> Hi Michael,
> On 05.02.2015 14:23, Michael Tremer wrote:
> > Hello Robert,
> >
> > IPFire already comes with Python on board.
> yes, I know that
> >
> > [root(a)ipfire ~]# python
> > Python 2.7.3 (default, Aug 23 2013, 19:24:00)
> > [GCC 4.4.7] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> > What are you missing and what do you want to do?
> actual is 2.7.9, which has some features not available in 2.7.3
> 
> actually I would like to install some python libraries, and to install 
> them I need an actual version of the setup tools..
> But they do not run under 2.7.3 ..
> 
> robert
> 
> >
> > -Michael
> >
> > On Thu, 2015-02-05 at 11:03 +0100, robert rottermann wrote:
> >> Hi ,
> >>
> >> I am new to this list and would like to say hi to everybody.
> >>
> >> As I am an old python hand, I would like to have an actual python
> >> running on ipfire.
> >> So that will be my first attempt to get my feet wet with developing for
> >> ipfire.
> >>
> >> now my question: is such an project already in the works by somebody of you?
> >>
> >> thanks
> >> robert
> >> _______________________________________________
> >> Development mailing list
> >> Development(a)lists.ipfire.org
> >> http://lists.ipfire.org/mailman/listinfo/development
> >
> 


  reply	other threads:[~2015-02-05 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 10:03 robert rottermann
2015-02-05 13:23 ` Michael Tremer
2015-02-05 13:35   ` robert rottermann
2015-02-05 23:37     ` Michael Tremer [this message]
2015-02-07 11:37       ` robert rottermann
2015-02-07 12:23         ` Michael Tremer
     [not found] <54D65F7A.7050700@redcor.ch>
2015-02-07 18:56 ` Michael Tremer
2015-02-08  8:42   ` robert rottermann
2015-02-09 11:26     ` Arne Fitzenreiter

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1423179443.17371.171.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox