debug binaries not replaced from python.org

[Denis Akhiyarov]

If I install conda on Python 3.6 from python.org, then the Python debug binaries *._d are not replaced by conda versions. Could this create binaries incompatibility issues when building native packages locally?

[Ray Donnelly]

I am not sure what you mean by 'install on'. If you mean install to the exact same location then that is not something you should do. Conda Python and python.org Python should not be mixed like this. You should uninstall one before installing the other ideally it else install them to a different location.

For your specific question, Anaconda Python does not provide debug binaries and therefore they will not overwrite those from python.org

On Jun 26, 2017 9:00 PM, "Denis Akhiyarov" <denis.a...@gmail.com> wrote:

If I install conda on Python 3.6 from python.org, then the Python debug binaries *._d are not replaced by conda versions. Could this create binaries incompatibility issues when building native packages locally?

--
Anaconda Community Support Group Brought to you by Continuum Analytics
---
You received this message because you are subscribed to the Google Groups "Anaconda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+unsubscribe@continuum.io.
To post to this group, send email to anac...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/anaconda/.

[Denis Akhiyarov]

Ok, then i guess i have to compile all my dependencies without using conda. Mixing pip/python.org, conda/miniconda/anaconda is not recommended, but people do it all the time due to limitations of either side.

On Monday, June 26, 2017 at 3:06:50 PM UTC-5, Ray Donnelly wrote:

I am not sure what you mean by 'install on'. If you mean install to the exact same location then that is not something you should do. Conda Python and python.org Python should not be mixed like this. You should uninstall one before installing the other ideally it else install them to a different location.

For your specific question, Anaconda Python does not provide debug binaries and therefore they will not overwrite those from python.org

On Jun 26, 2017 9:00 PM, "Denis Akhiyarov" <denis.a...@gmail.com> wrote:

If I install conda on Python 3.6 from python.org, then the Python debug binaries *._d are not replaced by conda versions. Could this create binaries incompatibility issues when building native packages locally?

--
Anaconda Community Support Group Brought to you by Continuum Analytics
---
You received this message because you are subscribed to the Google Groups "Anaconda - Public" group.

To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+u...@continuum.io.

[Ray Donnelly]

If you can articulate the limitations on the Anaconda side that would be useful. Are you requesting a full debug variant of Python here? For that to work with Anaconda we'd have to provide a complete set of python modules compiled against that debug variant too which is not a minor task.

To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+unsubscribe@continuum.io.

[Denis Akhiyarov]

At least the set of debug symbols/binaries provided by python.org would be great! All the rest should really be compiled locally, if debug symbols and/or binaries are required.

The use case is debugging using Visual Studio the managed or native CPython extensions or embedded CPython, especially built with Cython or pythonnet.

[Ray Donnelly]

OK, can I ask that you file a feature request at https://github.com/ContinuumIO/anaconda-issues/issues please?

To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+unsubscribe@continuum.io.