[Python-modules-team] Bug#868808: Bug#868808: celery: Memory addresses being output in documentation fixed in upstream

[Preston Moore]

Here is the commit in question:

https://github.com/celery/celery/commit/bccea8de7dc083d390509f686aaa79c5e30fa5bd

It is a very small fix.


Thanks,
Preston


> On Jul 18, 2017, at 6:35 PM, Brian May  wrote:
> 
> Preston Moore  writes:
> 
>> As part of the reproducible builds effort[1] I have been working with 
>> Celery's
>> developers to merge a fix that will allow Sphinx to correctly strip memory
>> addresses as it generates Celery's documentation.  This fix is now in place
>> upstream. 
> 
> It seems like there is not going to be a new celery release anytime
> soon:
> 
> https://github.com/celery/celery/pull/3958#issuecomment-313997326
> 
> Are you able to provide a link to the commit that fixed this?
> -- 
> Brian May 

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#868808: Bug#868808: celery: Memory addresses being output in documentation fixed in upstream

[Brian May]

Preston Moore  writes:

> As part of the reproducible builds effort[1] I have been working with Celery's
> developers to merge a fix that will allow Sphinx to correctly strip memory
> addresses as it generates Celery's documentation.  This fix is now in place
> upstream. 

It seems like there is not going to be a new celery release anytime
soon:

https://github.com/celery/celery/pull/3958#issuecomment-313997326

Are you able to provide a link to the commit that fixed this?
-- 
Brian May 

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team