moved startup script to own module

[k-dominik]

I forgot to include the startup script in the conda package for a reason ;)

I did try to use the setup.py scripts directive, but this will not work reliably as an entrypoint in conda.

note: this entrypoint has to run before any import of an ilastik module.

[emilmelnikov]

Should we create an issue in the conda-build repo? This behaviour looks like a bug...

[codecov]

Codecov Report

Merging #2547 (8312538) into main (28bb8dc) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2547      +/-   ##
==========================================
+ Coverage   51.56%   51.57%   +0.01%     
==========================================
  Files         514      514              
  Lines       60141    60141              
  Branches     9169     9169              
==========================================
+ Hits        31009    31019      +10     
+ Misses      27522    27514       -8     
+ Partials     1610     1608       -2     

Impacted Files	Coverage Δ
lazyflow/operators/generic.py	88.97% <0.00%> (-0.20%)	⬇️
...ets/objectClassification/opObjectClassification.py	80.46% <0.00%> (-0.10%)	⬇️
lazyflow/slot.py	89.93% <0.00%> (+0.30%)	⬆️
lazyflow/operator.py	79.74% <0.00%> (+0.94%)	⬆️
lazyflow/operators/opPixelFeaturesPresmoothed.py	91.28% <0.00%> (+1.74%)	⬆️
lazyflow/operators/opReorderAxes.py	90.74% <0.00%> (+1.85%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 28bb8dc...8312538. Read the comment docs.

[k-dominik]

I think this might have been my bad...

[k-dominik]

okay this one is really annoying. I tried different variants, also following the conda-build tests that test that it actually should be working, but I never got an exe file on windows for the script when supplied as scripts in setup.cfg (hence I closed #2549, and reopened this one.). I think this is related to conda/conda-build#3965.

[emilmelnikov]

Do we even need an entrypoint for non-packaged ilastik variants? I think devs and people who want to use conda-based ilastik should be fine with python ilastik.py ... instead of ./ilastik ....

[k-dominik]

I'm thinking not of devs but people who install ilastik using conda. They should be able to ilastik to start.

[k-dominik]

turns out this might be some conda build issue (tracking it here: conda/conda-build#4385). So in order to keep things noarch, an explicit entrypoint is (currently) needed.

cc: @emilmelnikov

[emilmelnikov]

Maybe rename the module to ilastik.main, or at least ilastik.startup?