The malformed PACKAGECONFIG looks like this:

PACKAGECONFIG[:python_version < "3.8"] = ",,,python3-typing-extensions"
PACKAGECONFIG[standard] = ",,,python3-pyyaml python3-httptools python3-python-dotenv python3-watchgod python3-websockets"
PACKAGECONFIG[standard:sys_platform != "win32" and (sys_platform != "cygwin" and platform_python_implementation != "pypy")] = ",,,python3-uvloop!"
PACKAGECONFIG[standard:sys_platform == "win32"] = ",,,python3-colorama"


Which is taken from the extras_require parameter to setuptools.

Hello Ross, I wish to ask if this bug is resolved since its been almost a year since this was put up.

And also, I would like to know how to reproduce this bug.

Abongwa,

Yes it still reproduces with master, the way to see this is run the devtool command that is listed in the first comment.  I tested this yesterday.

The problem is that pysetuptools sees the uvicorn.egg-info/requires.txt as extra requirements.  Recipetool parses this information to generate the PACKAGECONFIG lines, specifically the python parsing function in create_buildsys_python.py (in scripts/lib/recipetool). There is a set of characters in the replacements variable and code in apply_info_replacements(). This code probably needs to be fixed to handle the "bad" lines:

[:python_version < "3.8"]
typing-extensions

[standard:sys_platform != "win32" and (sys_platform != "cygwin" and platform_pyt
hon_implementation != "PyPy")]
uvloop!=0.15.0,!=0.15.1,>=0.14.0

[standard:sys_platform == "win32"]
colorama>=0.4

Are you interested in helping out on this, if so, you can assign the bug to yourself.

did pick this bug as my first to solve (NEWCOMER)
I think I found a solution, but I'm a bit unsure what the expected behavior is.
I don't see any support for expressions in PACKAGECONFIG eg. 
PACKAGECONFIG[:python_version < "3.8"] so those should not be added to the bb recipe.
I add a simple check to exclude any PACKAGECONFIG, which contains an expression.
Is this the right way to go or is something else expected?

Yes, that would be the general approach, it would be good if possible to provide a warning saying that recipetool was unable to parse or add those PACKAGECONFIG either as output or as a comment in the new recipe bb file.

I did rework my patch (https://bpa.st/SXEQ) instead of just omitting that malformed lines my current approach is to replace the expression (parsed from requires.txt) by a parsable replacement that can be enabled manually. 
E.g.
#PACKAGECONFIG ?= "pythonversionsmaller3dot8 standard standardsysplatformnotequalswin32andsysplatformnotequalscygwinandplatformpythonimplementationnotequalspypy standardsysplatformequalsequalswin32"
PACKAGECONFIG[pythonversionsmaller3dot8] = ",,,python3-typing-extensions"
PACKAGECONFIG[standard] = ",,,python3-pyyaml python3-httptools python3-python-dotenv python3-watchgod python3-websockets"
PACKAGECONFIG[standardsysplatformnotequalswin32andsysplatformnotequalscygwinandplatformpythonimplementationnotequalspypy] = ",,,python3-uvloop!"
PACKAGECONFIG[standardsysplatformequalsequalswin32] = ",,,python3-colorama"

This will work for the uvicorn package. Is there any test to check that my modifications do not break anything?

(In reply to comment #7)
> I did rework my patch (https://bpa.st/SXEQ) instead of just omitting that
> malformed lines my current approach is to replace the expression (parsed
> from requires.txt) by a parsable replacement that can be enabled manually. 
> E.g.
> #PACKAGECONFIG ?= "pythonversionsmaller3dot8 standard
> standardsysplatformnotequalswin32andsysplatformnotequalscygwinandplatformpyth
> onimplementationnotequalspypy standardsysplatformequalsequalswin32"
> PACKAGECONFIG[pythonversionsmaller3dot8] = ",,,python3-typing-extensions"
> PACKAGECONFIG[standard] = ",,,python3-pyyaml python3-httptools
> python3-python-dotenv python3-watchgod python3-websockets"
> PACKAGECONFIG[standardsysplatformnotequalswin32andsysplatformnotequalscygwina
> ndplatformpythonimplementationnotequalspypy] = ",,,python3-uvloop!"
> PACKAGECONFIG[standardsysplatformequalsequalswin32] = ",,,python3-colorama"
> 
> This will work for the uvicorn package. Is there any test to check that my
> modifications do not break anything?

I would suggest adding spaces for better readability.  You could just change the replace lines to add a space for the "" or add spaces around the words your replacing.

No, but you should consider adding a test using the uvicorn package to ensure it's parsed correctly.  Take a look at meta-selftest.

spaces are not allowed, but - (hyphens) are ok. Should improve the readability as lot as well:

#PACKAGECONFIG ?= "python-version-smaller-3-dot-8 standard standardsys-platform-not--equals-win32andsys-platform-not--equals-cygwinandplatform-python-implementation-not--equals-pypy standardsys-platform-equals--equals-win32"
PACKAGECONFIG[python-version-smaller-3-dot-8] = ",,,python3-typing-extensions"
PACKAGECONFIG[standard] = ",,,python3-pyyaml python3-httptools python3-python-dotenv python3-watchgod python3-websockets"
PACKAGECONFIG[standardsys-platform-not--equals-win32andsys-platform-not--equals-cygwinandplatform-python-implementation-not--equals-pypy] = ",,,python3-uvloop!"
PACKAGECONFIG[standardsys-platform-equals--equals-win32] = ",,,python3-colorama"

unsure about the bugzilla workflow
I did send my patch to the mailing list. It got merged into master-next and master
https://lists.openembedded.org/g/openembedded-core/message/167334?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3ACreated%2C%2CPACKAGECONFIG%2C20%2C2%2C0%2C92039954
- so what is next? 
- Who should close the bug?

You can, as you sent the patch, but I'll do it now.

Fixed in oe-core a854d95a79e64f3f82abfa4cc1daec750abf4249

bulk change to add Saul's non-WR address.

Bulk change: Remove Saul's old WR address.