unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: arkhan@disroot.org
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Compiling Python 2.7.16
Date: Tue, 18 Jun 2019 15:16:57 +0000	[thread overview]
Message-ID: <cf44950d148819c911857cc9f77273b1@disroot.org> (raw)
In-Reply-To: <87pnnbng9o.fsf@elephly.net>

I get it,
I'm new to guix, so I think the question would be how can I have a workflow similar to the one with pyenv + virtualenv + emacs, using guix + emacs ..?

__
Edison

18 de junio de 2019 9:02, "Ricardo Wurmus" <rekado@elephly.net> escribió:

> Hi Edison,
> 
>> Hi,
>> 
>> I'm trying to use this https://github.com/pyenv/pyenv
>> 
>> Thanks
> 
> Please keep the mailing list in Cc.
> 
> Generally, I don’t think pyenv is going to be useful when you’re already
> using Guix.
> 
> In order to help you we need to have more information. Please provide
> answers to my previous questions. Here they are for context:
> 
>>> I'm trying to compile the version of python 2.7.16
>> 
>> How?
>> 
>>> but I get the following error
>>> 
>>> WARNING: The Python readline extension was not compiled. Missing the GNU readline lib?
>>> ERROR: The Python zlib extension was not compiled. Missing the zlib?
>> 
>> What Guix command did you run to get this error?
>> 
>>> I have installed those packages but when they die, they can not be located
>> 
>> I don’t know what this means.
> 
> --
> Ricardo

  parent reply	other threads:[~2019-06-18 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 17:36 Compiling Python 2.7.16 Edison Ibáñez
2019-06-18 12:56 ` Ricardo Wurmus
     [not found] ` <492f4be4de6405aec2c3f29f0a68cd91@disroot.org>
2019-06-18 14:02   ` Ricardo Wurmus
2019-06-18 15:16   ` arkhan [this message]
2019-06-18 15:24     ` Ricardo Wurmus
2019-06-18 15:32     ` arkhan

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=cf44950d148819c911857cc9f77273b1@disroot.org \
    --to=arkhan@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).