Sorry, I meant  I will *NOW* try to do some basic customizations and import 
some of my Dublin Core based Metadata ( a simple set ) and see how this 
goes. 

On Thursday, 7 December 2017 11:02:49 UTC+2, Roshan Bhurtha wrote:
>
> Dear Adam 
> Thanks for delving in to this. Many apologies for this late reply.  As in 
> many small teams I have to get my hand in many pies and had to quickly jump 
> from one project to another.
>
> I have been able to install the latest  Arches version 4.0.1. I will not 
> try to do some basic customizations and import some of my Dublin Core based 
> Metadata ( a simple set ) and see how this goes. 
>
> Regards
> Roshan
>
> On Friday, 24 November 2017 17:56:21 UTC+2, Adam Cox wrote:
>>
>> Hi Roshan, I think the problem for you is that you have tried to run pip 
>> install arches and then pip install arches --no-binary :all: without 
>> running pip uninstall arches in between. Then, when you then tried to 
>> install 4.0b3 pip considered that to be a new package and ran the entire 
>> install process properly. So, it's not a difference with the Arches 
>> packages, but an issue with your virtualenv. To test this, make a fresh 
>> virtual environment and first run pip install arches --no-binaries :all: and 
>> you'll be able to import django.
>>
>> I will share some screenshots of my own retesting of this, demonstrating 
>> the need to uninstall the arches package.
>>
>> First with python 2.7.6 (which is my current global python)
>>
>> [image: Inline image 1]
>> etc.......... (lots more uninstall messages)
>> [image: Inline image 2]
>>
>> And also with Python 2.7.13
>>
>> [image: Inline image 3]
>> etc.
>> [image: Inline image 4]
>>
>> You'll notice that in both environments, pip 9.0.1 is used as well.
>>
>> The reason for the no-binaries argument is that by default pip tries to 
>> use a different type installation process (using binaries) for all of the 
>> python packages listed in requirements.txt. Some of those packages 
>> apparently don't have binaries available, which (annoyingly) breaks the 
>> installation process for all of them. This is a strange and kind of opaque 
>> issue (also I believe pip behaves slightly differently on different 
>> operating systems), but we found that you can direct pip to not look for 
>> any binary distributions when it installs these python dependencies, which 
>> fixes the issue and is a safe course of action.
>>
>> Thanks for being diligent about trying to fix this issue. I strongly 
>> advise getting 4.0.1 to install correctly and that you do not use 4.0b3, as 
>> there were some important bugfixes applied in 4.0.1.
>>
>> Adam
>>
>> On Fri, Nov 24, 2017 at 2:59 AM, Roshan Bhurtha <[email protected]> 
>> wrote:
>>
>>> *An update on this:*
>>>
>>>  It seems that there is a hiccup with the command "pip install arches 
>>> --no-binary :all:"
>>>
>>> But if I run this command
>>>
>>> *pip install arches==4.0b3 --no-binary :all:*
>>>
>>> django is installed !
>>>
>>> I am not sure why the default version of Arches will not pull the 
>>> dependancies.
>>>
>>> regards
>>> Roshan
>>>
>>> On Wednesday, 22 November 2017 10:25:18 UTC+2, Roshan Bhurtha wrote:
>>>>
>>>> Dear Adam, 
>>>> Thanks for your reply. 
>>>> I ran  the "pip install arches --no-binary :all:"   command, and it 
>>>> said all "Requirement already satisfied", BUT django was not installed 
>>>> when 
>>>> I imported inside Python!
>>>> Have a look at this screenshot please.
>>>> Any ideas what I am doing wrong ?
>>>> Thanks 
>>>> Roshan
>>>>
>>>>
>>>> <https://lh3.googleusercontent.com/-du6pO4bvNz4/WhUz8c-Bn0I/AAAAAAAACFE/ixs_rBOP8_0wx8WHijMs2M5n_R8tDbF9ACLcBGAs/s1600/django.png>
>>>>
>>>>
>>>> On Friday, 17 November 2017 18:40:22 UTC+2, Adam Cox wrote:
>>>>>
>>>>> Hi Roshan,
>>>>>
>>>>> Any command you run that references the manage.py file must be run 
>>>>> with the virtual environment activated, which will add the (ENV) prefix 
>>>>> to 
>>>>> your command prompt.
>>>>>
>>>>> To quickly test that Django (along with all other python dependencies) 
>>>>> has installed correctly, you can activate your virtual environment, then 
>>>>> run python (which will open the python interpreter) then import django. 
>>>>> If you get an error, then something didn't work during the pip 
>>>>> install arches --no-binary :all: process. To exit the python 
>>>>> interpreter, use exit().
>>>>>
>>>>> FYI, I have just finished an overhaul of the installation 
>>>>> documentation that should clear up some issues that have come up, 
>>>>> streamline the process, as well as a command to load an example package 
>>>>> that we have made so it is easier to get up and running. You can find it 
>>>>> here: http://arches4.readthedocs.io/en/latest/installation/ (as 
>>>>> before).
>>>>>
>>>>> Adam
>>>>>
>>>>> On Fri, Nov 17, 2017 at 7:05 AM, Roshan Bhurtha <[email protected]> 
>>>>> wrote:
>>>>>
>>>>>> Dear all
>>>>>> I am trying to install arches( Windows 64-bit) and I am now at  the 
>>>>>> stage where I have to create a project, with the command *"python 
>>>>>> C:\Projects\ENV\Scripts\arches-project create my_project"*
>>>>>> * , *as given on the arches website.
>>>>>>
>>>>>> I run into a problem here: I am assuming that I have to run the above 
>>>>>> mentioned command OUT of the (*ENV) * that I created ?
>>>>>>
>>>>>> And if I do run this command from a normal windows command line (out 
>>>>>> of the ENV) , i get the  error message  "ImportError: no module named 
>>>>>> django" 
>>>>>> How do I proceed ? And at what stage was Django supposed to have been 
>>>>>> installed in the process ?
>>>>>> I am trying to do as diligently as possible and follow the steps 
>>>>>> given exactly, but obviously I made am error(s) somewhere. Any help will 
>>>>>> be 
>>>>>> much appreciated.
>>>>>>
>>>>>> thanks !
>>>>>> Roshan
>>>>>>
>>>>>> -- 
>>>>>> -- To post, send email to [email protected]. To 
>>>>>> unsubscribe, send email to [email protected]. For 
>>>>>> more information, visit 
>>>>>> https://groups.google.com/d/forum/archesproject?hl=en
>>>>>> --- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Arches Project" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> -- 
>>> -- To post, send email to [email protected]. To unsubscribe, 
>>> send email to [email protected]. For more information, 
>>> visit https://groups.google.com/d/forum/archesproject?hl=en
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Arches Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to