ruby.git/test/csv/test_encodings.rb, branch v3_3_11

[ruby/csv] Add CSV::InvalidEncodingError

2023-10-03T07:13:18+00:00

(https://github.com/ruby/csv/pull/287)

To handle encoding errors in CSV parsing with the appropriate error
class

https://github.com/ruby/csv/commit/68b44887e5

[ruby/csv] test: rename Helper to CSVHelper

2023-05-24T16:44:17+00:00

(https://github.com/ruby/csv/pull/278)

Rename it so that in ruby/ruby, the generic name Helper is not used.

Merge csv-3.2.6

2022-12-09T07:36:22+00:00

[ruby/csv] CSV.generate_line: use the encoding of the first non ASCII field as the expected encoding

2020-07-19T17:32:55+00:00

See also: https://github.com/ruby/stringio/issues/13#issuecomment-660543554

https://github.com/ruby/csv/commit/004cf49d18

[ruby/csv] Revert "test: use binary mode explicitly for Ruby 2.7"

2020-07-19T17:32:50+00:00

This reverts commit 736174d28413a4c36630b0daf2f170c8d2fc9abe.

It doesn't solve anything.

https://github.com/ruby/csv/commit/0ee3bdd0d3

[ruby/csv] test: use binary mode explicitly for Ruby 2.7

2020-07-19T17:32:50+00:00

https://github.com/ruby/csv/commit/736174d284

[ruby/csv] Ensuring StringIO's encoding in CSV.generate (#111)

2020-07-19T17:32:49+00:00

https://github.com/ruby/csv/commit/dbf55ef008

Remove unneeded exec bits from some files

2019-11-09T12:36:30+00:00

I noticed that some files in rubygems were executable, and I could think
of no reason why they should be.

In general, I think ruby files should never have the executable bit set
unless they include a shebang, so I run the following command over the
whole repo:

```bash
find . -name '*.rb' -type f -executable -exec bash -c 'grep -L "^#!" $1 || chmod -x $1' _ {} \;
```

Import CSV 3.1.2 (#2547)

2019-10-12T05:03:21+00:00

Fix keyword argument separation warnings in test

2019-08-30T19:39:31+00:00