(please cc to the list) There's no particular problem running two Pythons (different versions or different bitness) on the same machine. Just make sure you install them into different folders, e.g. C:\Python27, C:\Python27_64. After this, when you install any package, you should be careful to choose which version of Python to install against (you will be given a list).
The only minor problem is that by default IDLE will use the last version of Python you installed (i.e. right click, open with IDLE). You can get around this by having a shortcut on your desktop to different IDLEs, or use an editor (e.g. Spyder) that allows you to specify which Python to run stuff with. - Noel On 30 July 2013 22:13, macc_200 <macc_...@yahoo.co.uk> wrote: > Thanks. That will be it. It's 64 bit. Is it possible to run two pythons > on the same machine? And if I do, am I likely to break what's already > there? > > From: Noel O'Boyle <baoille...@gmail.com> > To: Pete Jone <bbac...@outlook.com> > Cc: . <openbabel-discuss@lists.sourceforge.net> > Sent: Tuesday, 30 July 2013, 21:41 > Subject: Re: [Open Babel] openbabel module not imported by python > > All of our Windows code is currently 32-bit, and so it requires 32-bit > Python. Are you sure your Python is the 32-bit one? > > - Noel > > On 30 July 2013 20:04, Pete Jone <bbac...@outlook.com> wrote: >> Hi, >> I've just installed openbabel 2.3.2 on a Windows8 laptop using the Windows >> installer. The GUI starts up OK but if I try to import openbabel in IDLE >> I >> get the No module Named openbabel error. I also tried installing pybel >> and >> it tells me that python is not found in the registry and stops. I can use >> python (2.7) fine and import rdkit and various other modules. Any ideas >> about what is wrong? The openbabel datadir variable looks a bit odd: >> (C:\Users\pc1\AppData\Roaming\OpenBabel-2.3.2\data) but I really don't >> know >> what is wrong - it's always worked like clockwork before. >> thanks >> P >> >> >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> _______________________________________________ >> OpenBabel-discuss mailing list >> OpenBabel-discuss@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openbabel-discuss >> > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > OpenBabel-discuss mailing list > OpenBabel-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbabel-discuss > > ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ OpenBabel-discuss mailing list OpenBabel-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-discuss
