is there any reason why we have to resort to such ...
# python
r
is there any reason why we have to resort to such long names in Python (and in other languages too, apparently), as opposed to TypeScript? see https://www.pulumi.com/registry/packages/aws/api-docs/networkfirewall/rulegroup/#aws-networkfirewall-rulegroup for example: By the time you get down to the
rules_source_list
argument, you have to assign it to a `
Copy code
aws.networkfirewall.RuleGroupRuleGroupRulesSourceRulesSourceListArgs(...
function call
g
Yes, all SDKs are generated from the original Go Code, where this is facilitated by interfaces which were not properly translated into python namespaces/packages. It is one of the reasons I'm migrating from python to TypeScript because in TS I do not have to deal with long names so often.
r
are you saying that the translation is somehow done properly in TS, and that the TS side of things gets more love vs Python?
b
Yes, all SDKs are generated from the original Go Code, where this is facilitated by interfaces which were not properly translated into python namespaces/packages
this isn’t correct. The general reason the Python type system is as it is is because of the way the Python type system works. There is an upcoming project to convert python’s typings to `TypedDict`: https://github.com/pulumi/pulumi/issues/11732 Typescript doesn’t get more love than the other languages, it’s just the case that TS is good at expressing the complex types needed
ultimately, Python’s type system is bolted on to the language
I’m sure there are ways that we could have improved the python SDK before typed dict, but typed dict is going to dramatically improve things
r
thank you, @billowy-army-68599!