Update to 1.0.1

[ericpre]

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy
• Ensured the license file is being packaged.

Close #16.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[ericpre]

@conda-forge/prettytable, this PR is ready for review.

[ericpre]

cc @hugovk.

[hugovk]

I'm not very familiar with conda-forge, but the updated URL and dependencies look right 👍

[ericpre]

Ping @conda-forge/prettytable, could you please review this PR?

[conda-forge-linter]

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 (recipe) and found some lint.

Here's what I've got...

For recipe:

• noarch: python recipes are recommended to have a lower bound on minimum python bound. This recommendation will become requirement in a future version.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[ericpre]

@conda-forge/core, would it be possible to get this PR merged?

From a quick search on github of the maintainer of this recipe (https://github.com/orgs/conda-forge/teams/prettytable/members), they don't seem to be active anymore on conda-forge. I have added myself to help with the maintenance of this recipe.

@hugovk, would you like to be added as recipe maintainer too, since you are now maintaining prettytable? It would be useful if you could follow what is going on with this recipe!

[chrisburr]

@conda-forge-admin, please rerender

[ocefpaf]

@conda-forge-admin please rerender

[ocefpaf]

Oops... @chrisburr was faster than me 😄

[chrisburr]

Oops... @chrisburr was faster than me 😄

You got a full commit in before I commented!

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

[ericpre]

Thanks!

[hugovk]

I'm not very familiar with Conda so not sure I'd be able to maintain this recipe. I am watching this repo though, and will comment if there's anything I spot. For example:

PrettyTable 1.0.1 actually supports 2.7 and 3.5+, but fine if this recipe is only for 3.5+. It's very unlikely we'd fix anything for Python 2.

The next PrettyTable release (probably 2.0.0) will be 3.6+. The EOL versions are already dropped in master.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[ocefpaf]

I'm not very familiar with Conda so not sure I'd be able to maintain this recipe. I am watching this repo though, and will comment if there's anything I spot. For example:

PrettyTable 1.0.1 actually supports 2.7 and 3.5+, but fine if this recipe is only for 3.5+. It's very unlikely we'd fix anything for Python 2.

The next PrettyTable release (probably 2.0.0) will be 3.6+. The EOL versions are already dropped in master.

@hugovk thanks! That kind of info is why having authors as maintainers is important. You don't need to worry about the conda details if you can every-now-and-them make comments like that. At the moment we are not building 2.7 and, while it would be nice to have it there for completeness, it won't get built. We need to watch out for the next release and update the Python constraint.