从“MacPython”转换到MacPorts python3一个好主意EIN& SciPy的？ [英] Transition from "MacPython" to MacPorts python3 a good idea for EIN & Scipy?
问题描述
我开始在OS X 10.6（Snow Leopard）上学习Python，其中有一个python.org Python dmg 。我认为我在SO上看到过这样的MacPython，但我也在想，（目前Google的MacPython最受欢迎）是不同的，对不对？
虽然我觉得我的python.org Python 3.3 .0安装对我来说工作相当合适（使用分发， easy_install 和 pip ，我安装了几个新软件包，包括 IPython ），我想开始使用 Emacs IPython Notebook（EIN）和 Scipy ，很明显，这种安排将需要很多额外的东西从 CheeseShop 。另外，我非常高兴地为GNU Emacs和其他unix（非Python）软件包使用 MacPorts 很长一段时间，所以我认为将python.org安装和MacPorts Python中的所有Python工作（我专注于学习py3）都是一个好主意。 p>
这是个好主意？ IOW，我可能会为自己做很多额外的时间/工作/头痛（像@davidavr写的关于这里，当他写道：MacPorts将下拉并安装完整的Python 2.4发行版与库。）获得很少的收益或者是使用像MacPorts这样的软件包管理器的好处，我的Python的东西会像我怀疑它可能是一个大的时间片。
我已经读了很多其他的线程这里（最相当老的）部分相关，但不觉得最近有什么真正解决我的问题，我遇到了很多老的建议，很明显，较新的建议是冲突的，所以我问什么可能被认为是重复的，但如果是，我不禁想到几年的过去可能已经改变了一些对旧的类似问题的答案。
尝试使用MacPorts和pip3很多日子，最终无法获得功能性的IPython笔记本电脑/ qtconsole与matplotlib和numpy和同情和所有那些美好的东西，我放弃了并切换到自制软件，最终为我工作，但我不得不从源码对于几个更大的包。虽然自制软件会安装这些软件包，但是对于Python 2.7而言，它似乎是严格执行的，而对于Python3来说似乎是这样做的。我在自制软件中尝试了几个选项来解决这个问题，但是最终放弃了，刚刚从源代码安装了像Qt这样的困难软件包。
所以我想我的经验是MacPorts pip3对我的特定目标来说不是一个好主意，而使用pip3的自制软件更好，但对于使用Python3的Scipy软件包仍然不完整。 （虽然也许如果我尝试从源码安装补充MacPorts的方式，我用自制软件的方式，然后MacPorts也将足够。）
回顾经验，我想对于新用户来说，如何从头开始并构建这些功能非常需要更详细和全面的文档，因为我尝试了许多不同的策略，最终只能通过尝试和错误以及来自所有方面的许多不同的建议在网络上，我终于得到了一些它。我仍然没有EIN，但是我认为这将严格要求emacs世界的工具来实现。 EIN文档强烈地鼓励使用一个名为el-get（或MELPA）的emacs包管理器，我发现这两个都是bug，所以我至今仍然是使用仍然很棒的浏览器的IPython笔记本。
编辑
哦，另一个非常重要的事情是：我停止使用Python 3.3.0进行移动回到Python 3.2.3作为 numpy 1.6.2不支持Python 3.3.0，虽然这有显然是固定在1.76倍，目前还没有计划释放一个麻木1.6.3 。
I started off learning Python on OS X 10.6 (Snow Leopard) with a python.org Python dmg. I think I've seen this called "MacPython" on SO, but I'm also thinking that this MacPython (currently Google's top hit for "MacPython") is different, right?
Although I felt like my python.org Python 3.3.0 install was working reasonably well for me initially (using distribute, easy_install, and pip, I installed several new packages including IPython), I'd like to start using Emacs IPython Notebook (EIN) and Scipy, and it's clear to me that this kind of arrangement is going to require a lot of additional stuff from the CheeseShop. Plus, I've been very happily using MacPorts for GNU Emacs and other unix (non-Python) packages for a long time, so I'm thinking that it might be a good idea to move all my Python work (I'm focused on learning py3) away from what I have now with the python.org install and into MacPorts Python.
Is that a good idea? IOW, am I likely to be making for a great deal of extra time/work/headache for myself (like the headaches that @davidavr writes about here when he writes, "MacPorts would pull down and install the full Python 2.4 distro along with the library.") for very little gain or is the benefit of using a package manager like MacPorts for my Python stuff going to be a big timesaver like I suspect it might be?
I've read many other threads here (most rather old) that partly relate, but don't feel like there's anything recent that really addresses my question, and I encountered lots of older advice where it was clear that newer advice conflicted, so I'm asking what may be considered a duplicate, but if it is, I can't help thinking that the passage of several years may have changed some of the answers to older similar questions.
After trying with MacPorts and pip3 for many days and ultimately being unable to get a functional IPython notebook/qtconsole going with matplotlib and numpy and sympy and all that wonderful stuff, I gave up and switched to homebrew which ultimately worked for me, but I had to do a regular install from source for several of the bigger packages. Although homebrew would install these packages, it seemed to be doing so strictly for Python 2.7 and never for Python3; I tried several options in homebrew to fix this, but finally gave up and just installed from source for those difficult packages like Qt.
So I guess my experience was that MacPorts with pip3 was not a good idea for my particular goal whereas homebrew with pip3 was better, but still incomplete for Scipy packages with Python3. (Although perhaps if I had tried installing from source to supplement MacPorts the way I did with homebrew then MacPorts would have sufficed also.)
Looking back on the experience, I think there is a great need for more detailed and comprehensive documentation for new users on how to start from scratch and build these capabilities because I tried many different strategies and it was ultimately only through trial and error and lots of different bits and pieces of advice from all over the web that I finally got some of it going. I still don't have EIN going, but I think that's going to require tools strictly from the emacs world to get that going. EIN documentation strongly encourages use of an emacs package manager called el-get (or MELPA), and I found both to be buggy, so all I have thus far is IPython notebook using a browser which is still wonderful.
EDIT
Oh, one other very important thing: I stopped trying with Python 3.3.0 and moved back to Python 3.2.3 as numpy 1.6.2 doesn't support Python 3.3.0 and although this has apparently been fixed in numpy 1.7.x, there are currently no plans to release a numpy 1.6.3.
这篇关于从“MacPython”转换到MacPorts python3一个好主意EIN& SciPy的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
