Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Dependency Version Management in Python
00:00
5 left

Dependency Version Management in Python

HardPython

Problem

An OpenAI Responses API tool bundle may depend on several versioned Python packages. Given available package versions and minimum-version dependency requirements, select one compatible version for every required package. Prefer the highest available version for each package. Return an empty dictionary if no valid selection exists.

Formal Specification

Implement resolve_dependencies(catalog, requirements). catalog is a dictionary mapping package names to dictionaries of version strings and their dependencies. Each dependency is represented as dependency_name: minimum_version, and all version requirements are inclusive. requirements maps root package names to their minimum acceptable versions. Return a dictionary mapping every resolved package to its selected version, or {} when resolution is impossible.

Versions use major.minor.patch format and should be compared numerically, not lexicographically. The dependency graph is acyclic. A package selected while resolving one dependency may be reused if it satisfies a later minimum-version requirement.

Constraints

  • 1 <= len(catalog) <= 100
  • Each package has at most 20 available versions
  • Versions use major.minor.patch format
  • The dependency graph is acyclic
  • Every dependency name appears in catalog
  • Return the highest compatible version whenever multiple solutions exist

Function Signature

def resolve_dependencies(catalog, requirements):
Interviewer

Your question is Dependency Version Management in Python. Start with the requirements in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePython 3
Sign up free to run your codeLog inLn 2
Run your code to see test output here.