me it's a bug in setuptools since the function that do this check and
raise the error are from setuptools package.
Alan
On 3 July 2013 19:50, Chris Barker - NOAA Federal wrote:
> This is really a build question, rather than a distributuion question
> -- I"d try th
dline-6.2.4.1/egg-dist-tmp-eyGcUE
error: Setup script exited with error: $MACOSX_DEPLOYMENT_TARGET mismatch:
now "10.3" but "10.4" during configure
How can solve this problem please?
Thanks in advance,
Alan
--
Alan Wilter SOUSA da SILVA, DSc
Bioinformatician, UniProt - PANDA, E
Hello,
On 10/18/11 06:04, PJ Eby wrote:
Does it occur with plain distutils (i.e., no setuptools)?
Yes, it seems that the behaviour persists.
Regards,
Alan Haggai Alavi.
--
The difference makes the difference.
___
Distutils-SIG maillist
re is anyway that I can help.
Attachment files:
- http://alanhaggai.org/files/Foo-0.2.0.zip
- http://alanhaggai.org/files/ark.png
- http://alanhaggai.org/files/zip_parser.out
Regards,
Alan Haggai Alavi.
--
The difference makes the diffe
On Wed 27 Jul 2011 02:34:03 PM CEST, Zvezdan Petkovic wrote:
> In short, the order is important:
>
> 1. build a source distribution
> 2. register
> 3. upload
I'd object that. I've always used register without creating a source
dist; the data used for registering just comes from
On 07/27/2011 09:01 AM, Algis Kabaila wrote:
> ak@supremo:/dat/work/py3/Matrix-Algebra$ python setup.py sdist upload
I can't see Matalg on pypi.
Have you tried registering before uploading? Can you see Matalg in the
list of packages you own when you login into pypi website?
python setup.py reg
.
That's probable. In that case I won't modify the releaser, maybe I
could start a totally different project, but I'd like to reuse what
can be reused.
--
Alan Franzoni
--
contact me at public@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
On Tue, Jan 11, 2011 at 2:41 PM, Maurits van Rees
wrote:
> Op 11-01-11 12:51, Alan Franzoni schreef:
>>
>> Hello,
>> I'm trying to automate my release process from vcs - something like:
>>
>> run tests ->
>> fetch current major, minor from branch (
ht I break other things unexpectedly?
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
, but work on that direction is being done. Feel
free to ask more questions if you need to.
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
k out distutils2 as well.
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
for systemwide package managers - dpkg/rpm - and Java
software (maven-ivy-etc) says we're currently doing it wrong in
Python. I'll do a research in other environments - ruby/gems,
perl/cpan, Haskell - and I hope we can work to change this.
--
iscussed at length in the past. The consensus, AFAIK
> is to be as nonrestrictive as possible in library distributions. Use
> lower bounds when you depend on a new feature. Use upper bounds if
> you know you have to, but you probably don't know this at the time you
> make the distri
es
not work, it's not a great win, don't you think so?
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
y path, nor yum neither apt will be able to do anything.
>
> The way to work around this with buildout is to use a buildout versions
> section:
>
> http://pypi.python.org/pypi/zc.buildout#repeatable-buildouts-controlling-eggs-used
>
> It wou
Hello,
I've got a strange issue with version resolution when using
zc.buildout; I don't know if it's zc.buildout specific or it's caused
by something which is done by distribute.
The example code can be fetched from there:
hg clone https://a...@bitbucket.org/Alan/buildout
imagine
nobody has really a good grasp on what's going on "under the hood".
I'm looking forward to help with packaging tools before it's too late
:-)
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG mail
python packaging FAQ?
If it has been reported many times but keeps popping up, it's probably
unpredictable enough. It took me 3 hours just on yesterday evening to
find a workaround to that, and I'd have gladly spared that :-(
--
Alan Franzoni
--
On Thu, Dec 9, 2010 at 11:25 PM, Alan Franzoni wrote:
[cut]
It appears that the zope.interface mantainer from Debian manually
copies the unnecessary - and confusing - __init__.py files:
http://svn.debian.org/viewsvn/pkg-zope/zope.interface/trunk/debian/rules?revision=2074&view=markup
It s
can I
find more info on them? Who's creating them, setuptools/distribute?),
but their usage and the declare_namespace method seems mutually
exclusive by the way; was that confusing zc.buildout, I suppose?
Should I open a ticket on ubuntu zope.interface package?
-
is suggested, but I
don't see enough proof that the reason behind such error lies within
namespace_packages. I'll make some tests in the next days and I'll
check whether it's the case.
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
funny sys.path mangling, probably ubuntu.
Yes, I suppose it's a kind of interference. I don't really know who's
causing the problems, I think we'd need some feedback from both
zc.buildout and ubuntu developers, but I can see Ubuntu still packages
1.4.3 even in Natty - there might b
For the records, or if anybody hits this problem before it's fixed;
the only way to cope with this that I found is to add
include-site-packages = false
in the configuration. This forces the redownload of the egg and
everything works fine.
--
Alan Franzoni
--
contact me at pub...@[mysu
I've verified this happens all the times on Ubuntu 10.10, both 32 and
64 bit. I don't know if it's Ubuntu's or zc.buildout's fault; I've
opened a ticket.
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distut
rference between the two install systems is not unlikely.
Just some questions for you, Attila:
- was your zope.interface installed through portage or via easy_install/pip?
- can you see zope.interface 3.6.1 being downloaded during the
buildout launch phase?
--
Alan Franzoni
--
contact me at p
le
"/tmp/MyProj/eggs/zope.testrunner-4.0.0-py2.6.egg/zope/testrunner/__init__.py",
line 21, in
import zope.testrunner.interfaces
File
"/tmp/MyProj/eggs/zope.testrunner-4.0.0-py2.6.egg/zope/testrunner/interfaces.py",
line 21, in
import zope.interface
ImportError: No module named interface
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
== 1.1 , it picks 1.1.0 . If I use >= 1.1 and <1.2.0, it
will pick beta releases for 1.2 as well.
That's quite clumsy, since it's something I do often and it's quite a
common practice (I suppose); isn't there any regex/wildcald character
support? Would any patc
27;d like to do something like:
import mymodule
get_pkg_info(mymodule).project_name
?
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
You
might just say "hey, lib A B C are always available on Windows
environments, pack everything else along." . I would keep advising
packing the interpreter as well, by the way.
Very important: I'm not a PyInstaller fan (I've used it a couple of
times), I'd just like to pre
ork easily
only for really simple cases. Everything else will just turn
overcomplicated.
You're really trying to port to Python what Java does through its
classpath system and, to a greater extent, with Osgi; but Python
philosophy is quite different, you'll end up distributing whole OSes!
hared libraries in order to
distribute your packages in a self-contained way. It's quite risky, my
approach with RPMs is to let the packaging system handle system-wide
deps, and use zc.buildout to handle python eggs and extensions.
--
Alan Franzoni
contact me at pub...@[mysurname].eu
_
holding your code, your scripts, and all downloads
& dependency eggs. And it's *really* easy to automatically create an
rpm once your project is setup that way, I think zc.buildout is
already got a recipe for RPMs about that.
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
_
me to a more precise subpackage, please?
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
you see some obvious issues?
4) how would you handle requirements string?
--
Alan Franzoni
--
contact me at pub...@[mysurname].eu
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
but this is a bit of mess when setting dependencies in setup.py and
retrieving them.
The problem around is with the project download page then; I should
just ask the developer to remove the dumb binary dist (which is mostly
useless btw, containing paths to the developer's machine homedir)?
--
ed.
So here I go:
melquiades:/ alan$ sudo /opt/local/bin/easy_install-2.6 byteplay
install_dir
/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/
Searching for byteplay
Reading http://pypi.python.org/simple/byteplay/
Reading http://code.google.com/p/byteplay
Re
viour with zc.buildout automatic dep fetching?
Thank you!
Alan Franzoni
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
On 7/13/10 1:50 PM, Maurits van Rees wrote:
> [buildout]
> extends = devel.cfg
I had no idea about the "extends" config option in zc.buildout. That'll
work perfectly right for us.
Thank you!
--
Alan Franzoni
contact me at
#x27;t right now, I'll be happy to code and submit a
patch. Any thoughts on what's the right approach? e.g. convention-based
naming (buildout.cfg.local.001 in the same dir as buildout.cfg, etc).
Thank you!
--
Alan Franzoni
contact me at pub...@[mysurname].eu
___
Is there any ETA on the next release of 0.6?
On Mon, Jul 14, 2008 at 2:50 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 12:11 PM 7/14/2008 -0500, Alan Runyan wrote:
>>
>> Just ran across the NameError that was fixed in revision 60846.
>> Looks like setup.py was
Just ran across the NameError that was fixed in revision 60846.
Looks like setup.py was bumped to 0.6c9 in revision 60848.
Was 0.6c9 intended to be released?
I heard a rumor of released software "gone missing" from pypi.
Curious to the status.
c
41 matches
Mail list logo
