Add a couple workarounds
@@ -23,12 +23,18 @@ build:
# In theory the requirements can/should be specified per-output, but in practice
# conda-build will produce a corrupt package if the compiler dependency is not
-# additionally specified at this top scope. It is required to declare the dependency
-# both here and in the outputs: section as well; removing either will cause the c
-# compiler to not be installed.
+# additionally specified at this top scope. It is required to declare the
+# compiler dependency both here and in the outputs: section as well; removing
+# either will cause the c compiler to not be installed.
+#
+# It's also required to specify a "python" dependency in this section so that
+# conda-build knows that this package is sensitive to the python version.
+# (It does not infer this from the py!=38 jinja selector)
requirements:
build:
- {{ compiler('c') }}
+ host:
+ - python
outputs:
- name: pyston_lite
@@ -38,8 +44,8 @@ outputs:
# An "build" section is required, or else it seems to skip
# the build in certain build scenarios:
build:
- # This section cannot be empty or the conda-smithy linter crashes
- -
+ # This build section cannot be empty or else it will crash the linter
+ script: true
requirements:
build:
