updating classifiers in setup.py

[eliasdorneles]

Hey fellows,

This fixes the pre-alpha classifier (see #18) and also add Topic :: Text Processing :: Markup.

We can consider it stable since v1.0, Scrapy is even depending on the current API already.

Also, maybe we could add the more specific Topic :: Text Processing :: Markup :: HTML and Topic :: Text Processing :: Markup :: XML too (see list of classifiers here).

What do you think?

Thanks!

[codecov-io]

Current coverage is 100.00%

Merging #19 into master will not affect coverage as of e0fcb62

@@            master     #19   diff @@
======================================
  Files            4       4       
  Stmts          194     194       
  Branches        28      28       
  Methods          0       0       
======================================
  Hit            194     194       
  Partial          0       0       
  Missed           0       0       

Review entire Coverage Diff as of e0fcb62

Powered by Codecov. Updated on successful CI builds.

[kmike]

Can someone please run python setup.py register to update classifiers on pypi without making a new version?

[eliasdorneles]

@kmike we'll release a 1.0.1 soon, do you think we should still register it for 1.0.0?

[eliasdorneles]

btw, as agreed with @dangra, I added HTML and XML classifiers too: c88d95f

[kmike]

I just wanted to mention that if the only reason to release 1.0.1 is to get classifiers updated then one can use python setup.py register, without bumping version.

[dangra]

why not going trough the usual flow of releasing a patch version? it seems natural to me and it doesn't have any disadvantages

[eliasdorneles]

@kmike well, I fixed a typo in HISTORY and I'll also add docstrings to csstranslator.py to help justify the release. =D
sorry guys, I should've been more careful.

[kmike]

and it doesn't have any disadvantages

One release more means users have to check what is changed one more time, download the package one more time and read one more changelog entry (irrelevant for the user). Not a big deal, but still.

setup.py register only changes what's displayed on pypi website, it doesn't change the tgz/wheel file.

I'll also add docstrings to csstranslator.py

A docstring is a code change, so it can justify a release :)

[dangra]

One release more means users have to check what is changed one more time, download the package one more time and read one more changelog entry (irrelevant for the user). Not a big deal, but still.

I think it is up to the guy in control of releases, although we will need an emoji for 🚲shedding :)

[kmike]

My point is that if we know nothing is changed from user's point of view we shouldn't do a release.

+1 to find a right emoji :)

[eliasdorneles]

🚲 ⛺ ?

[kmike]

👍

[dangra]

nice one :)