subprocess-exited-with-error while install

[pritam0070]

Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [416 lines of output]
performance hint: pomegranate/BayesianNetwork.pyx:479:56: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/BayesianNetwork.pyx:1168:51: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/BayesianNetwork.pyx:2785:24: Exception check after calling '_log2' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/BayesianNetwork.pyx:2789:16: Exception check after calling '_log2' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/MarkovNetwork.pyx:248:56: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:263:54: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/bayes.pyx:265:37: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:274:64: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:284:68: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:290:45: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/bayes.pyx:300:85: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/bayes.pyx:301:42: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/bayes.pyx:411:39: Exception check after calling '_predict_log_proba' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict_log_proba' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict_log_proba' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:419:43: Exception check after calling '_predict_log_proba' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict_log_proba' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict_log_proba' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:429:78: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/bayes.pyx:432:72: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:442:32: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/bayes.pyx:517:29: Exception check after calling '_predict' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:525:33: Exception check after calling '_predict' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict' to allow an error code to be returned.
performance hint: pomegranate/bayes.pyx:536:78: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/bayes.pyx:539:72: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/distributions/BetaDistribution.pyx:58:51: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/BetaDistribution.pyx:59:18: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/ConditionalProbabilityTable.pyx:338:26: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/ConditionalProbabilityTable.pyx:342:27: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/DirichletDistribution.pyx:46:51: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/GammaDistribution.pyx:58:30: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/GammaDistribution.pyx:58:53: Exception check after calling 'lgamma' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'lgamma' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/GammaDistribution.pyx:59:9: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/GammaDistribution.pyx:131:16: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/IndependentComponentsDistribution.pyx:133:25: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/distributions/IndependentComponentsDistribution.pyx:149:57: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/distributions/IndependentComponentsDistribution.pyx:191:18: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/distributions/IndependentComponentsDistribution.pyx:210:50: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/distributions/KernelDensities.pyx:163:28: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/KernelDensities.pyx:205:28: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/KernelDensities.pyx:248:28: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/LogNormalDistribution.pyx:52:30: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/LogNormalDistribution.pyx:53:13: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/LogNormalDistribution.pyx:72:18: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/MultivariateGaussianDistribution.pyx:92:20: Exception check after calling '_is_gpu_enabled' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_is_gpu_enabled' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/MultivariateGaussianDistribution.pyx:103:7: Exception check after calling 'mdot' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'mdot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'mdot' to allow an error code to be returned.
performance hint: pomegranate/distributions/MultivariateGaussianDistribution.pyx:109:44: Exception check after calling '_log_probability_missing' will always require the GIL to be acquired. Declare '_log_probability_missing' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/distributions/MultivariateGaussianDistribution.pyx:116:24: Exception check after calling '_is_gpu_enabled' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_is_gpu_enabled' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/MultivariateGaussianDistribution.pyx:181:20: Exception check after calling '_is_gpu_enabled' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_is_gpu_enabled' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/PoissonDistribution.pyx:57:59: Exception check after calling 'lgamma' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'lgamma' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/distributions/distributions.pyx:177:18: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/distributions/distributions.pyx:363:24: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/gmm.pyx:336:49: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/gmm.pyx:346:54: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/gmm.pyx:363:80: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/gmm.pyx:365:68: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/gmm.pyx:372:32: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/gmm.pyx:388:62: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:1371:45: Exception check after calling '_vl_log_probability' will always require the GIL to be acquired. Declare '_vl_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:1376:32: Exception check after calling '_forward' will always require the GIL to be acquired. Declare '_forward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:1385:30: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1437:30: Exception check after calling '_forward' will always require the GIL to be acquired. Declare '_forward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:1466:49: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:1498:30: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1515:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1533:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1552:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1556:29: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1608:21: Exception check after calling '_backward' will always require the GIL to be acquired. Declare '_backward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:1637:49: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:1683:30: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1707:30: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1738:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1765:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1770:25: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1786:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:1798:31: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:2070:48: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:2287:26: Exception check after calling '_predict_log_proba' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict_log_proba' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict_log_proba' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:2306:49: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:2316:19: Exception check after calling '_forward' will always require the GIL to be acquired. Declare '_forward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2317:20: Exception check after calling '_backward' will always require the GIL to be acquired. Declare '_backward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2325:39: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:2823:45: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2855:48: Exception check after calling '_log_probability' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log_probability' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_log_probability' to allow an error code to be returned.
performance hint: pomegranate/hmm.pyx:2862:19: Exception check after calling '_forward' will always require the GIL to be acquired. Declare '_forward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2863:20: Exception check after calling '_backward' will always require the GIL to be acquired. Declare '_backward' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2870:39: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:2892:56: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:2922:56: Exception check after calling 'pair_lse' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'pair_lse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:2954:42: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2984:54: Exception check after calling '_HiddenMarkovModel__viterbi_summarize' will always require the GIL to be acquired. Declare '_HiddenMarkovModel__viterbi_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:2999:45: Exception check after calling '_viterbi' will always require the GIL to be acquired. Declare '_viterbi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:3000:26: Exception check after calling '_HiddenMarkovModel__labeled_summarize' will always require the GIL to be acquired. Declare '_HiddenMarkovModel__labeled_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:3027:54: Exception check after calling '_HiddenMarkovModel__labeled_summarize' will always require the GIL to be acquired. Declare '_HiddenMarkovModel__labeled_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:3065:48: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/hmm.pyx:3217:53: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/hmm.pyx:3230:52: Exception check after calling '_log' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_log' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Declare any exception value explicitly for functions in pxd files.
performance hint: pomegranate/kmeans.pyx:294:16: Exception check after calling '_predict' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_predict' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_predict' to allow an error code to be returned.
performance hint: pomegranate/kmeans.pyx:566:25: Exception check after calling '_summarize' will always require the GIL to be acquired. Declare '_summarize' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pomegranate/kmeans.pyx:591:6: Exception check after calling 'mdot' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'mdot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'mdot' to allow an error code to be returned.
performance hint: pomegranate/utils.pxd:12:25: No exception value declared for '_is_gpu_enabled' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
  
  cpdef disable_gpu():
      global GPU
      GPU = False
  
  cdef ndarray_wrap_cpointer(void* data, numpy.npy_intp n):
       ^
  ------------------------------------------------------------
  
  pomegranate/utils.pyx:120:5: Function signature does not match previous declaration
  performance hint: pomegranate/utils.pyx:157:5: Exception check on 'mdot' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'mdot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'mdot' to allow an error code to be returned.
  performance hint: pomegranate/utils.pxd:17:17: No exception value declared for '_log' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: pomegranate/utils.pxd:18:18: No exception value declared for '_log2' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: pomegranate/utils.pxd:19:20: No exception value declared for 'pair_lse' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: pomegranate/utils.pxd:20:17: No exception value declared for 'gamma' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: pomegranate/utils.pxd:21:18: No exception value declared for 'lgamma' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  Compiling pomegranate/BayesClassifier.pyx because it changed.
  Compiling pomegranate/BayesianNetwork.pyx because it changed.
  Compiling pomegranate/FactorGraph.pyx because it changed.
  Compiling pomegranate/MarkovChain.pyx because it changed.
  Compiling pomegranate/MarkovNetwork.pyx because it changed.
  Compiling pomegranate/NaiveBayes.pyx because it changed.
  Compiling pomegranate/base.pyx because it changed.
  Compiling pomegranate/bayes.pyx because it changed.
  Compiling pomegranate/gmm.pyx because it changed.
  Compiling pomegranate/hmm.pyx because it changed.
  Compiling pomegranate/kmeans.pyx because it changed.
  Compiling pomegranate/parallel.pyx because it changed.
  Compiling pomegranate/utils.pyx because it changed.
  Compiling pomegranate/distributions/BernoulliDistribution.pyx because it changed.
  Compiling pomegranate/distributions/BetaDistribution.pyx because it changed.
  Compiling pomegranate/distributions/ConditionalProbabilityTable.pyx because it changed.
  Compiling pomegranate/distributions/DirichletDistribution.pyx because it changed.
  Compiling pomegranate/distributions/DiscreteDistribution.pyx because it changed.
  Compiling pomegranate/distributions/ExponentialDistribution.pyx because it changed.
  Compiling pomegranate/distributions/GammaDistribution.pyx because it changed.
  Compiling pomegranate/distributions/IndependentComponentsDistribution.pyx because it changed.
  Compiling pomegranate/distributions/JointProbabilityTable.pyx because it changed.
  Compiling pomegranate/distributions/KernelDensities.pyx because it changed.
  Compiling pomegranate/distributions/LogNormalDistribution.pyx because it changed.
  Compiling pomegranate/distributions/MultivariateGaussianDistribution.pyx because it changed.
  Compiling pomegranate/distributions/NormalDistribution.pyx because it changed.
  Compiling pomegranate/distributions/PoissonDistribution.pyx because it changed.
  Compiling pomegranate/distributions/UniformDistribution.pyx because it changed.
  Compiling pomegranate/distributions/distributions.pyx because it changed.
  [ 1/29] Cythonizing pomegranate/BayesClassifier.pyx
  [ 2/29] Cythonizing pomegranate/BayesianNetwork.pyx
  [ 3/29] Cythonizing pomegranate/FactorGraph.pyx
  [ 4/29] Cythonizing pomegranate/MarkovChain.pyx
  [ 5/29] Cythonizing pomegranate/MarkovNetwork.pyx
  [ 6/29] Cythonizing pomegranate/NaiveBayes.pyx
  [ 7/29] Cythonizing pomegranate/base.pyx
  [ 8/29] Cythonizing pomegranate/bayes.pyx
  [ 9/29] Cythonizing pomegranate/distributions/BernoulliDistribution.pyx
  [10/29] Cythonizing pomegranate/distributions/BetaDistribution.pyx
  [11/29] Cythonizing pomegranate/distributions/ConditionalProbabilityTable.pyx
  [12/29] Cythonizing pomegranate/distributions/DirichletDistribution.pyx
  [13/29] Cythonizing pomegranate/distributions/DiscreteDistribution.pyx
  [14/29] Cythonizing pomegranate/distributions/ExponentialDistribution.pyx
  [15/29] Cythonizing pomegranate/distributions/GammaDistribution.pyx
  [16/29] Cythonizing pomegranate/distributions/IndependentComponentsDistribution.pyx
  [17/29] Cythonizing pomegranate/distributions/JointProbabilityTable.pyx
  [18/29] Cythonizing pomegranate/distributions/KernelDensities.pyx
  [19/29] Cythonizing pomegranate/distributions/LogNormalDistribution.pyx
  [20/29] Cythonizing pomegranate/distributions/MultivariateGaussianDistribution.pyx
  [21/29] Cythonizing pomegranate/distributions/NormalDistribution.pyx
  [22/29] Cythonizing pomegranate/distributions/PoissonDistribution.pyx
  [23/29] Cythonizing pomegranate/distributions/UniformDistribution.pyx
  [24/29] Cythonizing pomegranate/distributions/distributions.pyx
  [25/29] Cythonizing pomegranate/gmm.pyx
  [26/29] Cythonizing pomegranate/hmm.pyx
  [27/29] Cythonizing pomegranate/kmeans.pyx
  [28/29] Cythonizing pomegranate/parallel.pyx
  [29/29] Cythonizing pomegranate/utils.pyx
  Traceback (most recent call last):
    File "/home/pk/miniconda3/envs/druggen/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
      main()
    File "/home/pk/miniconda3/envs/druggen/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
      json_out["return_val"] = hook(**hook_input["kwargs"])
    File "/home/pk/miniconda3/envs/druggen/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel
      return hook(config_settings)
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
      return self._get_build_requires(config_settings, requirements=[])
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
      self.run_setup()
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 522, in run_setup
      super().run_setup(setup_script=setup_script)
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 320, in run_setup
      exec(code, locals())
    File "<string>", line 61, in <module>
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
      cythonize_one(*args)
    File "/tmp/pip-build-env-ztds01r6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: pomegranate/utils.pyx
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.