gh-142903: add conda-forge license for pixi-packages #143468
Conversation
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
|
Could you word-wrap to match https://github.com/conda-forge/python-feedstock/blob/main/LICENSE.txt (and to make this readable without scrolling)? |
|
done |
|
You need to update your branch to fix the CI. |
|
out of interest, is the 'update branch' button not available to maintainers too? |
|
It is, I just don't want to cause you any trouble if you have local changes :-) |
|
should be good to go @encukou |
Doc/license.rst
Outdated
| license:: | ||
|
|
||
| BSD-3-Clause license | ||
| Copyright (c) 2015-2022, conda-forge contributors |
There was a problem hiding this comment.
you might want to proactively pick up the changes from conda-forge/conda-smithy#2458 here
| Copyright (c) 2015-2022, conda-forge contributors | |
| Copyright (c) 2015-2026, conda-forge contributors |
There was a problem hiding this comment.
Oh, wait, that's for the conda-smithy repo. Will it get copied to python-feedstock?
There was a problem hiding this comment.
conda-smithy is the main tool for taking care of feedstocks. It defines how feedstocks are updated ("rerendered"), and defines the baseline of what those feedstocks are made of (that's why that file is in a folder called feedstock_contents). As soon as a new smithy version is released (usually every couple of weeks), all feedstocks will get an updated copyright year in the course of regular maintenance.
Speaking as someone from cf/core, it was only due to a simple oversight that the copyright year wasn't updated. I can even push this change to the python feedstock manually if that makes you happy. 🙃
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
6 participants
cc @AA-Turner @isuruf
📚 Documentation preview 📚: https://cpython-previews--143468.org.readthedocs.build/