Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-06 Thread Adam Cox
Ok, thanks for the followup Colin, it makes sense you would have to upgrade
after you are in the virtual environment.

Adam

On Sun, May 5, 2019 at 9:03 PM Colin Wu  wrote:

> Just a follow-up:
>
> I did try the install again on a fresh Ubuntu 16.04 VM and my last
> observation (at the bottom of this thread) was incorrect: You must upgrade
> pip (to version 19.1) AFTER activating the virtual environment (between
> steps 3 and 4 of the installation instructions). Seems no matter what
> version of pip you're running before activating the virtual environment,
> the virtual environment starts with the old version.
>
> On Wednesday, 1 May 2019 22:10:49 UTC-4, Colin Wu wrote:
>>
>> Hi all,
>>
>> I am trying to install Arches on a Ubuntu 16.04 desktop and python
>> 2.7.12. Everything seems to go swimmingly until I reach the "Install
>> Elasticsearch with Arches" section!
>>
>> Running the suggested command (python manage.py es install) gives me
>> errors that ultimately result from the script not being able to find a
>> captcha module (ImportError: No module named captcha).
>>
>> I searched the forum and found (old) posts about not finding the captcha
>> module during an upgrade from 4.0.1 to 4.1.0. Tried the suggestions there
>> but no joy.
>>
>> I note that 4.4.1 was only released March 29 (?) so maybe the
>> installation procedure hasn't been sufficiently debugged yet?
>>
>> Thanks for any help.
>>
> --
> -- To post, send email to archesproject@googlegroups.com. To unsubscribe,
> send email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-03 Thread mr . adamcox
Ok! glad things are working out now, even if we don't fully understand why! 
I'm not sure why upgrading pip before you are in the virtual env would make 
a difference (as you can see in my example I did it within the virtualenv 
after it was created and activated), but if it works it works.

Martha, as to renaming environments and projects: I would conservatively 
just say no to both.

I believe that environments can't be renamed because there are references 
within the directory itself to it's name. Further, it's really good to 
treat them as disposable, so I'd recommend never holding any specific 
virtual environment dear. You should be able to delete and replicate one 
anytime you need, and you really should need to edit anything inside them 
either. You can use pip freeze to list out what libraries are installed in 
a virtual environment, and this can be useful if you have installed 
libraries and need to install the exact same versions into another.

As for projects, again I would say no just from a best practices point of 
view. The name of a project's top directory actually has no bearing on the 
app, so technically you can rename that if you want. However, the name of 
the second directory (my_project/my_project) is used (I believe) for the 
setting APP_NAME which is important throughout the app: it is used in the 
actual postgres database name that your project uses, and there are python 
import statements that have that directory name.

Adam

On Thursday, May 2, 2019 at 9:49:43 PM UTC-5, Colin Wu wrote:
>
> I think tomorrow I will start with a fresh Ubuntu VM and see what happens, 
> so don't close this just yet, Adam. ;)
>
>
> On Thursday, 2 May 2019 22:45:09 UTC-4, Martha S wrote:
>>
>> We'd already done that upgrade beforehand, Colin, 
>>
>> Whatever the problem was, though, we got past it, too. We have stopped at 
>> that point for tonight as well.
>>
>> Martha
>>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-02 Thread Martha S
We'd already done that upgrade beforehand, Colin, 

Whatever the problem was, though, we got past it, too. We have stopped at 
that point for tonight as well.

Martha

On Thursday, May 2, 2019 at 7:28:12 PM UTC-7, Colin Wu wrote:
>
> I think I've figured it out. *The trick is to ensure you upgrade pip (to 
> ver 19.1) BEFORE creating the virtual environment (step 2 in the install 
> procedure).*
>
> So, Step 1.1 - do 'pip install --upgrade pip'
>
> I did this doing this last install for Adam and was able to install 
> Elasticsearch. Haven't gone beyond that yet, though ... :)
>
>
> On Thursday, 2 May 2019 22:16:35 UTC-4, Colin Wu wrote:
>>
>> Adam,
>>
>> Here you go... 
>>
>> On Thursday, 2 May 2019 22:05:57 UTC-4, Adam Cox wrote:
>>>
>>> Hi Martha and Colin, ok it sounds like something is really failing in 
>>> the initial installation of arches into the virtual environment, so nothing 
>>> to do with the elasticsearch command itself. All of those modules should be 
>>> installed during the one pip command.
>>>
>>> Would either of you be able to try this out with a fresh virtual 
>>> environment and then share the log here? Use
>>>
>>> pip install arches --no-binary :all: --log pipinstall.log
>>>
>>> And then we can take a look at the log file.
>>>
>>> Thanks,
>>> Adam
>>>
>>> On Thu, May 2, 2019 at 8:39 PM Martha S  wrote:
>>>
>>>> I tried doing a re-install of python, but that didn't change anything. 
>>>> I have now pip installed the dateutil library at Ryan's suggestion, which 
>>>> then brought up a fail on edtf. I'll go down this path a little way, but 
>>>> there has to be an easier way to get back on track, right?
>>>>
>>>> Martha
>>>>
>>>> On Thursday, May 2, 2019 at 5:48:52 PM UTC-7, Martha S wrote:
>>>>>
>>>>> I redid the pip install of everything after the recaptcha line; some 
>>>>> were already present and one failed -- pycryptodome, which you can see in 
>>>>> the screen shot below.
>>>>>
>>>>> Now the problem is that there is no python dateutil library to import. 
>>>>> We had no problems with the initial install or the upgrade of python. I 
>>>>> sure hope we don't have to start anew. 
>>>>>
>>>>> Martha
>>>>>
>>>>> [image: No dateutil.jpg]
>>>>>
>>>>>
>>>>> On Thursday, May 2, 2019 at 4:41:05 PM UTC-7, Colin Wu wrote:
>>>>>>
>>>>>> Martha,
>>>>>>
>>>>>> I think you need to believe in the virtual environment to install 
>>>>>> modules, otherwise the new modules won't be seen by the virtual env.
>>>>>>
>>>>>> “Waste no more time arguing what a good man should be, just be one.” 
>>>>>> -- Marcus Aurelius
>>>>>> *From:* marth...@lacity.org
>>>>>> *Sent:* May 2, 2019 19:22
>>>>>> *To:* arches...@googlegroups.com
>>>>>> *Subject:* [Arches] Re: New install of 4.4.1 fails to install 
>>>>>> Elasticsearch
>>>>>>
>>>>>> Adam,
>>>>>>
>>>>>> Unfortunately, the pip install of captcha changed nothing. What do 
>>>>>> you recommend next?
>>>>>>
>>>>>> Thanks,
>>>>>> Martha
>>>>>>
>>>>>> [image: No Captcha2.jpg]
>>>>>>
>>>>>>
>>>>>> On Thursday, May 2, 2019 at 2:15:36 PM UTC-7, mr.a...@gmail.com 
>>>>>> wrote:
>>>>>>>
>>>>>>> Here is an example on ubuntu 16.04, python 2.7.12:
>>>>>>>
>>>>>>>
>>>>>>> I did get an error the first time I tried without upgrading pip. In 
>>>>>>> that case, I got a "no module named django" error when trying to create 
>>>>>>> the 
>>>>>>> project, even though the installation of Arches looked as if it had 
>>>>>>> gone 
>>>>>>> smoothly and the virtual env was activated.
>>>>>>>
>>>>>>> Also note that I used --no-cache-dir here in the pip install of 
>>>>>>> arches because this server has a small amount of memory and was 
>>>>>>> crashing 
>>&g

Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-02 Thread Colin Wu
I think I've figured it out. *The trick is to ensure you upgrade pip (to 
ver 19.1) BEFORE creating the virtual environment (step 2 in the install 
procedure).*

So, Step 1.1 - do 'pip install --upgrade pip'

I did this doing this last install for Adam and was able to install 
Elasticsearch. Haven't gone beyond that yet, though ... :)


On Thursday, 2 May 2019 22:16:35 UTC-4, Colin Wu wrote:
>
> Adam,
>
> Here you go... 
>
> On Thursday, 2 May 2019 22:05:57 UTC-4, Adam Cox wrote:
>>
>> Hi Martha and Colin, ok it sounds like something is really failing in the 
>> initial installation of arches into the virtual environment, so nothing to 
>> do with the elasticsearch command itself. All of those modules should be 
>> installed during the one pip command.
>>
>> Would either of you be able to try this out with a fresh virtual 
>> environment and then share the log here? Use
>>
>> pip install arches --no-binary :all: --log pipinstall.log
>>
>> And then we can take a look at the log file.
>>
>> Thanks,
>> Adam
>>
>> On Thu, May 2, 2019 at 8:39 PM Martha S  wrote:
>>
>>> I tried doing a re-install of python, but that didn't change anything. I 
>>> have now pip installed the dateutil library at Ryan's suggestion, which 
>>> then brought up a fail on edtf. I'll go down this path a little way, but 
>>> there has to be an easier way to get back on track, right?
>>>
>>> Martha
>>>
>>> On Thursday, May 2, 2019 at 5:48:52 PM UTC-7, Martha S wrote:
>>>>
>>>> I redid the pip install of everything after the recaptcha line; some 
>>>> were already present and one failed -- pycryptodome, which you can see in 
>>>> the screen shot below.
>>>>
>>>> Now the problem is that there is no python dateutil library to import. 
>>>> We had no problems with the initial install or the upgrade of python. I 
>>>> sure hope we don't have to start anew. 
>>>>
>>>> Martha
>>>>
>>>> [image: No dateutil.jpg]
>>>>
>>>>
>>>> On Thursday, May 2, 2019 at 4:41:05 PM UTC-7, Colin Wu wrote:
>>>>>
>>>>> Martha,
>>>>>
>>>>> I think you need to believe in the virtual environment to install 
>>>>> modules, otherwise the new modules won't be seen by the virtual env.
>>>>>
>>>>> “Waste no more time arguing what a good man should be, just be one.” 
>>>>> -- Marcus Aurelius
>>>>> *From:* marth...@lacity.org
>>>>> *Sent:* May 2, 2019 19:22
>>>>> *To:* arches...@googlegroups.com
>>>>> *Subject:* [Arches] Re: New install of 4.4.1 fails to install 
>>>>> Elasticsearch
>>>>>
>>>>> Adam,
>>>>>
>>>>> Unfortunately, the pip install of captcha changed nothing. What do you 
>>>>> recommend next?
>>>>>
>>>>> Thanks,
>>>>> Martha
>>>>>
>>>>> [image: No Captcha2.jpg]
>>>>>
>>>>>
>>>>> On Thursday, May 2, 2019 at 2:15:36 PM UTC-7, mr.a...@gmail.com wrote:
>>>>>>
>>>>>> Here is an example on ubuntu 16.04, python 2.7.12:
>>>>>>
>>>>>>
>>>>>> I did get an error the first time I tried without upgrading pip. In 
>>>>>> that case, I got a "no module named django" error when trying to create 
>>>>>> the 
>>>>>> project, even though the installation of Arches looked as if it had gone 
>>>>>> smoothly and the virtual env was activated.
>>>>>>
>>>>>> Also note that I used --no-cache-dir here in the pip install of 
>>>>>> arches because this server has a small amount of memory and was crashing 
>>>>>> with a "MemoryError" without that argument. However, --no-cache-dir is 
>>>>>> not 
>>>>>> generally required.
>>>>>>
>>>>>> Adam
>>>>>>
>>>>>>
>>>>>> On Thursday, May 2, 2019 at 3:59:24 PM UTC-5, mr.a...@gmail.com 
>>>>>> wrote:
>>>>>>>
>>>>>>> Ok, I was able to get past this step on my end, and first thing I 
>>>>>>> think you should check: is your virtual environment activated? Your 
>>>>>>> command 
>>>>>>> li

Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-02 Thread Adam Cox
Hi Martha and Colin, ok it sounds like something is really failing in the
initial installation of arches into the virtual environment, so nothing to
do with the elasticsearch command itself. All of those modules should be
installed during the one pip command.

Would either of you be able to try this out with a fresh virtual
environment and then share the log here? Use

pip install arches --no-binary :all: --log pipinstall.log

And then we can take a look at the log file.

Thanks,
Adam

On Thu, May 2, 2019 at 8:39 PM Martha S  wrote:

> I tried doing a re-install of python, but that didn't change anything. I
> have now pip installed the dateutil library at Ryan's suggestion, which
> then brought up a fail on edtf. I'll go down this path a little way, but
> there has to be an easier way to get back on track, right?
>
> Martha
>
> On Thursday, May 2, 2019 at 5:48:52 PM UTC-7, Martha S wrote:
>>
>> I redid the pip install of everything after the recaptcha line; some were
>> already present and one failed -- pycryptodome, which you can see in the
>> screen shot below.
>>
>> Now the problem is that there is no python dateutil library to import. We
>> had no problems with the initial install or the upgrade of python. I sure
>> hope we don't have to start anew.
>>
>> Martha
>>
>> [image: No dateutil.jpg]
>>
>>
>> On Thursday, May 2, 2019 at 4:41:05 PM UTC-7, Colin Wu wrote:
>>>
>>> Martha,
>>>
>>> I think you need to believe in the virtual environment to install
>>> modules, otherwise the new modules won't be seen by the virtual env.
>>>
>>> “Waste no more time arguing what a good man should be, just be one.” --
>>> Marcus Aurelius
>>> *From:* marth...@lacity.org
>>> *Sent:* May 2, 2019 19:22
>>> *To:* arches...@googlegroups.com
>>> *Subject:* [Arches] Re: New install of 4.4.1 fails to install
>>> Elasticsearch
>>>
>>> Adam,
>>>
>>> Unfortunately, the pip install of captcha changed nothing. What do you
>>> recommend next?
>>>
>>> Thanks,
>>> Martha
>>>
>>> [image: No Captcha2.jpg]
>>>
>>>
>>> On Thursday, May 2, 2019 at 2:15:36 PM UTC-7, mr.a...@gmail.com wrote:
>>>>
>>>> Here is an example on ubuntu 16.04, python 2.7.12:
>>>>
>>>>
>>>> I did get an error the first time I tried without upgrading pip. In
>>>> that case, I got a "no module named django" error when trying to create the
>>>> project, even though the installation of Arches looked as if it had gone
>>>> smoothly and the virtual env was activated.
>>>>
>>>> Also note that I used --no-cache-dir here in the pip install of arches
>>>> because this server has a small amount of memory and was crashing with a
>>>> "MemoryError" without that argument. However, --no-cache-dir is not
>>>> generally required.
>>>>
>>>> Adam
>>>>
>>>>
>>>> On Thursday, May 2, 2019 at 3:59:24 PM UTC-5, mr.a...@gmail.com wrote:
>>>>>
>>>>> Ok, I was able to get past this step on my end, and first thing I
>>>>> think you should check: is your virtual environment activated? Your 
>>>>> command
>>>>> line prompt should be prefixed with the name of the directory of your
>>>>> virtualenv. In the docs we use ENV, so if you've followed that you should
>>>>> be seeing (ENV) at the front of each line.
>>>>>
>>>>> The following is on windows, though I'll see about getting an ubuntu
>>>>> test too.
>>>>>
>>>>>
>>>>> Please note that I don't recommend using echo to put the GDAL library
>>>>> path in settings_local.py as I did in the example above--it will
>>>>> erase the other contents of that file. Best to hand edit.
>>>>>
>>>>> If you still have trouble, could you send a screenshot or two?
>>>>>
>>>>> Thanks,
>>>>> Adam
>>>>>
>>>>> On Thursday, May 2, 2019 at 3:20:56 PM UTC-5, mr.a...@gmail.com wrote:
>>>>>>
>>>>>> Hi Colin and Martha,
>>>>>>
>>>>>> I'll try out a test installation locally and see what I can find. In
>>>>>> the meantime, if you try pip installing captcha does that solve it, or 
>>>>>> lead
>>>>>> to messages of new libraries that are missing?
>>>

Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-02 Thread Martha S
I tried doing a re-install of python, but that didn't change anything. I 
have now pip installed the dateutil library at Ryan's suggestion, which 
then brought up a fail on edtf. I'll go down this path a little way, but 
there has to be an easier way to get back on track, right?

Martha

On Thursday, May 2, 2019 at 5:48:52 PM UTC-7, Martha S wrote:
>
> I redid the pip install of everything after the recaptcha line; some were 
> already present and one failed -- pycryptodome, which you can see in the 
> screen shot below.
>
> Now the problem is that there is no python dateutil library to import. We 
> had no problems with the initial install or the upgrade of python. I sure 
> hope we don't have to start anew. 
>
> Martha
>
> [image: No dateutil.jpg]
>
>
> On Thursday, May 2, 2019 at 4:41:05 PM UTC-7, Colin Wu wrote:
>>
>> Martha,
>>
>> I think you need to believe in the virtual environment to install 
>> modules, otherwise the new modules won't be seen by the virtual env.
>>
>> “Waste no more time arguing what a good man should be, just be one.” -- 
>> Marcus Aurelius
>> *From:* marth...@lacity.org
>> *Sent:* May 2, 2019 19:22
>> *To:* arches...@googlegroups.com
>> *Subject:* [Arches] Re: New install of 4.4.1 fails to install 
>> Elasticsearch
>>
>> Adam,
>>
>> Unfortunately, the pip install of captcha changed nothing. What do you 
>> recommend next?
>>
>> Thanks,
>> Martha
>>
>> [image: No Captcha2.jpg]
>>
>>
>> On Thursday, May 2, 2019 at 2:15:36 PM UTC-7, mr.a...@gmail.com wrote:
>>>
>>> Here is an example on ubuntu 16.04, python 2.7.12:
>>>
>>>
>>> I did get an error the first time I tried without upgrading pip. In that 
>>> case, I got a "no module named django" error when trying to create the 
>>> project, even though the installation of Arches looked as if it had gone 
>>> smoothly and the virtual env was activated.
>>>
>>> Also note that I used --no-cache-dir here in the pip install of arches 
>>> because this server has a small amount of memory and was crashing with a 
>>> "MemoryError" without that argument. However, --no-cache-dir is not 
>>> generally required.
>>>
>>> Adam
>>>
>>>
>>> On Thursday, May 2, 2019 at 3:59:24 PM UTC-5, mr.a...@gmail.com wrote:
>>>>
>>>> Ok, I was able to get past this step on my end, and first thing I think 
>>>> you should check: is your virtual environment activated? Your command line 
>>>> prompt should be prefixed with the name of the directory of your 
>>>> virtualenv. In the docs we use ENV, so if you've followed that you should 
>>>> be seeing (ENV) at the front of each line.
>>>>
>>>> The following is on windows, though I'll see about getting an ubuntu 
>>>> test too.
>>>>
>>>>
>>>> Please note that I don't recommend using echo to put the GDAL library 
>>>> path in settings_local.py as I did in the example above--it will erase 
>>>> the other contents of that file. Best to hand edit.
>>>>
>>>> If you still have trouble, could you send a screenshot or two?
>>>>
>>>> Thanks,
>>>> Adam
>>>>
>>>> On Thursday, May 2, 2019 at 3:20:56 PM UTC-5, mr.a...@gmail.com wrote:
>>>>>
>>>>> Hi Colin and Martha,
>>>>>
>>>>> I'll try out a test installation locally and see what I can find. In 
>>>>> the meantime, if you try pip installing captcha does that solve it, or 
>>>>> lead 
>>>>> to messages of new libraries that are missing?
>>>>> Use
>>>>>
>>>>> pip install django-recaptcha==1.4.0
>>>>>
>>>>> as is listed here 
>>>>> https://github.com/archesproject/arches/blob/stable/4.4.1/arches/install/requirements.txt#L14
>>>>>
>>>>> Adam
>>>>>
>>>>> On Thursday, May 2, 2019 at 1:24:06 PM UTC-5, Martha S wrote:
>>>>>>
>>>>>> Hi, All, 
>>>>>>
>>>>>> We are at exactly the same point in the 4.4.1 install with the same 
>>>>>> issue. Any answers? We are on Ubuntu 18.04, pip 19.1, and Python 
>>>>>> 2.7.15rc1.
>>>>>>
>>>>>> Martha
>>>>>>
>>>>>> On Wednesday, May 1, 2019 at 7:10:49 PM UTC-7, Colin Wu wrote:
>>>>>>

Re: [Arches] Re: New install of 4.4.1 fails to install Elasticsearch

2019-05-02 Thread Martha S
Yes, Colin,

That has made a difference, but as you found, I am now missing a number of 
libraries. I will attack that and then try the es install again.

Thanks,
Martha

On Thursday, May 2, 2019 at 4:41:05 PM UTC-7, Colin Wu wrote:
>
> Martha,
>
> I think you need to believe in the virtual environment to install modules, 
> otherwise the new modules won't be seen by the virtual env.
>
> “Waste no more time arguing what a good man should be, just be one.” -- 
> Marcus Aurelius
> *From:* marth...@lacity.org 
> *Sent:* May 2, 2019 19:22
> *To:* arches...@googlegroups.com 
> *Subject:* [Arches] Re: New install of 4.4.1 fails to install 
> Elasticsearch
>
> Adam,
>
> Unfortunately, the pip install of captcha changed nothing. What do you 
> recommend next?
>
> Thanks,
> Martha
>
> [image: No Captcha2.jpg]
>
>
> On Thursday, May 2, 2019 at 2:15:36 PM UTC-7, mr.a...@gmail.com wrote:
>>
>> Here is an example on ubuntu 16.04, python 2.7.12:
>>
>>
>> I did get an error the first time I tried without upgrading pip. In that 
>> case, I got a "no module named django" error when trying to create the 
>> project, even though the installation of Arches looked as if it had gone 
>> smoothly and the virtual env was activated.
>>
>> Also note that I used --no-cache-dir here in the pip install of arches 
>> because this server has a small amount of memory and was crashing with a 
>> "MemoryError" without that argument. However, --no-cache-dir is not 
>> generally required.
>>
>> Adam
>>
>>
>> On Thursday, May 2, 2019 at 3:59:24 PM UTC-5, mr.a...@gmail.com wrote:
>>>
>>> Ok, I was able to get past this step on my end, and first thing I think 
>>> you should check: is your virtual environment activated? Your command line 
>>> prompt should be prefixed with the name of the directory of your 
>>> virtualenv. In the docs we use ENV, so if you've followed that you should 
>>> be seeing (ENV) at the front of each line.
>>>
>>> The following is on windows, though I'll see about getting an ubuntu 
>>> test too.
>>>
>>>
>>> Please note that I don't recommend using echo to put the GDAL library 
>>> path in settings_local.py as I did in the example above--it will erase 
>>> the other contents of that file. Best to hand edit.
>>>
>>> If you still have trouble, could you send a screenshot or two?
>>>
>>> Thanks,
>>> Adam
>>>
>>> On Thursday, May 2, 2019 at 3:20:56 PM UTC-5, mr.a...@gmail.com wrote:
>>>>
>>>> Hi Colin and Martha,
>>>>
>>>> I'll try out a test installation locally and see what I can find. In 
>>>> the meantime, if you try pip installing captcha does that solve it, or 
>>>> lead 
>>>> to messages of new libraries that are missing?
>>>> Use
>>>>
>>>> pip install django-recaptcha==1.4.0
>>>>
>>>> as is listed here 
>>>> https://github.com/archesproject/arches/blob/stable/4.4.1/arches/install/requirements.txt#L14
>>>>
>>>> Adam
>>>>
>>>> On Thursday, May 2, 2019 at 1:24:06 PM UTC-5, Martha S wrote:
>>>>>
>>>>> Hi, All, 
>>>>>
>>>>> We are at exactly the same point in the 4.4.1 install with the same 
>>>>> issue. Any answers? We are on Ubuntu 18.04, pip 19.1, and Python 
>>>>> 2.7.15rc1.
>>>>>
>>>>> Martha
>>>>>
>>>>> On Wednesday, May 1, 2019 at 7:10:49 PM UTC-7, Colin Wu wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I am trying to install Arches on a Ubuntu 16.04 desktop and python 
>>>>>> 2.7.12. Everything seems to go swimmingly until I reach the "Install 
>>>>>> Elasticsearch with Arches" section!
>>>>>>
>>>>>> Running the suggested command (python manage.py es install) gives me 
>>>>>> errors that ultimately result from the script not being able to find a 
>>>>>> captcha module (ImportError: No module named captcha).
>>>>>>
>>>>>> I searched the forum and found (old) posts about not finding the 
>>>>>> captcha module during an upgrade from 4.0.1 to 4.1.0. Tried the 
>>>>>> suggestions 
>>>>>> there but no joy.
>>>>>>
>>>>>> I note that 4.4.1 was only released March 29 (?