Yes, the implementation is plain wrong. Currently in fmtcore.jl

Format.jl/src/fmtcore.jl

Lines 337 to 341 in 37c24b9

    
           if 1.0e-4 <= ax < 1.0e6 
        
               _pfmt_f(out, fs, x) 
        
           else 
        
               _pfmt_e(out, fs, x) 
        
           end

fs is passed without regard on how to handle significant digits. The correct behavior is documented in Python's Format String documentation this repo referenced to.
I will see if I can do anything, currently this gives the correct behavior but I am not sure this is how they do it.

function _pfmt_g(out::IO, fs::FormatSpec, x::AbstractFloat)
    # number decomposition
    ax = abs(x)
    if 1.0e-4 <= ax < 1.0e6
        newprec = fs.prec - floor(Int, log10(x)) - 1
        _pfmt_f(out, FormatSpec(fs ;prec=newprec), x)
    else
        newprec = fs.prec - 1
        _pfmt_e(out, FormatSpec(fs ;prec=newprec), x)
    end
end

g format differs from Python #88

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`g` format differs from Python #88