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 grow to v1.0.0 #5292

Merged
merged 32 commits into from
Feb 9, 2021
Merged

🎉 Update grow to v1.0.0 #5292

merged 32 commits into from
Feb 9, 2021

Conversation

lluerich
Copy link
Collaborator

@lluerich lluerich commented Feb 2, 2021

This is a work in progress as I am still dealing with a couple of errors during the build.

Once merged it will fix #5110.

Comment on lines 35 to 38

messages = manager.ServerMessages()
messages.add_message('Pod:', pod.root, colors.HIGHLIGHT)
messages.add_message('Server:', url_root, colors.HIGHLIGHT)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Since the idea of this extension is to silence the startup log and we are not printing them anyway, this can be removed.

Comment on lines 44 to 45
messages.add_message(
'Ready.', 'Press ctrl-c to quit.', colors.SUCCESS, colors.SUCCESS)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here.

@@ -52,7 +52,7 @@ class MarkdownInHtmlExtension(extensions.BaseExtension):
def __init__(self, pod, config):
super(MarkdownInHtmlExtension, self).__init__(pod, config)

if config.has_key(CLEAR_EXTRA_EXTENSIONS_FLAG) and config.get(CLEAR_EXTRA_EXTENSIONS_FLAG):
if config.__contains__(CLEAR_EXTRA_EXTENSIONS_FLAG) and config.get(CLEAR_EXTRA_EXTENSIONS_FLAG):
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hm... if config.get(CLEAR_EXTRA_EXTENSIONS_FLAG, None) should actually be enough. Methods pre- and postfixed with __ are not meant to be called directly.

@matthiasrohmer
Copy link
Collaborator

Nice, thanks so far, Leo! How many rendering issues are there? And can you briefly summarize in which categories they fall?

@sebastianbenz
Copy link
Collaborator

Extremely excited about this. Please hurry, so that I might not have to setup python 2.7 on my new notebook ;-)!

@matthiasrohmer
Copy link
Collaborator

Things work in general. Build times did increase by ~30%, this needs to be investigated. Besides that there are strange things with the code formatting that @lluerich looks into.

@lluerich
Copy link
Collaborator Author

lluerich commented Feb 8, 2021

Additionally, if using Pygments >= 2.4, the output will be wrapped in <code> tags, whereas earlier versions will not.

Source

@lluerich lluerich marked this pull request as ready for review February 8, 2021 16:55
@Nmeer112 Nmeer112 mentioned this pull request Feb 8, 2021
4 tasks
@matthiasrohmer matthiasrohmer changed the title 🚧 Update grow to v1.0.0 🎉 Update grow to v1.0.0 Feb 9, 2021
@matthiasrohmer
Copy link
Collaborator

Note: that's a breaking change for previous contributors to amp.dev. To get amp.dev running again on your local machine, coming from Python 2.7 perform the following steps.

pip uninstall grow
# This will install Python 3. Skip if already present
brew install python

# Install Grow 1 using a Python 3 environment
pip3 install grow

@patrickkettner
Copy link
Collaborator

patrickkettner commented Feb 9, 2021 via email

@matthiasrohmer
Copy link
Collaborator

Hm... you are correct. Update most parts of it but we still use echo "export PATH=\"$(python -m site --user-base)/bin\":\$PATH" >> ~/.bash_profile in the README. This should probably be python3 there.

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.

Upgrade to Grow 1
4 participants