[ 
https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Petrus Hyvönen updated PYLUCENE-70:
-----------------------------------
    Description: 
The --generate seems to be missing double 
in package_dir parameter on windows platform

In tests at JCC conda build feedstock 
([https://github.com/conda-forge/jcc-feedstock/tree/main/recipe/test/java-example-test-parameters])

--generates gives a setup.py with row:
    
       package_dir={"test1": "build\test1"},

 
But should be:

      package_dir={"test1": "build\\test1"},


  was:
The --generate seems to be missing double 
in package_dir parameter on windows platform

In tests at JCC conda build feedstock 
([https://github.com/conda-forge/jcc-feedstock/tree/main/recipe/test/java-example-test-parameters])

--generates gives a setup.py with row:
{color:#d4d4d4}  
{color}{color:#9cdcfe}package_dir{color}{color:#d4d4d4}={{color}{color:#ce9178}"test2"{color}{color:#d4d4d4}:
 {color}{color:#ce9178}"build\{color}test2"\{color}},
 
But should be:
{{  
package_dir}}{color}{{{}{color:#d4d4d4}={{color}{color:#ce9178}"test2"{color}{color:#d4d4d4}:
 {color}{color:#ce9178}"build\\{color}{color:#ce9178}test2"}{color},{}}}
{{ }}


> JCC --generate missing additional \ on windows
> ----------------------------------------------
>
>                 Key: PYLUCENE-70
>                 URL: https://issues.apache.org/jira/browse/PYLUCENE-70
>             Project: PyLucene
>          Issue Type: Bug
>         Environment: Windows11, conda python package
>            Reporter: Petrus Hyvönen
>            Priority: Blocker
>
> The --generate seems to be missing double 
> in package_dir parameter on windows platform
> In tests at JCC conda build feedstock 
> ([https://github.com/conda-forge/jcc-feedstock/tree/main/recipe/test/java-example-test-parameters])
> --generates gives a setup.py with row:
>     
>        package_dir={"test1": "build\test1"},
>  
> But should be:
>       package_dir={"test1": "build\\test1"},



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to