Skip to content

fix: declare lxml as a runtime dependency (v1.6.1)#84

Open
AleksandrSl wants to merge 2 commits into
contentstack:developmentfrom
AleksandrSl:fix/declare-lxml-dependency
Open

fix: declare lxml as a runtime dependency (v1.6.1)#84
AleksandrSl wants to merge 2 commits into
contentstack:developmentfrom
AleksandrSl:fix/declare-lxml-dependency

Conversation

@AleksandrSl

Copy link
Copy Markdown

contentstack_utils.utils imports lxml.etree at module load time, but install_requires has been empty since initial release. Declare lxml with environment markers: >=6.1.0 on Python 3.8+ (aligned with requirements.txt),

=4.9.0,<5 on 3.6–3.7.

Aravind-Kumar-cstk and others added 2 commits June 30, 2026 20:31
contentstack_utils.utils imports lxml.etree at module load time, but
install_requires has been empty since initial release. Declare lxml with
environment markers: >=6.1.0 on Python 3.8+ (aligned with requirements.txt),
>=4.9.0,<5 on 3.6–3.7.

Co-authored-by: Cursor <cursoragent@cursor.com>
@AleksandrSl
AleksandrSl requested review from a team as code owners July 9, 2026 19:45
Comment thread setup.py
install_requires=[

# lxml 6.x requires Python 3.8+; keep 4.x for 3.6–3.7 (python_requires>=3.6).
"lxml>=4.9.0,<5; python_version<'3.8'",

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may make sense to drop support for python <3.9 already since even 3.10 is eol this October https://devguide.python.org/versions/
But that would be a major release

@AleksandrSl AleksandrSl Jul 9, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The development branch is not up to the latest main, so this change is propagated, but is not mine

__author__ = 'contentstack'
__status__ = 'debug'
__version__ = '1.6.0'
__version__ = '1.6.1'

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I just though that patch version bump is not ideal, and major release is better, because thought people had to install lxml already they could install any version of it, since the library didn't restrict it. Now it's restricted, so people may get conflicts? Shouldn't be that bad, but I leave the decision on you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants