> On Oct 22, 2014, at 23:59, Márk Csaba wrote:
>
> Hello Thomas,
>
> thanks for the suggestion.
> Out developers would like to use different versions with pkg_resources
> switched from code, not from virtualenv.
> I've modified the easy_install.pth but adding both version lead me to
> VersionCo
> On Oct 22, 2014, at 23:59, Márk Csaba wrote:
>
> Hello Thomas,
>
> thanks for the suggestion.
> Out developers would like to use different versions with pkg_resources
> switched from code, not from virtualenv.
> I've modified the easy_install.pth but adding both version lead me to
> VersionCo
Hello Thomas,
thanks for the suggestion.
Out developers would like to use different versions with pkg_resources
switched from code, not from virtualenv.
I've modified the easy_install.pth but adding both version lead me to
VersionConflict error.
The solution was to remove all pylucene line from e
> On Oct 22, 2014, at 20:22, Márk Csaba wrote:
>
> Hello,
>
> I'm trying to install 4.9.0 and 4.10.1 to the same python, but pip list shows
> only the last one.
> How can I install lucene from source not to overwrite or deregister the
> previous one?
Create python virtualenv setups. This all
Hi Caba,
you probably have both ‚installed‘ - i.e. both versions are copied into your
global python’s site-packages directory, but only one is enabled by the
installer (pip or easy-install). The ‚active‘ packages are added to the python
sys.path - this is typically done in a file ‚easy-install.
Hello,
I'm trying to install 4.9.0 and 4.10.1 to the same python, but pip list shows
only the last one.
How can I install lucene from source not to overwrite or deregister the
previous one?
Thanks,
Csaba
