GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — v3.1.0 Strict mode. Robuster support for unicode inc bug fixes. by JamesParrott · Pull Request #422 · GeospatialPython/pyshp

Conversation

@JamesParrott

@JamesParrott JamesParrott commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

Make dbf string encoding robust (names and records)

Replace strip_leading_whitespace and replace_ascii_spaces_with_underscores with strict

Respect unicode code point boundaries when truncating field names

Pass mypy - make repr of bytes explicit in f string

Handle .dbf C & M fields with _encode_dbf_string & _decode_C_or_M_field

Make dbf string encoding robust (names and records)

Make en/decoding of dbf field name and "C" field values robuster.

Make dbf record writing atomic

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@JamesParrott
v3.1.0 Strict mode. Robuster support for unicode inc bug fixes.
e039403 
Make dbf string encoding robust (names and records)

Replace strip_leading_whitespace and replace_ascii_spaces_with_underscores with strict

Respect unicode code point boundaries when truncating field names

Pass mypy - make repr of bytes explicit in f string

Handle .dbf C & M fields with _encode_dbf_string & _decode_C_or_M_field

Make dbf string encoding robust (names and records)

Make en/decoding of dbf field name and "C" field values robuster.

Make dbf record writing atomic
@JamesParrott
JamesParrott merged commit 493534a into GeospatialPython:master Jun 23, 2026
30 checks passed

Uh oh!

There was an error while loading. Please reload this page.
@JamesParrott
JamesParrott deleted the Trim_strings_wrt_code_points_not_bytes branch June 23, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@JamesParrott
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.