Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
A
atd
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Georges Racinet
  • atd
  • Issues
  • #5

Closed
Open
Opened May 15, 2014 by Georges Racinet@gracinet🦑Maintainer

Sensitivity to ordering of imports

Created originally on Bitbucket by Anonymous

Currently, anybox.testing.datetime must be imported first, in order to replace the standard library's datetime module with its modified version, befiore other modules have imported it.

This is in practice hard to enforce in large framework contexts : the testrunner will be imported first no matter what, and in cases such as OpenERP, we have the policy to load the whole database before importing the tests with a runner such as nose (to avoid breaking havoc in the framework's dynamic module injection).

anybox.testing.datetime should provide a way to become insensitive to these orderings problems.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gracinet/atd#5