ShaheedHaque

With VERBOSE=1, the first error messages are: >>>>> >[ 36%] Building CXX object src/CMakeFiles/Py3KF5KI18n.dir/pybuild/PyKF5/KI18n/unifiedKI18n.cpp.o cd /home/srhaque/kdedev/frameworks-bindings/build/ki18n-prefix/src/ki18n-build/src && /usr/bin/c++ -DPy3KF5KI18n_EXPORTS -DQT_CORE_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DTRANSLATION_DOMAIN=\\"ki18n5\\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE...

Based on the documentation on TRANSLATION_DOMAIN in ki18n/docs/programmers-guide.md, I tried prepending an `#undef TRANSLATION_DOMAIN` to the unifiedKI18n.cpp generated by the cmake logic, and that at least allows the compilation to...

I have forgotten the exact details, but if you have ki18n building, then perhaps we can just move on. FWIW, it was something like this: while I was using the...

Another option may be related to how the Celery pool (at least for the default configuration of "prefork") uses forking to create workers. The use of forking causes several issues...

What @naggie says makes perfect sense, but would appreciate knowing if @iandouglas or anybody else has a hybrid setup going? I'm ask because this project appears not to use the...

Thanks for the reply.

@jreese Any chance of a new PyPI release to pick up the likes of ffe7c7be61a0? I'd have asked over on your new repo but I could not see where to...

Thanks. Perhaps after that this issue can be closed...

@jreese Thanks for the new release, I can confirm the warnings I reported are gone.

I tried to debug this, and noticed that the shell seems to think that the *configured* beat schedule is empty: $ celery -A myapp shell ... >>> celery.conf.beat_schedule {} Could...