[Chicago] Sympy for Python 3 ???

Tue Sep 29 19:15:54 CEST 2015

For just opening .ipynb files, Ipython requires an ipython (jupyter now I
guess) server to be running for the file to work. What you should do is, in
your terminal, cd into the folder where that file is located and then run
the ipython notebook command. This will open a browser window with a list
of the ipython files in that folder, which you can then open and edit / run
again.

Don't ever use Idle, so can't speak towards what's going on there...

On Tue, Sep 29, 2015 at 11:51 AM, Lewit, Douglas <d-lewit at neiu.edu> wrote:

> Hi William,
>
> Thanks for the reply.  I think Anaconda is GREAT!  However, there are
> times when I prefer the simplicity of IDLE.  What's strange is that IDLE
> does not have access to Anaconda's modules, even when I use Python's
> os.chdir( ) command to switch over to the folder/directory that contains
> those modules!  (Or at least I think I did.  There are so many files! )
>  For example, when I'm in Anaconda I can *import sympy* and everything is
> wonderful.  But IDLE returns an error and complains that I'm trying to
> import a non-existent module.   :-(  Anaconda is great, but 1) You can't go
> back and edit previous lines in the Anaconda Terminal, and 2) the *ipython
> notebook* solves this problem nicely, but I always have problems saving
> and restarting the notebook's file.  On my Mac, the "ipython notebook"
> command creates a Safari page, and I can use Python from within the Safari
> page.  Great!  But then let's say I save the file with a .ipynb extension.
> If I double-click on this file in the future, Safari opens it up alright,
> but none of the command lines are executable, and the file isn't much fun
> to read or look at.  I'm probably missing a step or a command or something
> like that.  But yes, in general Anaconda is quite impressive and the
> installation is pretty easy.  In Anaconda all the important modules are at
> my fingertips, so it is really nice to work with for the most part.  But
> again, IDLE has advantages.  In IDLE, I can move the cursor around inside a
> function's definition to change stuff.  Not in the Anaconda Terminal.  Once
> I ENTER over to the next line, I'm stuck!  I can't get back.  The best I
> can do is just CNTRL-C and start my function definition over again.
>
> I think my answer was way too long!  Sorry!  Just trying to explain what's
> going on.  I just wish there was a way that I could get IDLE to access all
> the modules that Anaconda can access.  Not really sure how to do it without
> tearing apart my operating system.  (And I really don't want to do that! )
>  I must say that on this particular issue Linux really does have a leg up
> on Mac OS-X because of Linux's builtin package managers.  However, for
> other things I really prefer Mac OS-X.  I wish we could combine the best of
> both worlds!  Let's call it LINAC!!!   :-)
>
> Doug.
>
>
>
> On Tue, Sep 29, 2015 at 8:19 AM, William E. S. Clemens <
> wesclemens at gmail.com> wrote:
>
>> I would personally highly recommend MacPorts over Homebrew.
>>
>> I find Homebrew to have some security concerns. I haven't played around
>> with Homebrew in a few years so they may have corrected this issue.
>> Homebrew installs itself and the software it manages  in /usr/local/ and
>> changes the permissions on this folder so the user that install Homebrew
>> can write to this directory. This is concur because a malicious pieces of
>> software can easy modify command line tools and basic unix utilities by
>> writing to this directory.
>>
>> If you are just looking for a simple way to mange your Python packages I
>> wouldn't recommend going with either of these. You can install newer
>> versions of Python for python.org. The newer versions have pip included
>> with it so it makes life a little easier.
>>
>> If you want to go the path of least resistance you can install the
>> Anaconda. This Python distribution uses an alternative package manager call
>> conda. Although it has fare fewer packages then pip and Pypi, It ships all
>> the major packages in wheels that can easy be installed on OSX without the
>> need to compile the C/Fortran parts. Whereas pip downloads the source and
>> attempts to compile it. Pip's method is more prone to failure especially on
>> OSX where you are using a different compiler then Linux.
>>
>> Managing  your Python software dependancies on a system wide basis can
>> have issues. Have you ever looked into using virtualenv?
>>
>> --
>> William Clemens
>> Phone: 847.485.9455
>> E-mail: wesclemens at gmail.com
>>
>> On Tue, Sep 29, 2015 at 6:04 AM, Tanya Schlusser <tanya at tickel.net>
>> wrote:
>>
>>> > P.S.  Almost forgot.... is there a Mac OS-X equivalent to the useful
>>> Ubuntu
>>> > command:
>>> > sudo apt-get install ..... and
>>> > sudo apt-get remove .....
>>>
>>>
>>> There are two popular options: homebrew and macports. For homebrew, open
>>> a terminal and type:
>>>
>>> ruby -e "$(curl -fsSL
>>> https://raw.githubusercontent.com/Homebrew/install/master/install)"
>>>
>>>
>>> and type this at the bottom of your ~/.profile file :
>>>
>>> export PATH=/usr/local/bin:/usr/local/sbin:$PATH
>>>
>>>
>>> and then do this in the terminal:
>>>
>>> brew install python
>>>
>>> Other homebrew options at: http://brew.sh/
>>>
>>> _______________________________________________
>>> Chicago mailing list
>>> Chicago at python.org
>>> https://mail.python.org/mailman/listinfo/chicago
>>>
>>>
>>
>> _______________________________________________
>> Chicago mailing list
>> Chicago at python.org
>> https://mail.python.org/mailman/listinfo/chicago
>>
>>
>
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> https://mail.python.org/mailman/listinfo/chicago
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20150929/3018fa85/attachment.html>