Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2014-02-14 Thread Etienne Millon
Hi,

According to pypi, charade has been merged into chardet.
Is packaging charade still relevant?

* https://pypi.python.org/pypi/chardet:
 This is a continuation of Mark Pilgrim's excellent chardet.
 Previously, two versions needed to be maintained: one that supported
 python 2.x and one that supported python 3.x. We've recently merged
 with Ian Corduscano's charade fork, so now we have one coherent
 version that works for Python 2.6+.

-- 
Etienne Millon


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2014-02-14 Thread Daniele Tricoli
retitle 698258 RFP: python-charade -- universal encoding detector for Python 2 
and Python 3
noowner 698258
thanks

Hello Etienne,

On Friday 14 February 2014 14:49:41 Etienne Millon wrote:
 According to pypi, charade has been merged into chardet.
 Is packaging charade still relevant?

Thanks for reminding that I had to close this bug.
Yes, I talked to Piotr after the discovery of the merge, and
packaging charade make no sense anymore:
closing this bug was in my TODO list, thanks for the reminder!

Piotr, I can help updating python-chardet if you agree.

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org

signature.asc
Description: This is a digitally signed message part.


Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2014-02-14 Thread Piotr Ożarowski
[Daniele Tricoli, 2014-02-14]
 On Friday 14 February 2014 14:49:41 Etienne Millon wrote:
  According to pypi, charade has been merged into chardet.
  Is packaging charade still relevant?
 
 Thanks for reminding that I had to close this bug.
 Yes, I talked to Piotr after the discovery of the merge, and
 packaging charade make no sense anymore:
 closing this bug was in my TODO list, thanks for the reminder!
 
 Piotr, I can help updating python-chardet if you agree.

https://pypi.python.org/pypi/chardet is the current one, right?

I will try to update it this weekend, feel free add yourself to
Uploaders if you beat me to it


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-11-25 Thread Piotr Ozarowski
[Daniele Tricoli, 2013-11-25]
 Piotr, do you have any concerns?

not anymore, please send me RFS mail when it's ready
(you can also add python-chardet package that imports * from charade
and I will remove chardet from Debian)


signature.asc
Description: Digital signature


Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-04-26 Thread Daniele Tricoli
Hello Ian,
sorry for this late response.

[CCing Piotr to get his attention]

On Wednesday 20 March 2013 03:41:19 Ian Cordasco wrote:
 I was only concerned because, if I remember correctly, Debian has a
 python-requests package. As someone who doesn't use Debian (or Ubuntu)
 I was concerned (as a maintainer of requests) that the vendored
 dependencies were being stripped and other Debian packages used in
 their stead.

Yes, Debian has a python-requests package: I'm the maintainer of the 
package, but I'm also a user of python-requests; So I want it in the best 
shape ;)

I understand your concern, and I want to make clear why, as the maintainer 
of python-requests I decided to use chardet instead of charade: after doing a 
diff between charade 1.0.1 and the version of chardet we have in Debian there 
were almost no difference.

My plan was to get charade into Debian before uploading a new version of 
requests, but yesterday Thomas Goirand uploaded requests 1.2.0: I discovered 
looking at commit log on #debian-python :)

As you can understand by this ITP, I'm in favor of having charade in Debian 
and this is my advocacy:
1) charade has an active upstream (which is very kind and supportive) :)
2) charade fix long standing bugs of chardet
3) charade is used by requests, a very popular library

Ian, can you add something more? I think point 1 and 2 are enough to have 
charade in Debian.

I plan to start packaging charade so I will can upload a new revision of 
requests 1.2.0 that use charade instead of chardet.

Piotr, do you have any concerns?

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org

signature.asc
Description: This is a digitally signed message part.


Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-03-19 Thread Daniele Tricoli
Hello Ian,
sorry for this late response I was a bit busy this month.

I'm CC'ing the BTS so your reply can be read by anyone.

On Wednesday 13 February 2013 15:42:51 Ian Cordasco wrote:
 I'm the maintainer of charade and I just noticed your email thread on
 Debian. I just wanted to point out that requests is using charade
 because of how it vendors all of its dependencies.

Many thanks for your reply!

 Trying to have both python-chardet and python3-chardet in the same 
 package was causing a lot of problems and overall hair-pulling. charade 
 is just a way of supporting both python 2 and python 3 in the same 
 package without needing separate versions for separate python versions.

I understand the problem of having both python-chardet and python3-chardet 
in the same package but this problem doesn't exist in Debian, so I can't 
rely to this to bring python-charade into Debian.

Don't think Debian just don't care about it, but having two similar 
projects in the archive demands a cost, so we have to illustrate advantages 
clearly.

 It's still being improved and we are adding new encodings as well, so 
 your effort to add it to the Debian repositories was not in vein. We 
 don't yet have support for those encodings, but I'm planning on working 
 on them over the next couple weekends. If you're interested in helping, 
 that would be awesome.

Enhancements in python-charade is a very good point to bring it into 
Debian, and I undelined your enhancements for this reason.

I don't have a lot of time at the moment but I will try to devote a bit of 
time to help!
 
 Just thought I'd give you the short story as to why requests uses (and
 loves) charade, and give you some more reasons for arguing your case
 in the future.

Many thanks for your words! I will keep an eye to this ITP.

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-03-19 Thread Ian Cordasco
On Tue, Mar 19, 2013 at 5:58 PM, Daniele Tricoli er...@mornie.org wrote:
 Hello Ian,
 sorry for this late response I was a bit busy this month.

No worries

 Trying to have both python-chardet and python3-chardet in the same
 package was causing a lot of problems and overall hair-pulling. charade
 is just a way of supporting both python 2 and python 3 in the same
 package without needing separate versions for separate python versions.

 I understand the problem of having both python-chardet and python3-chardet
 in the same package but this problem doesn't exist in Debian, so I can't
 rely to this to bring python-charade into Debian.

 Don't think Debian just don't care about it, but having two similar
 projects in the archive demands a cost, so we have to illustrate advantages
 clearly.

I was only concerned because, if I remember correctly, Debian has a
python-requests package. As someone who doesn't use Debian (or Ubuntu)
I was concerned (as a maintainer of requests) that the vendored
dependencies were being stripped and other Debian packages used in
their stead.

 It's still being improved and we are adding new encodings as well, so
 your effort to add it to the Debian repositories was not in vein. We
 don't yet have support for those encodings, but I'm planning on working
 on them over the next couple weekends. If you're interested in helping,
 that would be awesome.

 Enhancements in python-charade is a very good point to bring it into
 Debian, and I undelined your enhancements for this reason.

 I don't have a lot of time at the moment but I will try to devote a bit of
 time to help!

Yeah, frankly, I have been very busy since sending that email and
finding the information needed to add those character sets has not
been... simple. Hopefully I will finish my degree uneventfully and
find more time afterward.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-01-21 Thread Daniele Tricoli
On Friday 18 January 2013 03:42:55 Daniele Tricoli wrote:
 Maybe I can just update requests using python-chardet for now, but I'm
 a  bit worried about that missed detection on Python 3.

Using python(3)-chardet, all requests' tests are ok, so for now I'm going 
to use it. I'm keeping this open to be ready if in future we need to switch 
to charade.

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-01-17 Thread Piotr Ożarowski
  python-charade is a port of Mark Pilgrim's chardet with support for both
  Python 2 and Python 3.

if Python 3 support is the only reason why it was forked, note that we
already have python3-chardet in Debian. Are there any other advantages?

 The package will be maintained under the umbrella of the DPMT and it's
 a dependency for the new version (1.1.0) of python-requests.

can requests use chardet?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-01-17 Thread Daniele Tricoli
Hello Piotr,
thanks for your comments!

On Thursday 17 January 2013 12:38:12 Piotr Ożarowski wrote:
   python-charade is a port of Mark Pilgrim's chardet with support for
   both Python 2 and Python 3.
 
 if Python 3 support is the only reason why it was forked, note that we
 already have python3-chardet in Debian. Are there any other advantages?

The Python 3 support is not what made me think about packaging python-
charade: right now python3-requests 0.12.1-1 is using python3-chardet.

Note that I missed, when I sent the ITP, that the following is true for the 
development version. I took project information from the git but I missed 
that the default branch is the development one:

Inside clean and isolated virtualenv:

Python 2.7.3 (default, Jan  2 2013, 13:56:14) 
[GCC 4.7.2] on linux2
Type help, copyright, credits or license for more information.
 import charade
 data = open('bom-utf-16-be.srt', 'rb').read()
 charade.detect(data)
{'confidence': 1.0, 'encoding': 'UTF-16BE'}

Python 3.2.3 (default, Sep 10 2012, 11:22:57) 
[GCC 4.7.1] on linux2
Type help, copyright, credits or license for more information.
 import charade
 data = open('bom-utf-16-be.srt', 'rb').read()
 charade.detect(data)
{'confidence': 1.0, 'encoding': 'UTF-16BE'}

Here, instead, the system wide Debian python-chardet:

Python 2.7.3 (default, Jan  2 2013, 13:56:14) 
[GCC 4.7.2] on linux2
Type help, copyright, credits or license for more information.
 import chardet
 data = open('bom-utf-16-be.srt', 'rb').read()
 chardet.detect(data)
{'confidence': 1.0, 'encoding': 'UTF-16BE'}

Python 3.2.3 (default, Sep 10 2012, 11:22:57) 
[GCC 4.7.1] on linux2
Type help, copyright, credits or license for more information.
 import chardet
 data = open('bom-utf-16-be.srt', 'rb').read()
 chardet.detect(data)
{'confidence': 0.5, 'encoding': 'windows-1252'}

Is it worth backporting to python-chardet? Right now charade doesn't differ 
to much from it but in future it might be.
 
  The package will be maintained under the umbrella of the DPMT and it's
  a dependency for the new version (1.1.0) of python-requests.
 
 can requests use chardet?

Right now, yes, since the two codebase don't differ much. requests is 
currently embedding charade 1.0.1, so there should be no problems.

Maybe I can just update requests using python-chardet for now, but I'm a 
bit worried about that missed detection on Python 3.

What do you suggest?

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org


signature.asc
Description: This is a digitally signed message part.


Bug#698258: ITP: python-charade -- universal encoding detector for Python 2 and Python 3

2013-01-15 Thread Daniele Tricoli
Package: wnpp
Severity: wishlist
Owner: Daniele Tricoli er...@mornie.org

* Package name: python-charade
  Version : 1.0.1
  Upstream Author : Ian Cordasco graffatcolmin...@gmail.com
* URL : https://github.com/sigmavirus24/charade
* License : LGPL
  Programming Lang: Python
  Description : universal encoding detector for Python 2 and Python 3

 python-charade is a port of Mark Pilgrim's chardet with support for both
 Python 2 and Python 3.

 Supported encodings:

   - ASCII, UTF-8, UTF-16 (2 variants), UTF-32 (4 variants)
   - Big5, GB2312, EUC-TW, HZ-GB-2312, ISO-2022-CN (Traditional and
 Simplified Chinese)
   - EUC-JP, SHIFT_JIS, ISO-2022-JP (Japanese)
   - EUC-KR, ISO-2022-KR (Korean)
   - KOI8-R, MacCyrillic, IBM855, IBM866, ISO-8859-5, windows-1251
 (Cyrillic)
   - ISO-8859-2, windows-1250 (Hungarian)
   - ISO-8859-5, windows-1251 (Bulgarian)
   - windows-1252 (English)
   - ISO-8859-7, windows-1253 (Greek)
   - ISO-8859-8, windows-1255 (Visual and Logical Hebrew)
   - TIS-620 (Thai)

The package will be maintained under the umbrella of the DPMT and it's
a dependency for the new version (1.1.0) of python-requests.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org