Skip to content

Milestones

List view

  • v1.8.0

    This milestone was issued to gather issues related to the code base modernization, styling, and rules. In this milestone is planned a major source code reformatting, which would make hard to compare with previous versions of the source code, although not impossible. Because of this, it's very important that we do it only once. After this, we will start the code migration toward the [v2.0](https://github.com/petl-developers/petl/milestone/29) that will: 1. Introduce API/language changes like typing 2. Drop some backward compatibility, like Python 2.7 support 3. Fix some ambiguities of the current library/code This would give us the opportunity to easily compare differences between 1.* and 2.* and in case of any bugs the necessary changes would be much easier to apply to both versions.

    No due date
    •0/1 issues closed
    0% complete1 open0 closed

  • v2.0

    This milestone is inteded to make a whole code base mordernization aimed to add safety throught adding **typing** information to all internal and user facing methods and classes. The typing would allow all modern tools to type check the source code for our users, and also the `petl` internal source code. This will avoid a whole class of mistakes and provide more information for AI assistants and other tools that assist development. It's important to notice that this milestone will: 1. Introduce user-facing API/language changes like typing 2. Drop some backward compatibility, like Python 2.7 support 3. Fix some ambiguities of the current library/code Because of this, users should be warned to upgrade their source code and retest against this new [v2.0](https://github.com/petl-developers/petl/milestone/29). This migration also shold not prevent us to maintain a v1.8x branch containing bug fixes and support to newer python versions. Before starting this milestone, it is planned a major source code reformatting described in the [v1.8](https://github.com/petl-developers/petl/milestone/34) milestone. It is required because it makes easier to apply bug fixes to boh versions.

    No due date
    •8/18 issues closed
    44% complete10 open8 closed