Make it pip installable about django-ajax HOT 9 CLOSED

Sadly, I can't. Someone made a lightweight utility library and named it django-ajax. He has no interest in renaming it and no interest in consolidating.

from django-ajax.

See https://pypi.python.org/pypi/django_ajax (Yes, PyPI is too dumb to suss out the difference between a - and an _.)

from django-ajax.

💩

I'll close it. I think the other pip instructions in the readme will at least help.

from django-ajax.

@joestump Sorry, I have to jump in here, please read my last email again:

Hi Joe,

Given you're averse to merging and you'd like to keep your package a
simple lightweight set of helpers, I don't think there's a reasonable
way to merge.

I'm not strictly against merging. I'm not sure how to merge, that'a all.
And that's the reason I asked you about your merge plans, it looked like
you have thought about this.

BTW, next time you build a package like this I might suggest a more
specific naming mechanism so that people will know it's only meant for
"utils" or "helpers" (e.g. django-ajax-helpers or django-ajax-utils).

I think the same is true for your package (django-ajax-api?).
django-ajax is probably way to generic for most packages. Anyways I
could rename django_ajax, too. I really don't want to stand in the way
of any django project.

Probably the best would be to create a django-ajax package without any
downloads, just linking to django-ajax-api and django_ajax_utils or
something similar.

What do you think?

David

First I offered you to rename my project, so you could keep your name. Second I suggested a different solution, including a meta package to guide people to the right place and asked about your opinion

I never received an answer. So please, if you want to sort out an pip install, keep the discussion up. I'm open to anything, but I don't want to not talk about things first.

from django-ajax.

@ddanier Your email is pretty clear in that you don't believe any package should be django-ajax. I disagree (and still do), but didn't see a reason to followup.

So here's my answer in full:

1. You didn't offer to change anything. You said you could rename. Not that you were willing to. And you did so after telling me my own package should be renamed.
2. This package was released 8 months prior to your own. It's also a tested, full-featured framework for Django with tons of users and lots of contributors vs. a utility app with template tags and a few context processors that appears to have been thrown over the wall 8 months ago and left as-is.

I didn't think we were comparing apples so I didn't reply. I didn't see a way to repsond in a manner that would result in you renaming your package and django-ajax with this package taking over the name in PyPi.

Sometimes I don't respond to emails because I don't feel like getting into a fight with a random stranger on the internet over shit that doesn't matter.

from django-ajax.

@joestump So somewone tells you he thinks your package should not be named django-ajax and still offers you to give that name up. I really don't see any reason not to take that chance.

Regarding 1.: I said I could rename my project and don't want to stand in the way of your project. I thought it was pretty clear this means I will change my project name if you insist. As I'm not a native speaker this maybe was not clear enough.

Regarding 2.: Sorry, but just shouting "First" is really childish. In fact my project is older, but has not been released to the public for some time...like you did miss to put your project on PyPI yourself. But I really don't think this is important. Whats important is the fact, that your project really has all the advantages you noted. Thats the reason I'm still willing to give up django_ajax and allow you to pick up that name on PyPI. (Sidenote: I'm still using my project and will continue to. I really don't need much more features, thats all.)

So, I didn't compare anything. I just wanted to sort this out the right way. Thats why I suggested to add a django-ajax meta package, so people could find many more AJAX utilities for django. I just wanted to get this right, so no need to fight about anything.

So if your still interested in getting django-ajax on PyPI, just mail me again. But please don't blame me for standing in your way. I don't want to and won't do this. But you have to talk about this with me, I'm not just going to delete the package after an email from some "random stranger". ;-)

from django-ajax.

This exchange is why I didn't reply to the original email.

from django-ajax.

@joestump I get the feeling your not willing to reasonable discuss this. Probable you haven't thought it through or you just don't care. So let me explain:

I can't just delete the package on PyPI. If I did I would break some installations, including my own projects. The reason why it has been put there is to make installation easy. So yes, I am using "pip install django_ajax" and I need to update all projects to an new name, new imports and so on. Otherwise the pip install will break or install a totally different package. This would be bad. And this is mainly the reason I tried to get some discussion going about how to proceed.

So, now I'm just suggesting this:

1. I rename django_ajax to (for example) django_ajax_utils (have to check the name first)
2. I'll change the current django_ajax package in a way it still works (depends on django_ajax_utils, wrappers for imports, raising a DeprecationWarning) and includes information about both projects in the PyPI description
3. We have to give this some time (at least 1 month, I would suggest 2 or 3 months)
4. This one is up to you. We could keep this django_ajax package as some meta package like I suggested before. But I'm still willing to just delete it after some transition period.

So please stop blocking a discussion you started yourself, please stop blocking getting django-ajax (your project) on PyPI and just drop me an note, if you want me to get this going. If you have objections, please write them down, so I am able to answer. I really want to support you here.

And just to be totally clear: There's nothing keeping you from putting django-ajax on PyPI. PyPI does not care about the package name, the python module and the website URL being the same. You already would have differences here, as the proposed package name is "django-ajax" and the python module would be just "ajax". So if you'r not willing to to this with a clean transition please feel free to just put the project on PyPI. You could have done this month ago.

from django-ajax.

I'm leaving my package as-is, if I end up wanting to include it in PyPi I'll be renaming it and putting an appropriate redirect on GitHub. I hope this resolves this matter.

from django-ajax.