Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the "Application dependency management" recommendations #1055

Conversation

pradyunsg
Copy link
Member

This is a more detailed recommendation that breaks up the recommendation
into multiple parts, to reflect that multiple tools need to be used in
workflows today to maximise compatibility with existing platforms.

It also recommends that deployed applications be isolated from the
system packages, as was implied but not explicitly noted.

The move away from Pipenv as the primary recommendation is a reflection
of the change that application development workflows have a greater
diversity in mature tooling available for them.

Toward #912

@pradyunsg pradyunsg force-pushed the rework-application-dependency-management-recommendations branch from 234e093 to d83a050 Compare March 4, 2022 08:42
@bhrutledge bhrutledge self-requested a review March 9, 2022 01:14
Copy link
Contributor

@bhrutledge bhrutledge left a comment

Choose a reason for hiding this comment

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

Thanks for this. I took the liberty of pushing some copy edits, and I have one content question.

source/guides/tool-recommendations.rst Show resolved Hide resolved
@pradyunsg pradyunsg force-pushed the rework-application-dependency-management-recommendations branch 2 times, most recently from 87bd7e2 to 79238e3 Compare March 11, 2022 06:24
pradyunsg and others added 2 commits March 11, 2022 06:33
This is a more detailed recommendation that breaks up the recommendation
into multiple parts, to reflect that multiple tools need to be used in
workflows today to maximise compatibility with existing platforms.

It also recommends that deployed applications be isolated from the
system packages, as was implied but not explicitly noted.

The move away from Pipenv as the primary recommendation is a reflection
of the change that application development workflows have a greater
diversity in mature tooling available for them.

Co-authored-by: Brian Rutledge <bhrutledge@gmail.com>
@pradyunsg pradyunsg force-pushed the rework-application-dependency-management-recommendations branch from 79238e3 to 8c8550d Compare March 11, 2022 06:33
@pradyunsg
Copy link
Member Author

pradyunsg commented Mar 11, 2022

@bhrutledge I've rebased this on main and squashed your copy edits to the new content (dropping the reordering + rewording of the developing bullet). You can click on "force-pushed" text in the GitHub event above, to review what exactly has changed across the force-push.

@bhrutledge bhrutledge merged commit f3e1dd5 into pypa:main Mar 11, 2022
@pradyunsg pradyunsg deleted the rework-application-dependency-management-recommendations branch March 11, 2022 11:19
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.

None yet

3 participants