Jesse Beder | 6 Sep 08:08 2011
Picon

minor errors in examples in the 1.2 spec

I believe there are errors in examples 8.5 and 8.21 in the 1.2 spec.
(In both cases, pyyaml (compiled using libyaml) agrees with me.)

In example 8.5, the value associated with the key "keep" should be "#
text\n\n" (the example only indicates that one newline should be
kept).

In example 8.21, the value associated with the key "literal" should be
"value\n" (the example does not keep the newline).

Thanks!

- Jesse

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
Andrey Somov | 7 Sep 16:37 2011
Picon

Re: minor errors in examples in the 1.2 spec

As far as I know PyYAML does not support 1.2 yet...

-
Andrey

On Tue, Sep 6, 2011 at 8:08 AM, Jesse Beder <beder@...> wrote:
> I believe there are errors in examples 8.5 and 8.21 in the 1.2 spec.
> (In both cases, pyyaml (compiled using libyaml) agrees with me.)
>

------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
Jesse Beder | 7 Sep 19:18 2011
Picon

Re: minor errors in examples in the 1.2 spec

You're right :)

Although I think both examples are still incorrect, although I'm not
sure about the first.

For example 8.5, under the "keep" indicator, the spec reads, "In this
case, the final line break and any trailing empty lines are considered
to be part of the scalar’s content." However, I'm not sure I
understand the part about trailing comments. If the example is
correct, then

keep: |+
  # text↓
↓

will produce {keep: "#text\n\n"}, but

keep: |+
  # text↓
↓
# Trail

will produce {keep: "#text\n"}, which seems strange (why should adding
a comment at the end remove a newline from the content?).

Example 8.21 looks like:

literal: |2
  value
folded: etc
(Continue reading)

Ratnadeep Debnath | 13 Sep 08:22 2011
Picon

Support for YAML 1.2 in PyYaml?

Hi,

Currently PyYaml supports YAML version 1.1. I would like to know when
will PyYaml add support for YAML version 1.2.

Thanks,
Regards,
rtnpro

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
Dennis Lissov | 18 Sep 21:38 2011
Picon

PyYAML bug tracker not functional

Hello everyone,

It's impossible right now to add a bug in PyYAML bug tracker at
http://pyyaml.org due to the following error:

Trac detected an internal error:
DatabaseError: database disk image is malformed

As I understand the PyYAML author has not been seen here for two
months... can I expect it to be restored soon?

Thanks,
Dennis.

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
Kirill Simonov | 18 Sep 23:26 2011
Picon

Re: PyYAML bug tracker not functional

On 09/18/2011 03:38 PM, Dennis Lissov wrote:
> Hello everyone,
>
> It's impossible right now to add a bug in PyYAML bug tracker at
> http://pyyaml.org due to the following error:
>
> Trac detected an internal error:
> DatabaseError: database disk image is malformed
>
> As I understand the PyYAML author has not been seen here for two
> months... can I expect it to be restored soon?

I guess that explains a surprising lack of ticket spam last month.

I fixed the problem, thank you for the report!

Thanks,
Kirill

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2

Gmane