Re: django-celery

2018-05-01 Thread Brian May
Thomas Goirand  writes:

> I agree as well. Please file a bug for its removal.

See Bug#897257.
-- 
Brian May 



Bug#897257: RM: django-celery -- ROM; Deprecated package

2018-04-30 Thread Brian May
Package: ftp.debian.org
Severity: normal

Hello,

django-celery is broken, deprecated upstream, and has been replaced by
other packages that are already in Debian, such as django-celery-results
and django-celery-beat.

This was discussed on debian-python, see:
https://lists.debian.org/debian-python/2018/04/msg00120.html

Please remove this package and all binaries from testing and unstable.

I don't believe anything depends on django-celery.

Thanks



Re: django-celery

2018-04-27 Thread Thomas Goirand
On 04/27/2018 08:22 AM, Brian May wrote:
> Hello,
> 
> Beginning to think we should seriously think about dropping this
> package. It is badly neglected by upstream, and there are now better
> alternatives. Such as django-celery-results (not sure if this is in
> Debian).
> 
> I attempted to fix it by upgrading to the latest upstream version (see
> git repository), but there are a number of python errors running tests,
> and I lack the interest in attempting to fix them (although at quick
> glance some of these errors look trivial to fix...)
> 
> As far as I am aware, nothing in Debian depends on django-celery.
> 
> Any thoughts?

I agree as well. Please file a bug for its removal.

Cheers,

Thomas Goirand (zigo)



Re: django-celery

2018-04-27 Thread Michael Fladischer

Hi Brian,

On 27/04/2018 08.22, Brian May wrote:

Beginning to think we should seriously think about dropping this
package. It is badly neglected by upstream, and there are now better
alternatives. Such as django-celery-results (not sure if this is in
Debian).


I'm completely with you on this. As the one who initially packaged 
django-celery it's time to drop it. Both its successors, 
django-celery-results and django-celery-beat are packaged for Python3 
(Python2 support can always be added if someone wants to step in) in Debian.


The only thing left to do is to find a way to do the transition to those 
new packages. I'm thinking about mentioning this in NEWS.Debian for 
django-celery as any automatic transition does not seem feasible.


Regards,
Michael



django-celery

2018-04-26 Thread Brian May
Hello,

Beginning to think we should seriously think about dropping this
package. It is badly neglected by upstream, and there are now better
alternatives. Such as django-celery-results (not sure if this is in
Debian).

I attempted to fix it by upgrading to the latest upstream version (see
git repository), but there are a number of python errors running tests,
and I lack the interest in attempting to fix them (although at quick
glance some of these errors look trivial to fix...)

As far as I am aware, nothing in Debian depends on django-celery.

Any thoughts?
-- 
Brian May 
https://linuxpenguins.xyz/brian/



Bug#881606: ITP: python-django-celery-beat -- Database-backed Periodic Tasks

2017-11-13 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-django-celery-beat
  Version : 1.1.0
  Upstream Author : Ask Solem 
* URL : https://github.com/celery/django-celery-beat/
* License : BSD-3-clause
  Programming Lang: Python
  Description : Database-backed Periodic Tasks

This extension enables you to store the periodic task schedule in the database.
.
The periodic tasks can be managed from the Django Admin interface, where you
can create, edit and delete periodic tasks and how often they should run.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAloJgOURHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WoEGwf/dtc7jVsZEiBpdBix/SpLjXngW0ol/aXM
ucDzYc4Gd4JGtLdY/tw0rJZFK5V9h5yRjLefkIY2bBoaeLoNygXeueFcrnOr4S2L
0Tn73sQVX7DMqrLMQ4qOTB5cE7mMmPY3fngoDQ00W4OPfZP5YgzclEhGzoRuIN5A
Z7mBEM+RhRHSe3QoVwt+U7nUrfxvZZd4psUToyTYg1pzrQWXQpPs2DW81YoMY7Nh
ZFwUy7MXq0d8biPGmdlk3X7fz10JRz92vHGIKTsFlYdzq1viDau0+zmDXdTQ7pan
OPQSxbd79UXL3Q5Bkgw1cuk1jh6+/1EReTYw0JhCUTq6lG2O+5DYdQ==
=fba9
-END PGP SIGNATURE-



Bug#871640: ITP: python-django-celery-results -- Celery result backends for Django

2017-08-10 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-django-celery-results
  Version : 1.0.1
  Upstream Author : Ask Solem 
* URL : https://github.com/celery/django-celery-results/
* License : BSD-3-clause
  Programming Lang: Python
  Description : Celery result backends for Django

 This extension enables you to store Celery task results using the Django ORM.
 .
 It defines a single model (django_celery_results.models.TaskResult) used to
 store task results, and you can query this database table like any other Django
 model.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAlmMH6wRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WoY8gf/UZjAs6ocs2/HgTvtGBfou8jt7+vtj8LQ
AusMa3XAnJXCLcprnrOvXeSgcIL4wnqDamiM4xNU248iPN/6ytgedPEM3wdBbWBE
Yl+wrc7MBLzWvVYi7PhGuijsDC230vZwzakFAHgcwoCHI1MPtUIpJ0Szw4/dJIMo
Ph1lFoyuoCySxYr6hnLeCDMRrhqiQjtwPecdmvFbopU1eupIxIFR7JA9n2K0FLqp
47cj8vIe3AgTd8NTFvpR36g3kFpteb68x3wgOeODsIUvDMqPdur+siRZ9eODdBdz
Xk61wYLesizsf+mWSkF65pzMPxOY+XasUlPMed/MEUtJJuO4cAtALQ==
=kHgA
-END PGP SIGNATURE-



Re: Bug#802839: django-celery: python 3 tests not invoked and break

2015-10-24 Thread Brian May
Robert Collins  writes:

> I'd probably shut that warning up using the warnings module API rather
> than weaking the test more broadly.

Might be the best thing.

> Also - track down and file a bug on the leak source.

How *do* you track these down? The warning doesn't say where the file
was opened.

Anyway, I suspect the problem is with the call to imp.find_module(),
which is a depreciated function in Python 3.4:

It ends with:

   file = open(file_path, mode, encoding=encoding)
   return file, file_path, (suffix, mode, type_)

djcelery.loaders.find_related_module() calls this function and ignores
the result. Which obviously means the file doesn't get closed.

try:
imp.find_module(related_name, app_path)
except ImportError:
return

return importlib.import_module('{0}.{1}'.format(app, related_name))

Need to think about if it is worth fixing, and what the best fix is.
-- 
Brian May 



Re: Bug#802839: django-celery: python 3 tests not invoked and break

2015-10-23 Thread Robert Collins
I'd probably shut that warning up using the warnings module API rather
than weaking the test more broadly. Also - track down and file a bug
on the leak source.



Re: Bug#802839: django-celery: python 3 tests not invoked and break

2015-10-23 Thread Brian May
Brian May  writes:

> ==
> FAIL: test_discovery_with_broken (djcelery.tests.test_discovery.TestDiscovery)
> --
> Traceback (most recent call last):
>   File 
> "/home/brian/tree/debian/python-modules/django-celery/tests/../djcelery/tests/test_discovery.py",
>  line 45, in test_discovery_with_broken
> self.assertEqual(log, [])
> AssertionError: Lists differ: [ 0x7f2b03474c88>] != []
>
> First list contains 1 additional elements.
> First extra element 0:
> {message : ResourceWarning("unclosed file <_io.TextIOWrapper 
> name='/home/brian/tree/debian/python-modules/django-celery/tests/someapp/tasks.py'
>  mode='r' encoding='utf-8'>",), category : 'ResourceWarning', filename : 
> '/home/brian/tree/debian/python-modules/django-celery/tests/../djcelery/loaders.py',
>  lineno : 204, line : None}
>
> - []
> + []
>
> --
> Ran 66 tests in 0.340s
>
> FAILED (errors=2, failures=1)

That includes a debug message I put in. Oops. Showing the warning object
that caused the problem.

It seems that Python3 is generating an unexpected error ("unclosed
file") that is upsetting the test because it expects 0 warnings.

Any ideas how to fix this? It doesn't appear to be this project that is
producing the warning, maybe that comes from Django.

Or should I just remove the Assert?

The code in question that appears to be producing the warning:

def autodiscover():
"""Include tasks for all applications in ``INSTALLED_APPS``."""
global _RACE_PROTECTION

if _RACE_PROTECTION:
return
_RACE_PROTECTION = True
try:
if django.VERSION < (1, 7):
return filter(None, [find_related_module(app, 'tasks')
 for app in settings.INSTALLED_APPS])
else:
from django.apps import apps
return filter(None, [find_related_module(app.name, 'tasks')
 for app in apps.get_app_configs()])
finally:
_RACE_PROTECTION = False


This is in git, in the expected python-modules location.
-- 
Brian May 



Bug#791675: ITP: django-celery-transactions -- Django transaction support for Celery tasks

2015-07-07 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: django-celery-transactions
  Version : 0.3.2
  Upstream Author : Nicolas Grasset  
* URL : 
https://github.com/fellowshipofone/django-celery-transactions
* License : BSD-2-clause
  Programming Lang: Python
  Description : Django transaction support for Celery tasks

 django-celery-transactions holds on to Celery tasks until the current database
 transaction is committed, avoiding potential race conditions as described in
 Celery's user guide.

 Features:
  * If the transaction is rolled back, the tasks are discarded. Django's
transaction middleware does this if an exception is raised.
  * If transactions aren't being managed, tasks are sent as normal. This means
that sending tasks from within Django's shell will work as expected, as
will the various transaction decorators commit_manually, commit_on_success,
etc.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJVm9zJAAoJEGlMre9Rx7W2lpwP/1f9pXdPYtCPSlMGvT2uKTOQ
8xY7d4N/sViPnFigNAuMqsYcdBILNCZodRPEHxBZCSuOejcV4CD+IJVnT0vLXFbe
ITF1g9U6AMV078QUqM8R4sg2W8QtYyqskcDADiTBBcv0r+ux+8d7leEHpWipmyt2
7qKTZUiKYMVri5NkylVLVOWuzcknw1zrA+Dxbw9Y3UmoMa2ew39r/zO4BacYxoF4
MvM6l4KRlku6JX/+ErEdi9g+xgcAzb1/imR5KA2U76O6I94FJq84ajpXcc/INKzg
nhGnmuNS/EtT+19ZTT771c76pKnSS+JzR9W4fX94us0fKzuCDAXTF/1W+wnQ1Nvg
yFMrjC6cIgk910CWv1A8Ok8zGS2Le8rjnuzJFntY9YjEYxO8IafPRWU0eBDEP288
435d8T8NVgJbvBbqALH7QadOg2NbQCd6fnMZ/FteixSuFt+rJMTl+lPNj+g1osox
QsgtvEfocdaLOxZpSj53WLwG4iJR9aeeHxnmAa5q5yiUzReEP1Pc7Oo1TYHcX9cN
iJR89ptds7uQLV555qbGtzD1Qf3rjnL5/kSWCl9AHM/cibjmrAi5Bn6wB3UOWIBB
rFAQ+QIN3ge0zBDIC15W5LC/sg59srfn2ME4yWJJ0pYmzEUb0zBp2Lnzp1PJCgGr
I3tEUIAaCKEs/bttoZOV
=76Fc
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150707140604.31702.78899.reportbug@kashyyyk



Bug#726993: RFS: django-celery-transactions/0.1.3-1 [ITP] -- Django transaction support for Celery tasks

2013-10-21 Thread Michael Fladischer
Package: sponsorship-requests
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "django-celery-transactions"

  * Package name    : django-celery-transactions
Version : 0.1.3-1
Upstream Author : Chris Doble 
  * URL : https://github.com/chrisdoble/django-celery-transactions
  * License : BSD-2-clause
Section : python

It builds those binary packages:

    python-django-celery-transactions - Django transaction support for Celery 
tasks

To access further information about this package, please visit the following 
URL:

http://mentors.debian.net/package/django-celery-transactions


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/d/django-celery-transactions/django-celery-transactions_0.1.3-1.dsc

More information about django-celery-transactions can be obtained from 
https://github.com/chrisdoble/django-celery-transactions.

Regards,
Michael Fladischer

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCgAGBQJSZQOdAAoJEGlMre9Rx7W2eToQALaaJGXd0fHMjaywSXOnQbsL
SspnfHt62+/3iQ8A25d0zp/25+vu7cNAz2Biw80i4oAziAUxqUq0KPrNjrQpcFgJ
8YWfyZyufvhSHj8DklAJoIYnmMc8/fyCtoAcKCknTD55bW+kOlp5r17x1MojriKQ
qKskZekmPF4fciotutGDZ8LtnfjaXx1Kk1CKUr4NpG4OiZn/SsQq72U61zCgNotZ
VW4iVLIZjYwraNXBMdoXCVQftoef4/iJJD0qQ7mbsklaribDDc9nbsQHHjy7tZ5r
XRiwMSGFq81PWH+MLudGvmWqsmo4FXs0uFHOC1JvDvf38okKa0TdiidWCYUX4/S0
zVkjsnSqh8NOB14jPseB9+0ddSkQb9rblziAdx17lyMbpfgi7U9DsjM5HfVNQ+Ut
WNhkHvvUIr1lqMTUDzJ7mb0RXHnAdhW6Nmtbt86YVqky8Y33VSJMM3sSMwQQHN5D
rt9gOpsEWE3nRLm9+a1NqPh6RuxxfS1bDXWXKLAaJnEaKPmnvugDjtSq9S1zPAom
M6daYjMzZWth+q+tbORjmvM195pw7fMX9VRRVovtieOOdYKa+4xVxCvNC2l2Sa3j
dr5IucARwnndvkg+Y2TD/svxBgf7FTuEerMqs6fwBhAFbKC9dwvt8XCmJr7iNr0l
jLMTXGXVrEJv+eMC+hoR
=uolS
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131021103616.17641.64104.report...@server.home.fladi.at



Bug#726990: ITP: django-celery-transactions -- Django transaction support for Celery tasks

2013-10-21 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: django-celery-transactions
  Version : 0.1.3
  Upstream Author : Chris Doble 
* URL : https://github.com/chrisdoble/django-celery-transactions
* License : BSD
  Programming Lang: Python
  Description : Django transaction support for Celery tasks

django-celery-transactions holds on to Celery tasks until the current database
transaction is committed, avoiding potential race conditions where the task is
executed before the transaction is committed in the database.

Features:
 * If the transaction is rolled back, the tasks are discarded. Django's
   transaction middleware does this if an exception is raised.
 * If transactions aren't being managed, tasks are sent as normal. This means
   that sending tasks from within Django's shell will work as expected, as
   will the various transaction decorators commit_manually, commit_on_success,
   etc.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCgAGBQJSZPlEAAoJEGlMre9Rx7W2b5gQAJo9OVS04xGuJ/AWxbGDiZhQ
Omge27bdw8f0uOiCq4PR8l/WHg7fLDp/qqIhbI/zI3gk/et954t/YAEw5ShN4C8J
SHHZ8+yWrhp0Z3DrLJh6nhLP47+V6LDEP4HIBQH0MDxgCSnTRSXqW3c/1rX87MQ7
VjwfdrpMZtbK53K6Y00cfo3QaKosiGsKU/qGPpxArUeiymg4nN3BedMkZ8oR/SoY
I30Z0596DaicuPN2HehENWlH92azWV8Bp+uxWlHkHnvy2RA4mE6B6ev9AxK022lH
kHW57XmASPwuPJ5pRG3vBJ/E24+dFBEKGRYLRYhJg07K6P5Lj0HvqCR0n/WjSbWY
cs8hBGbRwhS906833Ii4khdP9lnh5dqsKfdA3/na8/LFhIz18VsRQqB3NP8fnIdL
2lhwNwwCuIgt4l5KUAbhMWxEEgchIxPuR3A8lLRG5sMDQ7P+COrQ5IhpdBR8yL/q
yTcRGofxJDVd0K8gL/okGN6J5zP7wagy1bWNe5KjBATGwOvR7GIpoemRhemNHD02
xBlCtNVfEYNzIVY/sNXvJ8kbNPWKaCJk7s7mCG6ZHYeSExlNbd6ouyW5bB/SCRxx
jFOy+tWz/7fEIfzGKXM7lGpHucC/TceCcidYkuxcM55Bnfh+xjEYnj8yipRFtje2
06zdkoF4gCYiKTxAc/Hu
=076R
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131021095208.17798.14971.report...@server.home.fladi.at