[Chicago] Sympy for Python 3 ???

Lewit, Douglas d-lewit at neiu.edu
Wed Sep 30 03:04:58 CEST 2015

Exactly!  I'm a little nervous about changing my $PATH variable because I'm
definitely NOT a Unix administrator!  I mean.... I know the basics, like
cd, cp, mv, ls, ls -ld -- */, ls | wc -l, and some other cool stuff.  But
changing $PATH is a little scary to me!  On the rare occasion when I do
that stuff, I always use Emacs as my text editor.  The great thing about
Emacs is that when you edit a file, Emacs saves the original with a tilde
following the name of the file.  So if I want to edit bash.rc I end up with
bash.rc and bash.rc~.  If I totally screwed up bash.rc, then I just do this:

mv bash.rc~ bash.rc

That restores the previous bash.rc file.  It overwrites the messed up file
with the original correct file.  BUT in general I'm very nervous about
doing system changes like that.  I tried doing a dual boot of Ubuntu and
Kali Linux a while back.  Big mistake!!!!  I mistakenly deleted the grub
file and then I was really SCREWED!!!!  I had to do a fresh install of
Ubuntu on my hard drive.  That wasn't fun!  (Ubuntu is pretty easy to
install.  Kali Linux is NOT easy to install unless you know a lot about
networking, protocols, and other stuff that is currently beyond my
knowledge of modern computation.)

I would love to attend a Python Project Night.  The problem is that those
are always scheduled for a Thursday night.  That's when I have my
Informatics class.  And since the class meets up once a week, missing a
class for Python Project Night is probably not a smart move on my part.

Oh hey there Safia!  Thanks for writing.  Much appreciated.

On Tue, Sep 29, 2015 at 1:57 PM, William E. S. Clemens <wesclemens at gmail.com
> wrote:

> Os.chdir( ) is not what your looking for you need to add the path for your
> Anaconda packages to the sys.path list. That being said its generally not a
> good idea to mess with sys.path unless you know what your doing. It will
> almost surely break your code portability.
> If you need help setting up Python I would suggest that you go to Project
> Night. They are a great group of people and I'm sure they would be more
> then happy to get you started down the right path.
> http://www.meetup.com/ChicagoPythonistas/
> --
> William Clemens
> Phone: 847.485.9455
> E-mail: wesclemens at gmail.com
> On Tue, Sep 29, 2015 at 12:29 PM, Joshua Herman <zitterbewegung at gmail.com>
> wrote:
>> How do people generally learn python? I think I have progressed in the
>> following manner.
>> 0. Don't know what python is (First experience was from Carl Karsten
>> telling me the general syntax rules.
>> 1. Start by using python script on the command line
>> 2. Play with IDLE / other IDEs/ Scripting
>> 4. Use python at school at the compbio laboratory and Alcatel Lucen
>> 5. Learn what virtualenv is and make them
>> 6. Learn what ipython is and use ipython
>> 7. Play with anaconda
>> 8. I am here
>> Python is generally batteries included. Should ipython be a better
>> starting point for people who install python? I think more scientific/
>> financial oriented people are doing the following.
>> 1. Get exposed to python to apply to work
>> 2. Use ipython by installing using anaconda and use it in a browser?
>> possibly you don't even have a local install of python .
>> Now the person's goals will cause them to make a decision.
>> ?. Start by using python script on the command line
>> ?. Play with IDLE / other IDEs/ Scripting
>> ?. Learn what virtualenv is and make them
>> ?. Do web development
>> I think that if more people are doing the second path maybe we should
>> introduce python the second way instead of the first. For one reason
>> setting up ipython or some notebook interface on some cloud server is
>> probably going to become more common. The first way that people seem to
>> learn python takes much more steps to do interesting things and once a
>> person is hooked on python then they can learn the other steps.
>> On Tue, Sep 29, 2015 at 12:16 PM, sheila miguez <shekay at pobox.com> wrote:
>>> On Tue, Sep 29, 2015 at 11:51 AM, Lewit, Douglas <d-lewit at neiu.edu>
>>> wrote:
>>>> 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
>>> This is where the google it answer is helpful. A lot of times I'll have
>>> a question like this and will google and see some related stack overflow
>>> questions among other things. For this case I googled: using idle in
>>> anaconda
>>> That pulled up a mailing list discussion on the anaconda mailing list.
>>> It's an interesting thread, and you can see the devs saying that IDLE
>>> should be given better support. So that is nice for you to hear.
>>> https://groups.google.com/a/continuum.io/d/msg/anaconda/Dr8xFdKbA20/MWvhTO4KF8wJ
>>> The stack overflow response is
>>> http://stackoverflow.com/questions/26047185/import-anaconda-packages-to-idle
>>> Someone had the same problem you did. Try out the answer. It involves
>>> changing PATH, which is a normal kind of thing to do in an OS, and you
>>> won't need to worry about ripping apart your operating system. I don't know
>>> if the answer works, but it something to try.
>>> --
>>> shekay at pobox.com
>>> _______________________________________________
>>> 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/b595324a/attachment.html>

More information about the Chicago mailing list