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

Do not assume python is an interpreter for Python 2 #353

Merged
merged 1 commit into from Apr 8, 2013

Conversation

@Ereski
Copy link

Ereski commented Apr 8, 2013

On some distributions and configurations, the python command might refer to
python3 instead of python2, breaking the build. Fix this by using the first of
python2, python2.7, or python.

@Ereski
Copy link
Author

Ereski commented Apr 8, 2013

An updated pull request from #338.

@jdm
Copy link
Member

jdm commented Apr 8, 2013

The minimum version of python required for the bindings code generator is 2.7, so let's not check for older versions than that.

@jdm jdm closed this Apr 8, 2013
@jdm jdm reopened this Apr 8, 2013
On some distributions and configurations, the python command might refer to
python3 instead of python2, breaking the build. Fix this by using the first of
python2, python2.7, or python.
@Ereski
Copy link
Author

Ereski commented Apr 8, 2013

@jdm: Removed check for python2.{6,5}.

@Ereski Ereski closed this Apr 8, 2013
@Ereski Ereski reopened this Apr 8, 2013
@Ereski
Copy link
Author

Ereski commented Apr 8, 2013

This GitHub interface is a bit confusing :(.

jdm added a commit that referenced this pull request Apr 8, 2013
Do not assume python is an interpreter for Python 2
@jdm jdm merged commit e08b605 into servo:master Apr 8, 2013
@jdm
Copy link
Member

jdm commented Apr 8, 2013

Thanks!

@Ereski Ereski deleted the Ereski:find-python2 branch Apr 8, 2013
ChrisParis pushed a commit to ChrisParis/servo that referenced this pull request Sep 7, 2014
Fix query string bug that invalidates test
glennw pushed a commit to glennw/servo that referenced this pull request Jan 16, 2017
Add Api to access glyph dimensions

With this, standalone applications will be able to handle glyph spacing and/or positioning. Currently the workaround would be setting up a font renderer by yourself, but this would involve use of plattform dependent libraries and introduce overhead, since the texture cache already knows about the glyph dimensions.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/353)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.