All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Trevor Gamblin" <trevor.gamblin@windriver.com>
To: Leon Anavi <leon.anavi@konsulko.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-python][PATCH 3/5] python3-pyscaffold: Upgrade 3.3.1 -> 4.0
Date: Mon, 15 Mar 2021 09:01:08 -0400	[thread overview]
Message-ID: <09689b41-7ff8-bf34-729a-070ee84307b1@windriver.com> (raw)
In-Reply-To: <20210312162600.8335-3-leon.anavi@konsulko.com>

[-- Attachment #1: Type: text/plain, Size: 3906 bytes --]


On 2021-03-12 11:25 a.m., Leon Anavi wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> Upgrade to release 4.0:
>
> - Cookiecutter, Django and Travis extensions extracted to their
>    own repositories
> - Support for Python 3.4 and 3.5 dropped
> - Dropped deprecated requirements.txt file
> - Added support for global configuration (avoid retyping common
>    putup's options)
> - PyScaffold is no longer a build-time dependency, it just
>    generates the project structure
> - Removed contrib subpackage, vendorized packages are now runtime
>    dependencies
> - setuptools_scm is included by default in setup.cfg, setup.py and
>    pyproject.toml
> - API changed to use pyscaffold.operations instead of integer
>    flags
> - Allow string.Template and callable as file contents in project
>    structure
> - Extract file system functions from utils.py into file_system.py
> - Extract identification/naming functions from utils.py into
>    identification.py
> - Extract action related functions from api/__init__.py to
>    actions.py
> - helpers.{modify,ensure,reject} moved to structure.py
> - helpers.{register,unregister} moved to actions.py
> - New extension for automatically creating virtual environments
>    (--venv)
> - Added instructions to use pip-tools to docs
> - pre-commit extension now attempts to install hooks automatically
> - A nice message is now displayed when PyScaffold finishes running
>    (actions.report_done)
> - Removed mutually exclusive argparse groups for extensions
> - Progressive type annotations adopted in the code base together
>    with mypy linting
> - Simplified isort config
> - pyproject.toml and isolated builds adopted by default
> - Added comment to setup.cfg template instructing about extra links
> - Generate tox.ini by default
> - Replace pkg_resources with importlib.{metadata,resources} and
>    packaging
> - Adopt PEP 420 for namespaces
> - Adopt SPDX identifiers for the license field in setup.cfg
> - Removed deprecated log.configure_logger
> - Add links to issues and pull requests to changelog
> - Add an experimental --interactive mode (inspired by git rebase -i)
> - Reorganise the FAQ (including version questions previously in
>    Features)
> - Updated setuptools and setuptools_scm dependencies to minimal
>    versions 46.1 and 5, respectively
> - Adopted no-guess-dev version scheme from setuptools_scm
>    (semantically all stays the same, but non-tag commits are now
>    versioned LAST_TAG.post1.devN instead of LAST_TAG.post0.devN)
> - Fix problem of not showing detailed log with --verbose if error
>    happens when loading extensions
>
> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
> ---
>   .../{python3-pyscaffold_3.3.1.bb => python3-pyscaffold_4.0.bb}  | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>   rename meta-python/recipes-devtools/python/{python3-pyscaffold_3.3.1.bb => python3-pyscaffold_4.0.bb} (85%)
>
> diff --git a/meta-python/recipes-devtools/python/python3-pyscaffold_3.3.1.bb b/meta-python/recipes-devtools/python/python3-pyscaffold_4.0.bb
> similarity index 85%
> rename from meta-python/recipes-devtools/python/python3-pyscaffold_3.3.1.bb
> rename to meta-python/recipes-devtools/python/python3-pyscaffold_4.0.bb
> index 9bebcedd3..1ad33c10d 100644
> --- a/meta-python/recipes-devtools/python/python3-pyscaffold_3.3.1.bb
> +++ b/meta-python/recipes-devtools/python/python3-pyscaffold_4.0.bb
> @@ -12,6 +12,6 @@ inherit pypi setuptools3
>
>   PYPI_PACKAGE = "PyScaffold"
>
> -SRC_URI[sha256sum] = "1c3a2b76e60319b6ffc2a8b54e240382109c6241576bf0a47ea476c7194f6a69"
> +SRC_URI[sha256sum] = "7012ae5f9c95b910a39a099824104dc888beb932de86b07514882f3511bc6c74"
>
>   BBCLASSEXTEND = "native nativesdk"
> --
> 2.17.1
>
>
> 
>

[-- Attachment #2: Type: text/html, Size: 4572 bytes --]

  reply	other threads:[~2021-03-15 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 16:25 [meta-python][PATCH 1/5] python3-waitress: Upgrade 1.4.4 -> 2.0.0 Leon Anavi
2021-03-12 16:25 ` [meta-python][PATCH 2/5] python3-pako: Upgrade 0.3.0 -> 0.3.1 Leon Anavi
2021-03-15 13:00   ` [oe] " Trevor Gamblin
2021-03-12 16:25 ` [meta-python][PATCH 3/5] python3-pyscaffold: Upgrade 3.3.1 -> 4.0 Leon Anavi
2021-03-15 13:01   ` Trevor Gamblin [this message]
2021-03-12 16:25 ` [meta-python][PATCH 4/5] python3-croniter: Upgrade 1.0.6 -> 1.0.8 Leon Anavi
2021-03-15 13:01   ` [oe] " Trevor Gamblin
2021-03-12 16:26 ` [meta-python][PATCH 5/5] python3-prompt-toolkit: Upgrade 3.0.16 -> 3.0.17 Leon Anavi
2021-03-15 13:01   ` [oe] " Trevor Gamblin
2021-03-15 13:00 ` [oe] [meta-python][PATCH 1/5] python3-waitress: Upgrade 1.4.4 -> 2.0.0 Trevor Gamblin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09689b41-7ff8-bf34-729a-070ee84307b1@windriver.com \
    --to=trevor.gamblin@windriver.com \
    --cc=leon.anavi@konsulko.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.