Use getfullargspec when fetching lightgbm args

[dbczumar]

Signed-off-by: dbczumar corey.zumar@databricks.com

What changes are proposed in this pull request?

The latest dev version of lightgbm adds type hints to APIs, which breaks the use of inspect.getargspec. Accordingly, this PR updates lightgbm autologging to use inspect.getfullargspec instead.

How is this patch tested?

Unit / integration tests for lightgbm autologging

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

Interface

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

Language

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

Integrations

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

[harupy]

@dbczumar Can we replace inspect.getargspec in xgboost.py?

mlflow/mlflow/xgboost.py

Line 565 in 8a7659e

all_arg_names = inspect.getargspec(original)[0] # pylint: disable=W1505

[harupy]

@dbczumar Thanks for the fix! LGTM once #4748 (comment) is addressed and all the CI checks pass.

[dbczumar]

@dbczumar Thanks for the fix! LGTM once #4748 (comment) is addressed and all the CI checks pass.

Done! Thanks!