Hi Freddie, Indeed it manages to create a .egg file (seemingly binary) under the directory dist/.
So you say I should copy manually this file to the drectory <python dir>/ *lib/python3.3/site-packages*, right? However I still need the executable pyfr in the directory <python dir>/*bin, *which is created later at running the setup.py script. How can I then complete the installation? Thanks once more. Best regards, Antonio On Wednesday, June 22, 2016 at 4:13:28 PM UTC+2, Freddie Witherden wrote: > > Hi Antonio, > > On 22/06/2016 07:11, Antonio Garcia-Uceda wrote: > > Thanks a lot for you reply. > > > > Indeed the workng directory is under a networking file system. I can't > > tell you details though since I;m not aware of it, but I can ask. > > > > Please let me know whether you need any further info. > > My understanding is that Python sometimes has trouble installing to > network shares. However, using setup.py you should be able to get it to > build the relevant .egg for you and then copy this egg manually to the > relevant directory. > > Regards, Freddie. > > > -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout.
