On 2 Jul 2018, Michael Torrie wrote
(in article):
> On 06/30/2018 11:10 AM, Elliott Roper wrote:
> > I should have mentioned that none of this went wrong in 3.6. All I'm after
> > are packages I can install with pip3. I really don't need to go down all the
> > twisty passages installing Fortran
>
On 7/2/2018 9:50 AM, Michael Torrie wrote:
If you're wanting to use SciPy and matplotlib, I suggest you stick with
Python 3.6. There's little reason to immediately go to Python 3.7.
Anytime you upgrade to the very latest version of Python, it's going to
take some time for binary wheels to be bu
On 06/30/2018 11:10 AM, Elliott Roper wrote:
> I should have mentioned that none of this went wrong in 3.6. All I'm after
> are packages I can install with pip3. I really don't need to go down all the
> twisty passages installing Fortran
That's because there were likely binary packages available
On Thursday, June 28, 2018 at 1:09:04 PM UTC-4, Elliott Roper wrote:
> I have done something stupid. Don't know what.
>
> My $PATH looks like this
> XXXMac:~ elliott$ echo $PATH
> /Library/Frameworks/Python.framework/Versions/3.7/bin:/Library/Frameworks/Pyth
> on.framework/Versions/3.6/bin:/Librar
Elliott Roper writes:
> ...
> I should have mentioned that none of this went wrong in 3.6. All I'm after
> are packages I can install with pip3. I really don't need to go down all the
> twisty passages installing Fortran
"pip[*]" is a tool to install Python packages.
But some Python packages ar
On 30 Jun 2018, dieter wrote
(in article):
> Elliott Roper writes:
> > ...
> > install scipy wrote an error message longer than War and Peace that finished
> > with:-
> >
> > error: library dfftpack has Fortran sources b
On 06/29/18 21:48, dieter wrote:
I do not know "pkg-config". The name seems to indicate an
operating system package; but, it might also be a Python extension
package (less likely).
I would start with the "matplotlib"
installation instructions to look for information about it.
https://www.f
Elliott Roper writes:
> ...
> install scipy wrote an error message longer than War and Peace that finished
> with:-
>
> error: library dfftpack has Fortran sources but no Fortran compiler found
An error message of the t
On 29 Jun 2018, Terry Reedy wrote
(in article):
> On 6/28/2018 6:45 PM, Elliott Roper wrote:
> > On 28 Jun 2018, Terry Reedy wrote
>
> > > There is a pip command for making an editable file of installed
> > > packages. Run that in 3.6, perhaps after updating everything.
> > >
> > >
> > > There is
On 6/28/2018 6:45 PM, Elliott Roper wrote:
On 28 Jun 2018, Terry Reedy wrote
There is a pip command for making an editable file of installed
packages. Run that in 3.6, perhaps after updating everything.
There is another pip command for using that file to install everything
listed. Run that i
On 28 Jun 2018, Terry Reedy wrote
(in article):
> On 6/28/2018 1:08 PM, Elliott Roper wrote:
> > I have done something stupid. Don't know what.
>
> It appears that you ran 3.7 expecting that modules installed for 3.6
> would magically be available for 3.7.
Yes indeed. It worked for 3.4, 3.5, and 3
On 6/28/2018 1:08 PM, Elliott Roper wrote:
I have done something stupid. Don't know what.
It appears that you ran 3.7 expecting that modules installed for 3.6
would magically be available for 3.7.
There is a pip command for making an editable file of installed
packages. Run that in 3.6, pe
I have done something stupid. Don't know what.
My $PATH looks like this
XXXMac:~ elliott$ echo $PATH
/Library/Frameworks/Python.framework/Versions/3.7/bin:/Library/Frameworks/Pyth
on.framework/Versions/3.6/bin:/Library/Frameworks/Python.framework/Versions/3.
5/bin:/Library/Frameworks/Python.framew
13 matches
Mail list logo