-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add conflowgen #18124
Add conflowgen #18124
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 recipes/conflowgen:
|
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 recipes/conflowgen:
|
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 recipes/conflowgen:
|
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 ( |
It works locally when using `conda-build -c conda-forge -c domdfcoding ./recipes/conflowgen`, hopefully soon there will be clarification at domdfcoding/enum_tools#59 regarding the channel
Currently, not all of the tests are also shipped with the pip release. This will change soon. Then the pyargs approach [1] can be used as well. [1] https://docs.pytest.org/en/latest/explanation/goodpractices.html#tests-as-part-of-application-code
The PR is on hold as long as enum_tools is not on conda-forge. It is on pip as well as on the personal channel of domdfcoding though and the author is working on it - thanks a lot to him! |
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 recipes/conflowgen:
|
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but couldn't find any. |
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 ( |
I was trying to run this locally but at the time of working on it, the issue #18127 existed so that I could not check the pipeline locally. |
@1kastner, the linux error is |
Do you want to try to add enum_tools? You can add it here in a separate folder |
Make a new folder named enum_tools and add this meta.yaml: {% set name = "enum_tools" %}
{% set version = "0.9.0.post1" %}
package:
name: {{ name|lower }}
version: {{ version }}
source:
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/enum_tools-{{ version }}.tar.gz
sha256: e59eb1c16667400b185f8a61ac427029919be2ec48b9ca04aa1b388a42fb14d5
build:
noarch: python
script: {{ PYTHON }} -m pip install . -vv
number: 0
requirements:
host:
- pip
- python >=3.6
run:
- pygments >=2.6.1
- python >=3.6
- typing-extensions >=3.7.4.3
test:
imports:
- enum_tools
commands:
- pip check
requires:
- pip
about:
home: https://github.com/domdfcoding/enum_tools
summary: Tools to expand Python's enum module.
license: LGPL-3.0
license_file: LICENSE
extra:
recipe-maintainers:
- (your name?) |
{% set name = "conflowgen" %}
{% set version = "1.0.2" %}
package:
name: {{ name|lower }}
version: {{ version }}
source:
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/conflowgen-{{ version }}.tar.gz
sha256: c7c35a8ff153277166fbd052156ee1b83279ec8b3a1b468fc4815a7cff3bc04c
build:
noarch: python
script: {{ PYTHON }} -m pip install . -vv
number: 0
requirements:
host:
- pip
- python
run:
- enum-tools
- kaleido-core
- python-kaleido
- matplotlib-base
- numpy
- openpyxl
- pandas
- peewee
- plotly
- python
- seaborn
test:
imports:
- conflowgen
commands:
- pip check
requires:
- pip
about:
home: https://github.com/1kastner/conflowgen
summary: A generator for synthetic container flows at maritime container terminals with a focus on yard operations
license: MIT
license_file: LICENSE
extra:
recipe-maintainers:
- (your name) |
The original author of the package was so nice that he said he was going to do so. A bit of discussion can be found at domdfcoding/enum_tools#59. You can see that his package comes with quite some dependencies that need to be moved to conda-forge as well. I am very thankful that @domdfcoding mentioned he would do this step! Several of these packages already exist on his personal Anaconda channel. I am not 100% where this process is at now and how the dependency tree looks in its entirety, I only saw that the PR at #18361 got stuck because of a technical bug. It would be great and very helpful if @domdfcoding could comment on this. |
You prepared a different recipe and suggested that I should use yours instead. I guess it was automatically generated by grayskull? You list some of the optional dependencies and this made me thinking - the setup.py file in my repo was not precise enough. I will rework that because the recipe I showed here is what I actually intended to publish. |
I'm very sorry for not getting to this sooner. |
@domdfcoding I did not create a PR yet because I did not want to interfere with your specific versioning and packaging planning. I saw that you created a very nice collection of many tools with interdependencies. If it suits to your current concept and you have some capacities, I would prefer to leave it in your hands. If I can be of any help, please let me know! |
@domdfcoding the following enum_tools recipe worked for me: {% set name = "enum_tools" %}
{% set version = "0.9.0.post1" %}
package:
name: {{ name|lower }}
version: {{ version }}
source:
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/enum_tools-{{ version }}.tar.gz
sha256: e59eb1c16667400b185f8a61ac427029919be2ec48b9ca04aa1b388a42fb14d5
build:
noarch: python
script: {{ PYTHON }} -m pip install . -vv
number: 0
requirements:
host:
- pip
- python >=3.6
- setuptools
- whey
run:
- pygments >=2.6.1
- python >=3.6
- typing-extensions >=3.7.4.3
test:
imports:
- enum_tools
commands:
- pip check
requires:
- pip
about:
home: https://github.com/domdfcoding/enum_tools
summary: Tools to expand Python's enum module.
license: LGPL-3.0
license_file: LICENSE
extra:
recipe-maintainers:
- XXX But I guess it is easier for you to adjust to new circumstances as your modules evolve. |
With #18645, it should be solved very quickly! |
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 recipes/sarsen:
For recipes/xarray-sentinel:
|
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 ( |
@ngam thank you for your patience. Now it is done! Finally this is ready to merge! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks perfect. Unfortunately, I don't have merge rights here, but my unofficial review may accelerate an official review and merge!
@conda-forge/staged-recipes this is ready, thank you! |
@BastianZim nice job on those labels!!! (Love the colors too) |
@conda-forge/help-python ready for review (adding to see if we have a python label) |
Thank you @ngam for the review and support! |
@@ -1,50 +0,0 @@ | |||
{% set name = "gi-docgen" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase or, if that is easier, resubmit your recipe without deleting what was already there. The infrastructure handles this automatically and deleting them manually may cause problems.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only did this because of the linter statement at #18124 (comment). I will continue as proposed.
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).