|
| 1 | +#!/usr/bin/env bash |
| 2 | + |
| 3 | +# Licensed to the Apache Software Foundation (ASF) under one or more |
| 4 | +# contributor license agreements. See the NOTICE file distributed with |
| 5 | +# this work for additional information regarding copyright ownership. |
| 6 | +# The ASF licenses this file to You under the Apache License, Version 2.0 |
| 7 | +# (the "License"); you may not use this file except in compliance with |
| 8 | +# the License. You may obtain a copy of the License at |
| 9 | +# |
| 10 | +# http://www.apache.org/licenses/LICENSE-2.0 |
| 11 | +# |
| 12 | +# Unless required by applicable law or agreed to in writing, software |
| 13 | +# distributed under the License is distributed on an "AS IS" BASIS, |
| 14 | +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 15 | +# See the License for the specific language governing permissions and |
| 16 | +# limitations under the License. |
| 17 | + |
| 18 | +# A simple example of how to customize your python dependencies while re-using |
| 19 | +# as much as the pinned ones from the true-and-tested ones |
| 20 | + |
| 21 | +# first, create your own `requirements.in` file, as this example file |
| 22 | +# see `requirements/requirements-custom-example.in` as an example |
| 23 | + |
| 24 | +# copy the pinned dependency so that we can make it the target outpout for pip-compile |
| 25 | +# here we're getting pip-compile into using its output as an input |
| 26 | +cp requirements/development.txt requirements/requirements-custom-example.txt |
| 27 | + |
| 28 | +# pip-compile mixing your input and output (which also acts as the basis) |
| 29 | +pip-compile -o requirements-custom-example.in requirements-custom-example.in |
| 30 | + |
| 31 | +# this ideally is done as part of the release process, whenever any |
| 32 | +# of the files referenced here change, including requirements/development.txt |
0 commit comments