home.social

#fastkml — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fastkml, aggregated by home.social.

fetched live
  1. @kushal
    I had to shave some yaks first, but I finally came around to test the #pyuppsla 0.8.0 #xml library with #fastkml 🎉

    Claude's diagnosis:

    Bottom line up front: for the actual bulk of the work — building, parsing,
    serializing, round-tripping, and XPath-querying XML trees — pyuppsala.etree
    is a very high-fidelity, largely drop-in replacement for lxml.etree. Of
    ~1200 tests (stdlib + lxml + pyuppsala combined); only a handful needed
    pyuppsala-specific behavior, and the fastkml-side changes needed were small and surgical (four files, no redesign). The rough edges are concentrated in three
    places: recover-mode parsing, XSD numeric validation, and namespace-prefix resolution timing

    github.com/cleder/fastkml/pull

  2. @kushal
    I had to shave some yaks first, but I finally came around to test the #pyuppsla 0.8.0 #xml library with #fastkml 🎉

    Claude's diagnosis:

    Bottom line up front: for the actual bulk of the work — building, parsing,
    serializing, round-tripping, and XPath-querying XML trees — pyuppsala.etree
    is a very high-fidelity, largely drop-in replacement for lxml.etree. Of
    ~1200 tests (stdlib + lxml + pyuppsala combined); only a handful needed
    pyuppsala-specific behavior, and the fastkml-side changes needed were small and surgical (four files, no redesign). The rough edges are concentrated in three
    places: recover-mode parsing, XSD numeric validation, and namespace-prefix resolution timing

    github.com/cleder/fastkml/pull

  3. @kushal
    I had to shave some yaks first, but I finally came around to test the 0.8.0 library with 🎉

    Claude's diagnosis:

    Bottom line up front: for the actual bulk of the work — building, parsing,
    serializing, round-tripping, and XPath-querying XML trees — pyuppsala.etree
    is a very high-fidelity, largely drop-in replacement for lxml.etree. Of
    ~1200 tests (stdlib + lxml + pyuppsala combined); only a handful needed
    pyuppsala-specific behavior, and the fastkml-side changes needed were small and surgical (four files, no redesign). The rough edges are concentrated in three
    places: recover-mode parsing, XSD numeric validation, and namespace-prefix resolution timing

    github.com/cleder/fastkml/pull

  4. @kushal
    I had to shave some yaks first, but I finally came around to test the #pyuppsla 0.8.0 #xml library with #fastkml 🎉

    Claude's diagnosis:

    Bottom line up front: for the actual bulk of the work — building, parsing,
    serializing, round-tripping, and XPath-querying XML trees — pyuppsala.etree
    is a very high-fidelity, largely drop-in replacement for lxml.etree. Of
    ~1200 tests (stdlib + lxml + pyuppsala combined); only a handful needed
    pyuppsala-specific behavior, and the fastkml-side changes needed were small and surgical (four files, no redesign). The rough edges are concentrated in three
    places: recover-mode parsing, XSD numeric validation, and namespace-prefix resolution timing

    github.com/cleder/fastkml/pull

  5. @kushal
    I had to shave some yaks first, but I finally came around to test the #pyuppsla 0.8.0 #xml library with #fastkml 🎉

    Claude's diagnosis:

    Bottom line up front: for the actual bulk of the work — building, parsing,
    serializing, round-tripping, and XPath-querying XML trees — pyuppsala.etree
    is a very high-fidelity, largely drop-in replacement for lxml.etree. Of
    ~1200 tests (stdlib + lxml + pyuppsala combined); only a handful needed
    pyuppsala-specific behavior, and the fastkml-side changes needed were small and surgical (four files, no redesign). The rough edges are concentrated in three
    places: recover-mode parsing, XSD numeric validation, and namespace-prefix resolution timing

    github.com/cleder/fastkml/pull

  6. #fastkml can now parse and create #kml files with the new #python #pyuppsala #xml etree implementation. Still experimental, but all tests are passing.

    github.com/cleder/fastkml/

  7. #fastkml can now parse and create #kml files with the new #python #pyuppsala #xml etree implementation. Still experimental, but all tests are passing.

    github.com/cleder/fastkml/

  8. can now parse and create files with the new etree implementation. Still experimental, but all tests are passing.

    github.com/cleder/fastkml/

  9. #fastkml can now parse and create #kml files with the new #python #pyuppsala #xml etree implementation. Still experimental, but all tests are passing.

    github.com/cleder/fastkml/