Request

Issue #600

draft pr open

Verification

Verified — checks passed

We installed dependencies and ran lint and test in a sandbox — all passed.

Likely addresses the issue (95% confidence)

An AI estimate of whether the change actually fixes the issue — the checks themselves only confirm nothing broke. It's a hint for review, not a pass/fail check.

Why?

The diff modifies `src/dotenv/parser.py` so the `_equal_sign` regex no longer consumes whitespace after `=`, leaving spaces/tabs before a `#` inside the `_unquoted_value` capture where the existing `re.sub(r'\s+#.*', ...)` can strip them; it also changes `rstrip()` to `strip()` to discard that leading whitespace, and adds tests verifying that `a= #c` and `a= \t #c` parse to an empty value.

lintpassed · 17ms
```
All checks passed!
```

testpassed · 2.4s

........................................................................ [ 32%]
........................................................................ [ 64%]
........................................................................ [ 96%]
.........                                                                [100%]
225 passed in 1.85s

typecheck and build are not defined separately in this repo.

Ran 6/9/2026, 3:57:05 AM · python:pip

Get the code

Pull this branch

With gh CLI

gh pr checkout 3 --repo kamransiddiqui/python-dotenv

Raw git

git fetch https://github.com/kamransiddiqui/python-dotenv.git gitgot/issue-600-431b5049
git checkout -b gitgot/issue-600-431b5049 FETCH_HEAD

Fork-mode request: the branch lives on kamransiddiqui/python-dotenv (your fork), not theskumar/python-dotenv, so the commands above target the fork.

Drive locally

Paste this into your local coding agent (Claude Code, Cursor, etc.) to continue iterating with full repo context.

Context prompt

You are continuing work on a draft PR for theskumar/python-dotenv, addressing issue #600.

First, check out the branch with gitgot's first-pass change (run from a clone of the repo):
  gh pr checkout 3 --repo kamransiddiqui/python-dotenv

Then review the diff and:
- run the project's lint/typecheck/test commands and fix anything broken
- if the diff is wrong-headed, revert it and start fresh from the issue
- keep the change tight; do not refactor unrelated code

PR thread

No comments on the PR yet. Use the form below to start the thread.