running typer cli command from python code

[blnprasad]

How can i trigger/run typer cli specific command from python code. I guess i need to emulate command line arguments some where but not sure. Can you please help on this?

Cli:
python main.py goodbye --formal Camila

From Code:
i want to run specific command based on my need. how do i pass command line arguments, some thing like:
typer_app( "goodbye --formal Camila" )

[tiangolo]

A function in a Typer app is not modified by Typer, it's still a normal function. So, you should be able to call it directly as you normally would, just make sure you pass all the parameters to it.

[github-actions]

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

[justinpinkney]

What about in the case I'm using the typer.Option("default") syntax, now my function doesn't receive "default" as the default value, but instead a typer.models.OptionInfo object

Is there a way to deal with this?

[mirestrepo]

@justinpinkney Did you ever figure out a way to get the defaults correctly? Thanks in advance! My use case is to call the functions directly from the tests, but for every option that has a default I get something like <typer.models.OptionInfo object at 0x119787650> instead of the default value. I suppose if I don't use the typer.Option as a default it should work, but then I can take advantage of the --help etc

[justinpinkney]

@justinpinkney Did you ever figure out a way to get the defaults correctly? Thanks in advance! My use case is to call the suctions directly from the tests, by for every option that has a default I get something like <typer.models.OptionInfo object at 0x119787650> instead of the default value. I suppose if I don't use the typer.Option as a default it should work, but then I can take advantage of the --help etc

My problem exactly, didn't find a good way around this.

[ojomio]

Can this issue be re-opened? It seems to be a relevant one.

Right now if we want to call a function from code we have to write duplicate functions just for the Typer CLI with Typer defaults and counterparts with regular python defaults - very ugly (

[rec]

I am experiencing exactly the same issue.

The problem is hidden in this statement above: "A function in a Typer app is not modified by Typer, it's still a normal function. So, you should be able to call it directly as you normally would, just make sure you pass all the parameters to it."

(Italics mine.)

I want to call a Typer function which takes seven parameters, only one of which I want to modify.

So I need to pass in seven default arguments to get the one real argument in, and if I ever change any default, I now have to change it not just in the code but at every call site.

I can see how this would be fixed in Typer. It wouldn't be trivial, you'd have to use inspection on the function, and then decorate it based on that.

[ojomio]

Yes, so we literally write two functions - one with typer.Option and friends, which calls the second one, which only contains plain default values.

This way we get --help , type casting, enum checking at runtime and all what typer offers and still have a way to call the original function

The only problem is - you know - there are two functions

How a workaround for the problem we all have may look like- Typer.add_command automatically generates a plain version of decorated function and make it available through -say- .original attribute

[rec]

Exactly!! I could do this without too much effort, but it would require the Typer author(s) to want it :-), and to give it a pretty thorough review, as it would be a fairly big change. Another way, less violent, would be instead to park the wrapped, directly callable function on a .call property on the original function, so current behavior would not be changed.

…

On Sat, Sep 4, 2021 at 9:09 AM Yury Paykov ***@***.***> wrote: Yes, so we literally write *two* functions - one with typer.Option and friends, which calls *the second one*, which only contain plain default values. This way we get --help , type casting, enum checking at runtime and all what typer offers and still have a way to call the original function The only problem is - you know - there are two functions How a workaround for the problem we all have may look like- Typer.add_command automatically generates a plain version of decorated function and make it available through -say- .original attribute — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB53MRWWHG7JFCJJ55MQKLUAHA2PANCNFSM4NIJ6DYA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- /t PGP Key: ***@***.*** *https://tom.ritchford.com <https://tom.ritchford.com>* *https://tom.swirly.com <https://tom.swirly.com>*

[sherifattia]

The suggested workarounds make the code very ugly. It would be awesome if Typer can fix this

[nacitar]

Indeed, this shouldn't be closed. It's the biggest blemish this otherwise somewhat elegant library has.