##// END OF EJS Templates
extensions: prevent a crash on py3 when testing a bad extension minimum...
extensions: prevent a crash on py3 when testing a bad extension minimum A `None` placeholder is populated for each missing component by `util.versiontuple()`, which could safely be used with `>` on py2, but not py3. I guess there's another hole here where if the string is entirely bogus (i.e no numbers), it will be treated as 0.0, and always load. But that's always been the case. Differential Revision: https://phab.mercurial-scm.org/D11475

File last commit:

r46195:426294d0 default
r48828:a9bedc56 default
Show More
build.rs
18 lines | 577 B | application/rls-services+xml | RustLexer
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at https://mozilla.org/MPL/2.0/.
/*! Build script to integrate PyOxidizer. */
fn main() {
if let Ok(config_rs) =
std::env::var("DEP_PYTHONXY_DEFAULT_PYTHON_CONFIG_RS")
{
println!(
"cargo:rustc-env=PYOXIDIZER_DEFAULT_PYTHON_CONFIG_RS={}",
config_rs
);
} else {
panic!("unable to find build artifacts generated by pyembed crate");
}
}