Skip to content

pip bundle broken in 1.4 #1114

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.

Sign up for GitHub

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

Jump to bottom
Closed
qwcode opened this issue Aug 6, 2013 · 2 comments
Closed

pip bundle broken in 1.4 #1114

qwcode opened this issue Aug 6, 2013 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation
Milestone
1.4.1

Comments

@qwcode
Copy link
Contributor

qwcode commented Aug 6, 2013

from #1046...
"FYI, bundles are not just deprecated but also broken in 1.4. The build directories in the bundle cause the new 'existing build directory check' to cause bundle installation to fail. Because of this, I've reverted back to 1.3.1."
@qwcode
Copy link
Contributor Author

qwcode commented Aug 6, 2013

maybe related to #1078 (fixed in #1080)

@qwcode qwcode mentioned this issue Aug 7, 2013
Merged
@qwcode
Copy link
Contributor Author

qwcode commented Aug 7, 2013

closing. merged #1116

@qwcode qwcode closed this as completed Aug 7, 2013
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Milestone
1.4.1
Development

No branches or pull requests
1 participant
@qwcode