headers
Richard Jones | 1 Apr 2013 08:41
Picon
Gravatar

Reminder: catalog-sig is retired

Please direct all followups / CCs to distutils-sig.


Thankyou,

    Richard
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 0 comments |
headers
Richard Jones | 30 Mar 2013 23:16
Picon
Gravatar

Shutting down catalog-sig

Hi all,

We're about to merge the catalog-sig and distutils-sig by just removing the catalog-sig mailing list. If you wish to remain in the discussions regarding Python package cataloging then please subscribe to the distutils SIG.

The catalog SIG archives will remain, but the mailing list will be deleted and the SIG will be retired.

There's no real timeframe but it will be happening imminently.


     Richard

_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 0 comments |
headers
PJ Eby | 29 Mar 2013 19:54
Gravatar

Re: How to determine if archive is an sdist or bdist

On Fri, Mar 29, 2013 at 11:00 AM, James Carpenter <nawkboy <at> gmail.com> wrote:
> Looks like the idea of using a custom command is a better approach then.

I'm not sure why you think that.  The only kinds of archives whose
file types are ambiguous from the name, are sdist, bdist_dumb, and
random raw source dumps.  Everything else has a unique extension like
.egg, .exe, .msi, rpm, etc.  If you have a .zip, .tar.gz, .tgz, or
some other archive name, you can find out if it's an sdist by
inspecting its contents as I described.  And if it's not an sdist, you
can usually tell if it's a raw source dump by checking for a setup.py
in the archive root or a depth-1 subdirectory off the root.  (That's
what easy_install does, anyway, when it's given an archive it doesn't
know what to do with.)

>
> Is a custom command my only choice or can I register pre/post hooks to any
> given command?
>
>
> On Thu, Mar 28, 2013 at 3:36 PM, PJ Eby <pje <at> telecommunity.com> wrote:
>>
>> On Thu, Mar 28, 2013 at 3:57 PM, James Carpenter <nawkboy <at> gmail.com>
>> wrote:
>> > Is there an easy way to programmatically tell if an archive (tar.gz,
>> > zip,
>> > etc.) in the dist directory is a binary or sdist? I would like to
>> > post-process the contents of a dist directory and classify each build
>> > artifact there (egg, sdist, bdist, etc.).
>>
>> An sdist always has a single subdirectory in the archive's root
>> directory, named for the package+version, and containing a PKG-INFO
>> and setup.py (plus a bunch of other stuff).
>>
>> A bdist_dumb will not have such a subdirectory in the archive root;
>> instead it will have one or more directories like /usr, /opt, /Program
>> Files.
>>
>> Other bdist formats?  Hard to say.
>
>
Permalink | Reply | 3 comments |
headers
James Carpenter | 28 Mar 2013 20:57
Picon

How to determine if archive is an sdist or bdist

Is there an easy way to programmatically tell if an archive (tar.gz, zip, etc.) in the dist directory is a binary or sdist? I would like to post-process the contents of a dist directory and classify each build artifact there (egg, sdist, bdist, etc.).

Currently the only approach I know of is to have my own command that is run along with the relevant build command.  For example:

python setup.py sdist be_funky

or:
python setup.py sdist bdist bdist_egg be_funky

Using this approach the tuples in  self.distribution.dist_files provide the command, python version and file created. Unfortunately this solution is slightly more complicated in my use case than simply having an easy way to classify each build artifact and extract it's pkg-info.

_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 1 comment |
headers
Donald Stufft | 28 Mar 2013 19:22
Gravatar

Merge catalog-sig and distutils-sig

Is there much point in keeping catalog-sig and distutils-sig separate?

It seems to me that most of the same people are on both lists, and the topics almost always have consequences
to both sides of the coin. So much so that it's often hard to pick *which* of the two (or both) lists you post
too. Further confused by the fact that distutils is hopefully someday going to go away :)

Not sure if there's some official process for requesting it or not, but I think we should merge the two lists
and just make packaging-sig to umbrella the entire packaging topics.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA


_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 28 comments |
headers
Richard Jones | 28 Mar 2013 01:29
Picon
Gravatar

PEP 438 progress update

Hi all,

It was my intention to formally accept the PEP and deploy the
implementation to the production PyPI when I got back home this week,
but things have been quite hectic and I've not found the time to
perform the pre-deployment tasks needed (specifically steps 5, 6 and 7
of the first transition phase; determining the various email lists I
need to inform people of the changes.) At the moment I'm not sure when
I'll have time to do that; hopefully next week some time but it could
be as long as four weeks before I get sufficient tuits(round).

    Richard
Permalink | Reply | 0 comments |
headers
Andreas Jung | 27 Mar 2013 16:54

c.pypi.python.org - IP address change


Hi there,

I moved my c.pypi.python.org mirror to a new faster machine.

Please update the DNS entry to 176.9.146.29.

This mirror is  running on top of Christian Theune's bandersnatch
implementation.

Andrreas

--

-- 
ZOPYX Limited         | Python | Zope | Plone | MongoDB
Hundskapfklinge 33    | Consulting & Development
D-72074 Tübingen      | Electronic Publishing Solutions
www.zopyx.com         | Scalable Web Solutions
--------------------------------------------------
Produce & Publish - www.produce-and-publish.com
Attachment (lists.vcf): text/x-vcard, 353 bytes
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 1 comment |
headers
Jesus Cea | 26 Mar 2013 21:07
Picon
Favicon

Suscribing to PYPI projects


I wonder if would be too difficult to be able to subscribe to projects
in PYPI, to be notified if a new version is available.

An option to PIP & family to verify local versions with PYPI versions,
and report old version would be useful too.

--

-- 
Jesús Cea Avión                         _/_/      _/_/_/        _/_/_/
jcea <at> jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
Twitter:  <at> jcea                        _/_/    _/_/          _/_/_/_/_/
jabber / xmpp:jcea <at> jabber.org  _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
Permalink | Reply | 2 comments |
headers
Chris Withers | 26 Mar 2013 15:02
Picon

error trying to upload by package

Hi All,

I have a package called files: https://github.com/Simplistix/files

...but I get a 403 when I try to register it on PyPI.

Why is that?

cheers,

Chris

--

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Permalink | Reply | 1 comment |
headers
anatoly techtonik | 22 Mar 2013 09:32
Picon
Gravatar

PyPI Crediting

Does anybody think that PyPI source code base should include the names of the people who contributed to its development?
--
anatoly t.
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 0 comments |
headers
anatoly techtonik | 22 Mar 2013 09:26
Picon
Gravatar

PyPI web interface UX (Was: API for uploading packages to PyPI)

OMG. I didn't even looked at the boxes. IMHO somebody should reduce the amount of duplication and choices between menu and boxes. It is really-really overburdened. For example, no need to say "use search above" when it is evident the you need to find the button, or to use that "browse all packages" link when it is actually a first item on the menu.

RSS should be moved out of scope of main menu. It is just "yikes!".
The whole menu section with links to main Python web site should be moved out of place (is there a quick way to measure how many users follow these links)?

Yes, I can send a patch if everyone agrees.
--
anatoly t.


On Fri, Mar 22, 2013 at 11:16 AM, Ronald Oussoren <ronaldoussoren <at> mac.com> wrote:

On 22 Mar, 2013, at 8:37, anatoly techtonik <techtonik <at> gmail.com> wrote:

Hi,

I understand that this will make PyPI a potential target for automated spam bots, but still it will be awesome to have an API to upload packages to PyPI.

For example, I have a code that extract all necessary meta data for the package from the source file itself. It is even able to generate setup.py from this data. https://bitbucket.org/techtonik/astdump The next logical step in this chain is to teach it to upload stuff to PyPI.

Now I thought that this setup.py is an unnecessary complication. What I need, ideally is just upload single .py file, or a JSON and a .tar.gz FWIW. Is there a straightforward API for things like that? 

Several APIs are documented on pages linked directly from the PyPI homepage (the Infrastructure box)

Ronald

Please, CC.
--
anatoly t.
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig


_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 0 comments |

Gmane