Wagtail 2.1 released

275 views
Skip to first unread message

Matthew Westcott

unread,
May 23, 2018, 7:39:35 AM5/23/18
to wag...@googlegroups.com
Hi all,
I'm pleased to announce that Wagtail 2.1 is now released!
http://docs.wagtail.io/en/v2.1/releases/2.1.html

For upgrade instructions, see: http://docs.wagtail.io/en/v2.1/releases/upgrading.html

Cheers,
- Matt

Message has been deleted

zar...@columbia.edu

unread,
May 24, 2018, 12:33:09 PM5/24/18
to Wagtail support

Question, the module that this upgrade depends on, is it l18n or i18n?
l18n produces README.rst error for me. And it's breaking on Python 3.4.
Python 3.6.4 produced no error.

Thanks,
-Zarina

Matthew Westcott

unread,
May 24, 2018, 2:51:33 PM5/24/18
to wag...@googlegroups.com
Hi Zarina,

The module is 'l18n': https://pypi.org/project/l18n/
What's the exact error you're receiving (including stack trace, if available)? We've tested against Python 3.4 throughout development with no issues, so I think this must be something specific to your setup.

Cheers,
- Matt

zar...@columbia.edu

unread,
May 24, 2018, 3:13:18 PM5/24/18
to Wagtail support

Here's the error:

Collecting l18n==2016.6.4 (from -r requirements.txt (line 110))
  Using cached https://files.pythonhosted.org/packages/1d/a9/c514038919f430a9b748e31be06e3b365b1e4a4c1aa04b3990a9870df38d/l18n-2016.6.4.zip
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-zkwkdpjl/l18n/setup.py", line 99, in <module>
        long_description=open(os.path.join('README.rst')).read(),
      File "/mnt/jenkins/jobs/portfolio/workspace/ve/lib/python3.4/encodings/ascii.py", line 26, in decode
        return codecs.ascii_decode(input, self.errors)[0]
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2135: ordinal not in range(128)
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-zkwkdpjl/l18n/
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
make: *** [ve/sentinal] Error 1
Build step 'Execute shell' marked build as failure
[Cobertura] Publishing Cobertura coverage report...

[Cobertura] Publishing Cobertura coverage results...

[Cobertura] Cobertura coverage report found.

Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found but none of them are new. Did leafNodes run? 


-Zarina

David Moore

unread,
May 24, 2018, 8:41:04 PM5/24/18
to wag...@googlegroups.com
Hi Zarina,

It is my timezone setting code that introduced the dependency upon l18n :-(

This looks like a bug in the l18n setup.py code that is triggered when the operating system locale does not use UTF-8.

Can you run the snippet of code below on the same system?  It should trigger the same exception?

If you can change the system locale (e.g. export LC_ALL=en_US.UTF-8) then that should work-around the problem for you.

I can raise an issue with the l18n maintainer, but I guess something else needs to be done in the meantime.  I'll leave that to the Wagtail team.

Best wishes,
David.

"""
>>> str(l18n.tz_fullnames['Pacific/Easter'])
'Pacific/Easter Island'  # or 'Pacifique/Île de Pâques' in French
"""

import locale
print( locale.getpreferredencoding() )

description=open(__file__).read()
print( description )

--
You received this message because you are subscribed to the Google Groups "Wagtail support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wagtail+unsubscribe@googlegroups.com.
To post to this group, send email to wag...@googlegroups.com.
Visit this group at https://groups.google.com/group/wagtail.
To view this discussion on the web, visit https://groups.google.com/d/msgid/wagtail/91c35714-049b-483d-bec7-f10b626a7938%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

zar...@columbia.edu

unread,
May 25, 2018, 11:04:09 AM5/25/18
to Wagtail support

Hi David,

Thank you. One of the developers in my team took a look and said that the system locale is already using UTF-8.
It seems to him it looked like l18n had an issue when it read in its own readme file in setup.py, quite possibly the
issue lies in l18n. l18n's last release was September 2016. In the meantime, I'm going to continue using Wagtail 2.0.1.

Curious though, why are you using l18n for timezone setting when Django has its libraries for such use?

Thanks,
-Zarina
To unsubscribe from this group and stop receiving emails from it, send an email to wagtail+u...@googlegroups.com.

David Moore

unread,
May 25, 2018, 3:10:55 PM5/25/18
to wag...@googlegroups.com
Hi Zarina,

l18n is used to localize the time zone names for languages other than English.  The alternatives I saw were to ask the Wagtail translators to translate all 433 time zones from pytz.common_timezones, or just leave them in English regardless of what language was being used.


Best wishes, David.

Markus Sitzmann

unread,
Aug 5, 2018, 6:14:00 PM8/5/18
to Wagtail support
Hi,

A current "pip install" of 2.1 still fails with the error message reported here (UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2135: ordinal not in range(128)). I am on python 3.6.5 - is it already supposed to be fixed?

Thanks & best,
Markus

Matthew Westcott

unread,
Aug 5, 2018, 6:35:56 PM8/5/18
to wag...@googlegroups.com
Hi Markus,

No, we're still waiting for a fixed version of the l10n package to be released. Given that there hasn't been any update on that project for nearly a month now, I'll look into the possibility of making a bugfix release of Wagtail with that library bundled in, so that the installation issue doesn't arise.

Cheers,
- Matt
> --
> You received this message because you are subscribed to the Google Groups "Wagtail support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wagtail+u...@googlegroups.com.
> To post to this group, send email to wag...@googlegroups.com.
> Visit this group at https://groups.google.com/group/wagtail.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/wagtail/a3cdf68d-8b55-440c-a3ba-c393cdec7593%40googlegroups.com.

Markus Sitzmann

unread,
Aug 5, 2018, 6:55:34 PM8/5/18
to Wagtail support
Hi Matt,

thanks a lot for your quick answer - I am also still happy with v.2.0 of Wagtail which is a great project (I only wanted to get rid of this "pesky" update to 2.1.1 message you get on the admin panel :-))

Best,
Markus

Markus Sitzmann

unread,
Aug 6, 2018, 6:00:36 PM8/6/18
to wag...@googlegroups.com
Thanks for the very fast fix! 2.1.2 works.

Reply all
Reply to author
Forward
0 new messages