[
https://issues.apache.org/jira/browse/PYLUCENE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Vajda closed PYLUCENE-31.
--
Resolution: Fixed
distutils is on its way out with Python 3.12
> JCC Parallel/Multiproc
w if you have any questions about the
code when you have a look. I'm happy to help!
> JCC Parallel/Multiprocess Compilation + Caching
> ---
>
> Key: PYLUCENE-31
> URL: https://issues.apache.org
ssue. My apologies.
My reservations about maintaining more monkey patches still stand but I need to
review the patch to see how 'bad' it actually is.
> JCC Parallel/Multiprocess Compilation + Caching
> ---
>
>
to review/try this? Maybe it's
> a little too experimental, but thoughts appreciated. :-)
>
>> JCC Parallel/Multiprocess Compilation + Caching
>> ---
>>
>>Key: PYLUCENE-31
>>URL: https://is
ance to review/try this? Maybe it's a
little too experimental, but thoughts appreciated. :-)
> JCC Parallel/Multiprocess Compilation + Caching
> ---
>
> Key: PYLUCENE-31
> URL: https://issues.apache.org
lel/Multiprocess Compilation + Caching
> ---
>
> Key: PYLUCENE-31
> URL: https://issues.apache.org/jira/browse/PYLUCENE-31
> Project: PyLucene
> Issue Type: Improvement
> Environment:
[
https://issues.apache.org/jira/browse/PYLUCENE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Skillen updated PYLUCENE-31:
Attachment: (was: feature-parallel-build.patch)
> JCC Parallel/Multiprocess Compilat
[
https://issues.apache.org/jira/browse/PYLUCENE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Skillen updated PYLUCENE-31:
Attachment: feature-parallel-build.patch
> JCC Parallel/Multiprocess Compilation + Cach
Lee Skillen created PYLUCENE-31:
---
Summary: JCC Parallel/Multiprocess Compilation + Caching
Key: PYLUCENE-31
URL: https://issues.apache.org/jira/browse/PYLUCENE-31
Project: PyLucene
Issue Type
On 14 July 2014 23:19, Andi Vajda wrote:
>
> Hi Lee,
>
>> On Jul 14, 2014, at 19:01, Lee Skillen wrote:
>>
>> Hi,
>>
>> We've been utilising JCC frequently recently during development and
>> often have a need to recompile our JCC-based extensions due to changes
>> in the wrapped code - Doing so
Hi Lee,
> On Jul 14, 2014, at 19:01, Lee Skillen wrote:
>
> Hi,
>
> We've been utilising JCC frequently recently during development and
> often have a need to recompile our JCC-based extensions due to changes
> in the wrapped code - Doing so incurs a reasonably lengthy
> re-compilation effort
Hi,
We've been utilising JCC frequently recently during development and
often have a need to recompile our JCC-based extensions due to changes
in the wrapped code - Doing so incurs a reasonably lengthy
re-compilation effort due to the serial nature of the extension
building via distutils.
To help
12 matches
Mail list logo
