Update recipe to point to Paolo Herrera's official site #1
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
xylar
force-pushed
the
point_to_official_repo
branch
from
bbb5e77
to
0675520
Compare
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
@renefritze, I hope you will be okay with me adding myself as a maintainer. I also hope you will not find me too pushy having made such a substantial revision to this feedstock. I really do appreciate the work you've put into it. My colleagues and I use EVTK quite a lot to convert our model output to VTK format for visualization in ParaView, so we are really excited to have a package on conda-forge to use, rather than maintaining our own recipe on our own anaconda channel. |
|
@conda-forge-admin, please rerender |
xylar
force-pushed
the
point_to_official_repo
branch
from
86131ad
to
de01228
Compare
|
@conda-forge-admin, please rerender |
…nda-forge-pinning 2019.03.12
|
Similarly to conda-forge/python-slugify-feedstock#12, Appveyor shouldn't be running here because this is a Nevertheless, I think it is safe to merge. |
|
I'm closing this for now, based on the discussion in pyscience-projects/pyevtk#7 |
Checklist
conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)I was ready to create a feedstock for pyevtk when I realized to my amazement that someone had done so already! @renefritze, thank you very much for getting this started and for maintaining a mirror repo.
However, I've been in touch with @paulo-herrera and asked him to make an official v1.1.1 tag. In the process, he has decided to move the official site from BitBucket to GitHub. This should mean there is no longer a need to maintain the mirror repo at https://github.com/pyscience-projects/pyevtk (indeed, doing so could lead to confusion). I'll post an issue there as well.
@paulo-herrera also asked me to update the conda-forge feedstock to point to this new site. In the process, I needed to make a small patch (because README.txt was renamed to README.md but updates were not made to the MANIFEST and setup.py until after the v1.1.1 tag).
There is no longer a need to include the LICENSE or test in the recipe as they are part of the package, so I have removed them. I decided to run the full suite of examples as tests, since they are all extremely fast.